Migration Process Steps
It is highly recommended that you first undertake a test migration of all the content in a single test space and ensure the workflow state names are the same in cloud as in server.
Prerequisites
In your Confluence Server / Data Center Instance:
The latest version of Confluence Cloud Migration Assistant
The latest version of Comala Document Management
Confluence Cloud instance with Comala Document Management Cloud installed
On both instances
Confluence admin permission
Space admin permission
Check your requirements for an auditable history for page workflow events and activity before migration
Only the current page workflow state is migrated but to maintain a compliance record you can
run the Attach Activity utility in each space to add the workflow events and activity history as a CSV file attachment for each page with workflow activity that is then migrated with the page
choose to retain your legacy server/data center instance in read-only mode
Installation of the latest app version ensures you have the latest updates to support your migration.
Step 1 Plan your migration
review and plan the Atlassian Confluence migration process and the data that Confluence will migrate
review the feature differences of Comala Document Management in cloud compared to server
check what is migrated and what is not migrated to Confluence Cloud
always have an up to date backup of your server/datacenter source instance
use the Attach Activity utility in each space in server to generate and attach a CSV attachment of the page workflow events and activity to each page in the space
check the page-level restrictions on your source documents - pages with restrictions may not be migrated
A list of any pages with restrictions is generated in the Vendor checks in the Atlassian Migration Assistant as part of the migration pre-checks.
You will need administrator permission for both the server instance and the cloud site.
You can use the Comala Migration Assessment Tool to help analyze your server instance use of the Comala Document Management app.
Migration on a space-by-space basis (or if a larger instance on a small batch basis) is recommended to help in identifying any issues that may occur. It is recommended to undertake a test migration using a single space.
Step 2 Prepare Cloud site and test
Once Comala Document Management Cloud is installed to your cloud site you can prepare your cloud site.
set up an appropriate Confluence cloud instance as the target instance for the migration
install the Comala Document Management for Cloud app in your cloud instance
familiarize yourself (and your team and stakeholders) with Confluence cloud and cloud app capabilities
apply the required Comala Document Management workflow. This workflow can be
one of the workflows included on installation of the cloud app
a workflow translated from your server instane to cloud compatible JSON workflow using workflow translator☨ in server or data center
a workflow a custom workflow created in cloud using workflow builder
test your cloud setup and workflow
On installing Comala Document Management for Cloud, the following workflows are installed and available in each space
Some features of the workflows included with the cloud app may vary from the features found in the server/data center workflow with the same name.
☨ The workflow translator to cloud tool is available in our server and data center app to support creation of a JSON cloud-compatible copy of a server workflow template that can be added to your cloud space. The tool also highlights any workflow features in a server workflow template that cannot be translated to a JSON cloud workflow.
Step 3 Migrate
migrate your content, users and the current workflow state using the Confluence Cloud Migration Assistant
enable or apply your workflow to your content in cloud and validate*
Atlassian Migration Assistant runs pre-migration checks on our app and identifies issues that affect the migration such as pages with restrictions; Attach Activity CSV file process completion to include a record of each server page workflow activity.
* The workflow state names must match (including upper/small case letters) between server and cloud. Otherwise, the current state is not migrated.
It is recommended that you create a migration for each individual space.
To apply your custom workflows, we recommend the creation of these in a test space and then simply copy and paste the JSON workflow markup into the markup editor in the production space Document Management dashboard. You should also validate any workflows created using the server/dc app workflow translator to cloud tool in a test space before adding to your production space.
Migration Process Tasks
PLAN YOUR MIGRATION |
PREPARE CLOUD SITE & TEST |
MIGRATE |
MIGRATE CLOUD TASKS |
Be aware that some available app features may be located or be named in a differently in cloud. For example
Page Activity is available as Document Activity through the page tools menu
space administrators access the space app configuration in Space Settings>App links>Document Management
The workflow state at the time of migration is added as an attachment to the migrated document. The full history of workflow events and activity is not retained.
You can include a record the source page workflow events and activity by using the Attach Activity utility in each space to create and attach a CSV file of the workflow events and activity history to each page in the the server/data center before migrating the space to cloud.