Compliance-heavy industries and technical documentation teams need automated document control – not the overhead of managing multiple standalone apps. If your organization is running Comala Document Management in Confluence, the migration to Cloud is the right moment to consolidate your governance into Aura Workflow.
The best part: AppAnvil’s “Free Migration Included” service means our experts handle the heavy lifting for you – a risk-free transition at no additional cost.
What You Gain by Moving Your Workflows to Aura Workflow
Consolidating your document governance from Comala into Aura Workflow delivers three measurable advantages:
- Automated Lifecycle Management: Automate your entire document lifecycle from creation to publication. Use conditional logic to enforce the exact reviews and approvals required to meet your organizational standards – with total consistency across your instance.
- Precision Control and Security: Maintain full control over document reviews and access. Configure workflows with role-based reviews and expirations to ensure data security and version accuracy while keeping your teams moving at full speed.
- Verifiable Audit Readiness: Build organizational trust with a complete, built-in audit trail. Aura captures every edit, approval, and activity, providing a verifiable history so you always know who did what and when.
Prerequisites: Getting Comala Document Management Ready for Migration
The Comala-to-Aura migration supports both Comala Data Center and Comala Cloud. However, if your goal is to run Aura Workflow in Confluence Cloud, your Comala instance must be accessible for the migration script to extract workflow data.
For organizations moving from Data Center to Cloud, complete your DC-to-Cloud migration first using the Atlassian Cloud Migration Assistant. Once Comala Document Management is running in its Cloud version, you can proceed with the Aura migration.
Additional prerequisites:
Aura Workflow must be installed and your target workflows must already be configured in Aura — with matching state names where possible.
You need Site Admin permissions in Confluence to access the migration feature.
You will receive the migration script bundle from AppAnvil on request, or a consultant can run the migration for you.
How the Migration from Comala Document Management to Aura Workflow Works
Unlike other Aura migrations that use a point-and-click wizard, the Comala Document Management migration is a script-based process with a JSON upload. The migration preserves each page’s current workflow state, so your content continues where it left off after switching to Aura Workflow.
Here is how the process works in five steps:
Step 1: Recreate Your Workflows in Aura
Before migrating, set up your Comala workflows in Aura Workflow — either as global or space-scoped workflows, matching your existing Comala setup. Use the same state names as in Comala where possible. If a state name cannot be matched during migration, the page will be assigned the workflow’s initial state as a fallback.
Step 2: Run the Migration Script
AppAnvil provides a migration script bundle that connects to your Comala instance, extracts all active workflow assignments, and generates a JSON file. The script supports both Comala Data Center and Comala Cloud.
For Data Center, the script extracts workflow data automatically using your DC credentials. For Cloud, the Comala API does not expose workflow names directly — the generated JSON will contain placeholders that must be manually replaced with the actual Aura workflow names and scopes before uploading.
Step 3: Review the Generated JSON
Before uploading, review the JSON file. Each entry represents a single page or blogpost with its workflow assignment, including the content title, current state name, space key, target workflow name, and workflow scope. Verify that workflow names match your Aura configuration exactly, scopes are correct (global or space), and state names match the target Aura workflow.
Step 4: Upload and Start the Migration
Open Aura Workflow in Confluence, navigate to the Migration section, and upload the JSON file. Click Start Migration to begin the process. Large files are uploaded in chunks automatically.
Step 5: Monitor and Finalize
The migration UI shows applied pages, failed pages, and elapsed time in real time. You can stop and restart the migration at any time. After completion, successfully migrated pages will have their Aura Workflow applied with the correct state, and a migration history event is recorded for each page.
If some pages failed, review the count and retry the migration for the remaining pages.
For a full technical walkthrough – including script configuration, JSON field reference, state matching logic, and troubleshooting — visit the complete migration documentation.
Done with Comala? Other Migration Paths in the Aura Ecosystem
The workflow migration is part of a broader strategy to consolidate your Confluence app stack. Other supported migration paths include:
Data and Visualization: Move from Stiltsoft Table Filter to Aura Table Filter for integrated charting and modern filtering while preserving your spreadsheets.
Structure and Design: Replace the Refined Macro Toolkit or Appfire Numbered Headings with Aura Formatting — the headings migration is silent and follows ISO standards.
Technical Documentation: Migrate from Appfire LaTeX Math or Narva LaTeX Math to Aura Formatting for high-fidelity mathematical notation across your wiki.
Additional Workflow Apps: The Aura Migration Hub also supports transitions from AppFox Workflows, Appfire Page Approval, and Comala Publishing.
Ready to Modernize Your Document Governance?
Stop managing compliance with fragmented tools. AppAnvil’s free migration service makes the switch from Comala Document Management to Aura Workflow effortless and risk-free.