Versions Compared

Old Version 2

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.
Table of Contents
maxLevel4
absoluteUrltrue
excludeSee also
typeflat
separatorpipe

Excerpt

Manual Migration Tasks

Anchormanmigratetaskmanmigratetask

Due to differences in the Atlassian cloud and server platforms the migration of the Atlassian Migration Assistant will only migrate the following

  • the current workflow state data for each page

  • the user details for the change to the current state in the

Comalatech

  • Comala Document Management workflow for each page

You will need to install Comala Document Management Cloud in your cloud site.

You will need to undertake and check some manual tasks to complete the set of your cloud site. These tasks include

Table of Contents
maxLevel4
minLevel4

User migration

The migration of the actual users for access must be done as part of the Atlassian Migration Assistant. If the migration has not included the users then errors may occur when completing the space setup in cloud and applying your

Comalatech

Comala Document Management workflow.

Page restrictions

Any page with view or edit restrictions cannot be included in migration to Cloud with the page restrictions in place. You will need to temporarily remove the restrictions to allow migration of these pages to take place without any errors.

Tip

The migration pre-check in the Atlassian Migration Assistant includes a listing of pages in the migration with restrictions.

If you have a significant number of pages with restrictions please contact support.

Install Comala Document Management app

and enable migration

Prior to migration you will need to install the Comala Document Management for Cloud app.

Once installed, you must enable Server Migration in the Comala Document Management Cloud app global configuration.Image Removed

Simply move the Enable migrations slider to display the green tick

Image Removed

(info) If a migration process fails, you may have to disable and then re-enable migrations.

Workflow History

Tip

If using a custom workflow, you can use the server workflow builder Workflow Translator for Cloud to translate your workflow to cloud compatible JSON code. You can add this workflow to a cloud space by copying and pasting the translated cloud compatible JSON to the cloud app Code Editor.

The Workflow Translator for Cloud in server will not translate any workflow elements and parameters that are not directly compatible in cloud. If any are present in the server workflow, these elements, such as workflow triggers or some state parameters, are listed separately in the Cloud Translator.

Workflow History/Document Activity

Only the current state of a page with an applied workflow is exported as part of the Atlassian migration process. We

 do

 do not support migration of workflow history (also known as Page Activity or Document Activity). The workflow state is added as a file attachment to each document in cloud.

This state can be added to the content by initializing the workflow for the content in each space after the workflow has been applied.

If workflow

history

document activity is required for audit you may need to consider options of either

  • exporting this as CSV for each page

  • or running your legacy server instance as 'read only'

Tasks after completing the Atlassian migration process

Once you have enabled migration and undertaken the migration using the Atlassian Migration Assistant, to complete your cloud site you need to undertake tasks for

Child pages (Children Display)

Filter by label (Content by label)
showLabelsfalse
showSpacefalse
cqllabel = "manual" and ancestor = "13942587466"

Avoiding migrated user login issues

After the migration process has been completed it is recommended to exit and log in so migrated users are available (otherwise, the Cloud instance doesn’t recognize them).

Maintaining an audit history

(warning)

Note

If your organization is in a Compliance/Regulatory industry and you periodically get audited, then you will be required to keep Confluence on a Server running in read-only mode so auditors can review your previous Workflow History/Page Activity. The same goes for the Page Status.

You cannot migrate the full workflow history and page status to Cloud.

Info

icon

false

Please feel free to raise a /wiki/spaces/CDMCD/pages/13951991809

with the Comalatech Migration and Support team to help

to answer any queries you in planning the migration.

Please include with your request


oImage RemovedImage AddedImage Added