This site has moved to the integrated Appfire documentation and information site for our apps.
From February 2024 this site is no longer updated.
Take a look here! If you have any questions please email support@appfire.com
What is migrated by the Confluence Cloud Migration Assistant?
- Robert Alexander Marshall
What is migrated?
current workflow status
an entry in the workflow history - "Document has changed to 'xxx' state"
This is dependent on the successful migration of the page and the associated user.
Our integration with the Confluence Cloud Migration Assistant currently migrates the 'current workflow state' of page.
The page activity (aka workflow history), workflow markup, and other data are not included in the migration.
What is not migrated?
the workflowÂ
full-page activity
expiry date
assigned approvers
assigned read confirmations
Pages with restrictions will not migrate the Comala Document Management workflow state. These will be identified in the Vendor App Checks screen in the Atlassian Migration Assistant and details will be added to the CSV file that can be downloaded. Page restrictions will need to be temporarily removed prior to the migration to cloud.
Solution(s)
The workflow
You can use workflow builder in Cloud to recreate your workflows.
The app can be installed with the JSON version of the standard workflows installed in server.
Some features available in the JSON workflow in cloud may be different to those available in server.
It is not possible to use a script converter to convert the server markup to JSON.
Page activity
The page activity is not automatically migrated. The only current way to add the record to Cloud is through a page-by-page manual and cumbersome process by downloading a CSV file.
Expiry dates, assigned approver and assigned read confirmation data
These cannot be migrated and will need to be added to your Cloud site.
Further information
