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 20 Next »


Migration Process Steps

Prerequisites

  • Confluence Server instance with the latest update of Atlassian Migration Assistant

  • Latest version of Comala Document Management installed in your server or data center instance

  • Confluence Cloud instance with Comala Document Management Cloud installed

  • On both instances

    • Confluence admin permission

    • Space admin permission

(blue star) Installation of the latest app version will ensure you have the latest updates to support your migration.

Step 1 Plan your migration

(warning) Remember that 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

(blue star) 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.

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

  • enable migrations in Comala Document Management global configuration in cloud

(green star) On installing Comala Document Management for Cloud, the following workflows are available

Step 3 Migrate

  • refresh the connection between the Confluence instance and the migration service

  • 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

(blue star) You can refresh the connection between the Confluence instance and the migration service in Comala Document Management cloud global administration by moving the Enable migrations slide toggle option to OFF and then back to On in the cloud app global admin.

This is also a recommended option if you encounter a problem with a migration.

(green star) To apply your custom workflows, we recommend the creation of these in a test space and then simply copy the JSON workflow markup to your production space

Completing your cloud set up will include tasks such as choosing whether to process your workflows to the migrated state or initialize to a different state.

Migration Process Tasks

MIGRATE CLOUD TASKS

 Manual taks to complete the migration and the setup o your cloud site

(info) The workflow state at the time of migration is added as an attachment to the migrated document. To update the document workflow state correctly reindex the workflow applied to content, or if required, initialize your workflow to the required state for all the content. Otherwise, the workflow report for these documents will list documents as "not initialized").

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 Workflow History through the page tools menu

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

Migration Guide

  • No labels