Versions Compared

Old Version 10

changes.mady.by.user Robert Alexander Marshall

Saved on

compared with

New Version Current

changes.mady.by.user Robert Alexander Marshall

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Image Removed
Image Removed
Image Added


Image Added

Migration Process Steps

Excerpt
Tip

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.

Info

Prerequisites

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

Info

Step 1 Plan your migration

  • review and plan

and review
the Comalatech app in Cloud
Server

  • server

  • check what is migrated and what is not migrated to Confluence Cloud

  • always have an up to date backup of your server/

data center (warning)

  • datacenter source instance

  • ensure you have the latest Confluence Cloud Migration Assistant installed in your server/data center instance and enabled

    • use the Attach Activity option in server to generate and attach a CSV attachment of the page workflow activity to each page in the space

    You will need administrator permission for both the server instance and the cloud site.

    (blue star)

    You can use the

    Comalatech

    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.

    Info

    Step 2 Prepare Cloud site and test

    • set up an appropriate Confluence

    for Cloud

    • cloud instance as the target instance for the migration

    • install

    the 

    • the Comala Document Management for Cloud app in your

    Cloud instance

  • enable migrations in Comala Document Management cloud configuration

    • apply a predefined

    • 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
    the refresh the connection between the Confluence instance and the migration service

    • workflow builder and test

    Migrate

    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.

    Info

    Step 3 Migrate

     ‡

    • enable or apply your workflow to your content in

    Cloud

    • cloud and validate

    (info) You can refresh the connection between the Confluence instance and the migration service.
    Simply move the Enable migrations slider toggle option to OFF and then back to ON in the global admin for the app in your cloud side.
    This is also a recommended option if you encounter a problem with a migration.

    ‡

    • *

    * The workflow state names must match (including upper/small case letters) between server and cloud. Otherwise, the current state is not migrated.

    Image Added

    Tip

    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

    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
    tasks to complete the migration and the setup
    o
    of 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")

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

    Info

    Be aware that some available app features may be located

    and

    or be named in a

    different manner.  In cloud

    differently in cloud. For example

    • Page Activity is available as

    Workflow History

    • Document Activity through the page tools menu

    • space administrators access the space app configuration in Space

    Settings>Content Tools>Document Management 

    Migration Guide

    Page TreestartDepth1

    • 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.