Skip to end of banner
Go to start of banner

How can ACLI help with migration

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 18 Next »

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 and Jira

General for all applications

  1. Extensive Run type actions allowing bulk automation across many application objects and generic support like:

    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

  2. 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. More importantly, it can be used to drive migration automation using ACLI actions (and runFromSql) or other tools that can use databases. This is especially important in cross application migration where data needs to be restructured for the target application.

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

  4. Help with instance management for test and staging instances and applications using UPM actions like getAppList , installApp , addLicense, runFromAppList.

Conflue nce

  1. Confluence specific Run type action like runFromSpaceList, runFromContentList, runFromAttachmentList, and similar.

  2. exportSpace and restoreExport actions for managing space data.

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

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

    1. copySpace - copy entire space and (optionally) contents

    2. copyAttachments

    3. copyBlog

    4. copyComments

    5. copyLabels

    6. copyPage and copyPageChildren

    7. copyPermission

  5. Modify actions to repair text data with powerful regex find and replace capabilities. This are especially useful for repairing links in data and can be used in combination with database (runFromSql) to drive high volume changes.

    1. modifyPage

    2. modifyBlog

Jira

  1. Jira specific Run type action like runFromProjectList, runFromIssueList, runFromVersionList, runFromComponentList , runFromFieldListand similar.

  2. Archive related actions to help with controlling what might need to be migrations.

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

  4. import and importWorkflow actions

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

    1. copyAttactments - copy all attachments from one issue to another include on a target server.

  6. Modify issues, actions to repair text data with powerful regex find and replace capabilities. This are especially useful for repairing links in data and can be used in combination with database (runFromSql) to drive high volume changes.

    1. updateIssue

    2. modifyFieldValue

    3. updateComment

    4. updateCustomField

    5. updateCustomFieldOptions

  • No labels