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

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

0

What is migrated to Cloud? What is not migrated to Cloud?

What is migrated to Cloud?

Only the following is migrated with the Confluence Cloud Migration Assistant

  • current workflow status of each page

  • an entry in the workflow history

Any document that had a workflow applied while being in server,  in each Cloud space (after reindexing the workflow or initializing workflow states) will have

  • a lozenge added to the content in cloud showing the current workflow status

  • an entry on their Workflow History saying "Document has changed to 'xxx' state"

These will be present as long as document has been properly migrated using the Atlassian Migration process and the linked user exists in the Cloud instance.

What is not migrated to cloud?

The following is not included in the migration

  • workflows 

  • full page activity 

  • expiry date(s)

  • assigned approvers

  • assigned read confirmations

When migrating to Cloud

 (info) There are a number of Comalatech workflows installed with the Cloud app but these have different functionality compared to those bundled with the server app.

Be aware that some available app features may be located and named in a different manner. For example, in cloud

  • Page Activity is available as Workflow History through the page tools menu

  • space administrators access the space app configuration in Space Settings>Content Tools>Document Management 

Support

Please feel free to raise a support ticket with Comalatech Support.

  • No labels