This site has moved to the integrated Appfire documentation and information site for our apps.

From February 2024 this site is no longer updated.

Take a look here! If you have any questions please email support@appfire.com

Manual migration tasks

Owned by Robert Alexander Marshall
Last updated: Sept 18, 2023
3 min read
1 Manual Migration Tasks | 1.1 User migration | 1.2 Page restrictions | 1.3 Install Comala Document Management app | 1.4 Workflow History/Document Activity | 1.5 Tasks after completing the Atlassian migration process | 2 Avoiding migrated user login issues | 3 Maintaining an audit history

 

Manual Migration Tasks

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 Comala Document Management workflow for each page

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

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

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

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

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

If workflow 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

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

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



Migration Process Steps

Â