Versions Compared

Old Version 6

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.

Insert excerpt
COMALAMIG:_migration common assetsCOMALAMIG:
_migration common assets
namewhat_is_migrated_graphic
nopaneltrue

0What is migrated

to Cloud? What is not migrated to Cloud?

?

Table of Contents
minLevel3
maxLevel3
outlinefalse
styledisc
typelist
printabletrue
Excerpt
namewhat_is_migrated_what_is_not_migrated

What is migrated to Cloud?

Only the following app data is migrated with the Confluence Cloud Migration Assistant

  • current workflow status of each page

  • an entry in the workflow history

Any

  • W

In each cloud space after migration, a document that had a workflow applied while being in server,  in each cloud space will have has

  • a workflow state byline lozenge added to the content in cloud showing the current workflow status

  • an entry on each document’s workflow history saying "Document has changed to 'xxx' state"

Migration adds the last workflow state in the server an as a custom contents attachment to the migrated cloud document in cloud.

These will be are present as long as the document has been properly is successfully migrated using the Atlassian Migration process and the linked user exists in the cloud site.

What is not migrated to

cloud

Cloud?

The following is not included in the migration

  • workflows 

  • full page activity (the workflow

history

  • events and activities on each page)

  • expiry date(s)

  • assigned approvers

  • assigned read confirmations

  • record of

which

  • the last page version

was the

  • for a workflow with a final state

any

  • metadata set or retrieved by get-metadata and set-metadata macros and workflow parameters

When migrating to Cloud

  • the Comala Document Management for Server app is not migrated

  • app page report macros are not migrated

Pages with restrictions identified in the Atlassian Migration Assistant App vendor checks screen must have the restrictions removed before migration.

In the cloud site

Panel
bgColor#E3FCEF

A workflow in the server instance can be translated to cloud-compatible code using the Workflow Translator for Cloud option in the workflow builder (from Comala Document Management v6. 17.10+). The translated workflow template is added to the cloud site by copying the translated code from server and pasting it into the code editor in a cloud space.

Product differences

Note

There are also several product differences between the server and cloud apps.  

For example

In the cloud app

  • workflow triggers have a different range of trigger events, conditions, and actions from the server app

  • Page Activity is available as Document Activity through the page tools menu or the workflow popup ellipsis menu

cdmc_wf_popup_ellipsismenu_documentactivity.png

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

cdmc_documentmanagementdashboard_bundledworkflows_all_inactive.png

  • the workflow builder visual editor (and the code editor) are only accessible in the space document management dashboard for a custom workflow

cdmc_documentmanagementdashboard_customworkflowadded_visualeditoricon_highlighted.png

Support

Info

Raise a support ticket for your migration from our support team.

FAQ Migration Planning

Filter by label (Content by label)
showLabelsfalse
showSpacefalse
cqllabel = "plan_migration" and space = currentSpace ( )