Overview
Atlassian provides guides to support Cloud to Cloud migration of Confluence content.
- Migration of a Confluence cloud site to another existing cloud site
- Importing a Confluence space from one cloud site to another cloud site
However, migrating your content or importing a space does not include any apps installed in the source site.
You must undertake a number of steps to ensure that you can use your Comalatech Document Managment family app in your new site and retain the Comalatech workflow history.
Comala Document Management family app migration
In Confluence Cloud, the Comalatech app workflow history is not included in either the Confluence migration or Confluence space import process.
- only the last workflow state is retained for the document as data after the Confluence migration/Confluence space import
To retain access to the Comalatech workflow history a workflow history backup in each source space must be created prior to the migration/export process.
To copy the workflow history, for each space you must
- before migration/export backup workflow history in each source space
- migrate your cloud site or export an individual space in XML format
- after migrating your data, install the Comala Document Management family app in your new cloud site
For each space in your new site, choose the space settings>Comala Document Management/Control/Approval dashboard for the installed Comalatech app
- enable the space workflow
- reindex the space
- load the workflow history
If you are using a page workflow this needs to be added manually to each document.
A custom Comalatech workflow must be copied from the source site as a JSON file and added to each space in the destination site using the JSON editor in each cloud site. Custom workflows are only available in Comala Document for Management for Confluence Cloud - both the source and destination site need to have the Comala Document for Management for Confluence Cloud app installed.
Related links
Comalatech Documentation
Atlassian Documentation