Versions Compared

Old Version 34

changes.mady.by.user Robert Alexander Marshall

Saved on

compared with

New Version 35

changes.mady.by.user Robert Alexander Marshall

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Migration Process Steps

Excerpt
Info

Prerequisites

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

Info

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.

Info

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.

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

Info

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. Refreshing the connection in this way is a recommended option if you encounter a problem with the migration.

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.

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

Migration Process Tasks

PLAN YOUR MIGRATION

Expand
titlePlanning actions
Filter by label (Content by label)
showLabelsfalse
sortcreation
showSpacefalse
cqllabel = "planning" and space = "MIG"

PREPARE CLOUD SITE & TEST

Expand
titleCloud site preparation
Filter by label (Content by label)
showLabelsfalse
sortcreation
showSpacefalse
cqllabel = "prepcloud" and space = "MIG"

MIGRATE

Expand
titleAtlassian migration actions
Filter by label (Content by label)
showLabelsfalse
showSpacefalse
sortcreation
cqllabel = "migrate" and space = "MIG"

MIGRATE CLOUD TASKS

Expand
titleManual taks to complete the migration and the setup o your cloud site
Filter by label (Content by label)
showLabelsfalse
sortcreation
showSpacefalse
cqllabel = "migratecloudtasks" and space = "MIG"

(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").

Info

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