EDITING
Overview
Migration to Cloud requires the completion of the following
|
Due to the limitations of the Atlassian Cloud platform
- the Comala Document Management app does not have full feature compatibility between the Server app and the Cloud app
- once the Atlassian Confluence migration is completed you must install the Comala Document Management for Cloud in your Cloud instance
- add and apply the required Comalatech workfow
There is a limitation on the number of documents that can be included in a migration for Comala Document Management
- you will not be able to migrate more than 15,000 documents in a single migration
For instances larger than this, an instance-wide migration may time out. If this occurs, please try to migrate on a space-wide basis.
After the migration has been completed each space will need to be reindexed . This final step is is required to update the document workflow state correctly (otherwise the workflow report for these documents will list the document as "not initialized").
What is migrated to Cloud? | Prerequisites and preparation |
|---|---|
When choosing to migrate Comala Document Management to Cloud
Any document that had a workflow applied while being in Server
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 | You should
|
† 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. †† For example, a features not available in Cloud is the ability to filter the application of a space workflow to content by label. | |
In your source server instance, you can
- use the Comala Document Management Migration Assessment tool to view your current usage and populate the Comala Document Management Migration Assessment with your usage data
- create a support package for each space using the Comala Document Management Server Support Console
You can then, if required, raise a support ticket with the Comalatech support team and attach the support package and the usage data
If your migration includes over 200 pages with an applied Comalatech workflow it is recommended that you raise a support ticket to discuss your migration plans with the Comalatech Migration Support Team.
Be aware that some available app features may be located and named in a different manner. 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
Migration Steps
Enable the Atlassian Migration Assistant in your server instance
You must install following Atlassian dark feature in your Server instance for enabling the Atlassian Migration Assistant: migration-assistant.app-migration.feature
- navigate to
<HOST>/admin/darkfeatures.action - choose Add dark feature
- select
migration-assistant.app-migration.feature
Also check that your Confluence Cloud Migration Assistant is updated in your Cloud site.
Comala Document Management Server/Data Center Migration Assessment
Before undertaking any Atlassian migration activity, there are two steps to undertake in your server instance to enable the Comala Migration Assessment on your instance to gather the Comalatech data usage.
Enable Comala Document Management Migration Assessment data storage
- Choose the global configuration for the app
- scroll down to Comala Document Management Migration Assessment
- check Enable Migration Assessment data storage
- Save the configuration
The migration data will now be added to the Comala Document Management Migration Assistant in the server app global configuration. It is useful to enable this data storage in advance of copying the Usage data to allow usage of the app to fully populate the assessment data.
Copy the Usage Data added to the Comala Document Migration Assessment
- choose the global Comala Document Migration Assessment
The Migration Assessment data for the app is added to this migration assessment screen.
The assessment includes a numeric summary of the total usage of Comala Document Management app across your instance and the Usage data for the Comala Document Management app.
- select and copy the contents of Usage data box
- paste and save to a text editor
If you raise a support ticket with Comalatech for help with the migration, please include this copy of the Usage data.
Atlassian Confluence Migration
Migrate your Confluence instance using Atlassian Migration Guide
- the Atlassian Migration Guide guide supports the assessment of your needs and helps you plan your Confluence instance data migration including the options for migrating users.
The Comala Document Management for Cloud app must be installed in the Cloud instance. This setting ensures that the current Comalatech workflow state data for each document is migrated by the Atlassian Migration Assistant.
When using the Atlassian Migration Assistant option to Assess Apps ensure you set dropdown option for the Comala Document Management app as Needed in cloud.
If not already done so, you also be asked to confirm agreement to your app data migration.
Currently only the current Comalatech workflow state and details of the user associated with the the last action is migrated.
If not previously completed, Confirm the agreement to remove this blocking error from the Atlassian Migration Assistant
When performing this Confluence migration, it is recommended to migrate at an instance level. Otherwise Comalatech cannot commit to the correct migration of users’ related data.
In-App Migration Task
You need to have installed the Comala Document Management for Cloud app.
It is recommended that you have installed the Comala Document Management for Cloud app BEFORE you have completed the migration of your instance using the Atlassian Migration Assistant.
As a Confluence global administrator In your Cloud instance
- choose Comala Document Management app global Configuration
- move the slider to Enable Migrations
This means for any page migrated that had an applied Comalatech workflow in your Server/Data Center instance will retain the last workflow state information.
The space Workflow Report in the cloud instance will display all migrated pages in a space that had a workflow applied.
The workflow state and date of the migration will be displayed in the page tools workflow history option.
On the page and in the page workflow history report, these states will need to be /wiki/spaces/AWPD/pages/6428168172 when the required workflow is added to the content.
Manual Migration Tasks
Due to the limitations of the Atlassian Cloud platform the migration of the Comala Document Management app will only migrate the following
- the current workflow state data for each page
- the user details for the change to the current state in the Comalatech workflow for each page
The tasks include
User migration
The migration of the actual users for access must be done as part of the Atlassian Migration Assistant.
Comalatech workflows in Cloud
Due to limitations of the Atlassian Confluence Cloud platform, some Comalatech workflow server app features are not available or have a different range of functionality in Comalatech Document Management for Cloud workflows. For example, events and action macros available for JSON triggers in Cloud
Comalatech workflows bundled with Comala Document Management for Cloud app will have some different functionality compared to those in the Server/Data Center app.
- if using one of these bundled workflows, you will need to review its functionality in the Comala Document Management for Cloud app
If you require a custom Comalatech workflow used in your Server or Data Center instance, the workflow must be reproduced manually in your Cloud instance by
- editing the JSON markup in the markup editor in the Comala Document Management for Cloud app
- creating a new custom workflow using workflow builder in the Comala Document Management for Cloud app
Additional app installation
In your Cloud instance, if needed
- different space publishing of content will require the Cloud Publishing for Cloud app
- Read Confirmations will require the Read Confirmations for Cloud app
Space reindex
The final step in migration is to reindex the content for each space.
This is needed to update the document state correctly for those pages that you have not visited yet.
Otherwise, the state displayed for these documents in the Workflow Report will be listed as “not initialised”.
In your Cloud instance
- choose Space Settings>Content Tools>Document Management
- scroll down to Utilities>Migrated Space
- choose Reindex Workflows
Avoiding migrated user login issues
After the migration process has been completed it is recommended to exit and log in so migrated users are available (otherwise, the Cloud instance doesn’t recognize them).
Maintaining an audit history
If your organization is in a Compliance/Regulatory industry and you periodically get audited, then you will be required to keep Confluence on a Server so auditors can review your previous Workflow History/Page Activity. The same goes for the Page Status.
You cannot migrate the full workflow history and page status to Cloud.