Versions Compared

Old Version 1

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.

0

Image Removed

What is migrated to Cloud? What is not migrated to Cloud?

Excerpt

Insert excerpt
_migration common assets
_migration common assets
namewhat_is_migrated_graphic
nopaneltrue

0What is migrated?

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

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

prior to migration

before migration.

In the cloud site

Panel
bgColor#E3FCEF

Each A workflow in the server instance can be translated to cloud-compatible JSON code using the /wiki/spaces/AWPD/pages/617489050 Workflow Translator for Cloud option in the workflow builder (from Comala Document Management v6. 17.10+). The code can be copied and pasted to the workflow Code Editor 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 site space.

Product differences

Note

There are also a number of feature several product differences between the server and cloud apps.  

For example

,

 will have

  •  have different

functionality

  • functionalities compared to those bundled with the server app

.

In addition,

  • some available app features may be located and named

in a different manner. For example, in cloud

  • differently

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

Workflow History

  • Document Activity through the page tools menu or the workflow popup ellipsis menu

cdmc_wf_popup_ellipsismenu_documentactivity.pngImage Added

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

Management 

  • Management

cdmc_documentmanagementdashboard_bundledworkflows_all_inactive.pngImage Added

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

Support

Info

Please feel free to raise Raise a support ticket with for your migration from our support team.

FAQ Migration Planning

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