How can ACLI help with migration

ACLI automation capabilities support the automation of tasks in pre and post migration activities.

Depending on the size and the complexity of your migration, you might want to use tools designed to carry out complex migrations

\uD83D\uDCD8 Migration Tools

Migration tools that you may want to use are:

Appfire Configuration Manager for Jira (CMJ)
Atlassian Confluence Cloud Migration Assistant (CCMA)
Run CLI for Jira
Run CLI for Confluence

CCMA allows you to migrate Confluence from server to Cloud.

Confluence migration from server to server is not possible.

CMJ allows you to migrate a Jira instance both to server or to Cloud.

ACLI Automation Capabilities for Migration

ACLI Automation capabilities complements other tools in preparing for migration, staging and testing activities.

For example, as part of the migration strategy, you want to audit your content (analyse and rectify). Once you established what you have, you decide the content that you want to remove from migration (old and/or harmful files). Equally, after migration, you want to ensure that all the required content was migrated in the correct format and with the new naming convention and architecture.

You can leverage ACLI capabilities, using Run, Export ,copy actions and more to bulk automate across operations, as shown in General for all applications, Confluence-specific actions and Jira-specific actions.

General for all applications

All ACLI applications provide a set of actions that are useful for migration purposes, as follows:

Multiple Run actions that allow bulk automation across many application objects and generic support:
1. runFromCsv - run actions for each row
2. runFromSql - run action for each row of a database query
3. runFromJson - run actions based on JSON data like arrays
Database support for all list actions - the ability to automatically create or update database tables from application data.
The data is useful for analysis for planning migrations and understanding your application data.
For example, analyzing users, groups, and space permissions or looking for obsolete data that can be removed before migration.
Use database support to drive migration automation with ACLI actions (and runFromSql) or other tools that use databases.
-> Database support is particularly useful in cross application migration where data needs to be restructured for the target application.
Test staging and migrations with ACLI script to retrieve data and verify against expected results either manually or in formal tests using Gint. Also, ad-hoc testing and automations to fix up migration errors to avoid error prone manual updates.
Help with instance management for test and staging instances and applications using UPM actions like getAppList , installApp , addLicense, runFromAppList.

In addition, both Confluence and Jira provide specific actions that can be used in migration activities, as shown in the Tables Confluence actions and Jira-specific actions.

Conflue nce-specific actions

Action type

Use

Run

runFromSpaceList run actions for each space. Defaults to global spaces only. Filtering available like for getSpaceList.

runFromContentList run actions for each content item found from a content search.

runFromAttachmentList Run actions for attachments that match the same conditions as getAttachmentList.

@all can be used as a special value for the space parameter.

Use a variety of Run actions to minimise script writing.

exportSpace

restoreExport

Actions for managing space data

exportData

Action for exporting some constructs as ACLI scripts that can be modified and used to re-create on other systems.

Supported data types include:
SPACE, PARTICIPANTS, USERS, and GROUPS

Copy

copySpace to copy entire space and (optionally) contents

copyAttachments

copyBlog

copyComments

copyLabels

copyPage and copyPageChildren

copyPermission

Extensive Copy type of actions including support for targetServer to copy data to another server.

modifyPage

modifyBlog

Modify actions to repair text data with regex find and replace capabilities.

Modify actions are useful for repairing links in data and can be used in combination with database (runFromSql) to drive high volume changes.

Jira-specific actions

Action type	Use
`Run` `runFromProjectList` `runFromIssueList` `runFromVersionList` `runFromComponentList` `runFromFieldList`	Use a variety of `Run` actions for Jira to minimise script writing.
`archive`	Archive related actions to help with controlling what might need to be migrated.
`exportData`	Action for exporting some constructs as ACLI scripts that can be modified and used to re-create on other systems. Supported data types include: `PROJECT, PERMISSIONSCHEME, PARTICIPANTS, USERS, and CUSTOMFIELDS`
`import` `importWorkflow`
`Copy` `copyAttactments` - copy all attachments from one issue to another include on a target server.	Type actions including support for `targetServer` to copy data to another server.
`updateIssue` `modifyFieldValue` `updateComment` `updateCustomField` `updateCustomFieldOptions`	Modify issues actions repair text data and links in data with powerful regex find and replace capabilities, and can be used in combination with database (`runFromSql`) to drive high volume changes.