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

Version 1 Next »


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

Installation of the latest app version ensures you have the latest updates to support your migration.

Step 1 Plan your migration

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

  • 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 a Comala Document Management bundled workflow or recreate your custom workflow in cloud using workflow builder and test

Once Comala Document Management Cloud is installed to your cloud site you can prepare your cloud site.

On installing Comala Document Management for Cloud, the following workflows are available

The workflow translator to cloud tool is available in our server app to support creation of a JSON code copy of a server workflow template that can be added to your cloud space. The tool highlights any workflow features in a server workflow template that cannot be translated to a JSON cloud workflow.

Step 3 Migrate

* 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 prior to adding to your production space.


Migration Process Tasks




MIGRATE CLOUD TASKS

 Manual tasks to complete the migration and the setup of your cloud site

Ensure that the workflow state names are the same in server and cloud, otherwise the current workflow state is not migrated.


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 activity is not retained.

Related Pages

Comalatech Document Management

Atlassian

  • No labels