Migrate from Datacenter macro to cloud

How it works

The migration can map schema, object types, attributes, and optionally the object instances, but this requires the old datacenter key to be part of the object.

The flow consists of these steps: export the schema from the datacenter and upload it to the asset macros migration page in the cloud.

This document does not cover how the datacenter key is assigned to the object in the cloud instance for object-to-object mapping.

Groovy Schema Scripts

Step 1. Grant who can perform migrations

1. Go to Apps → Asset Data Studio

2. Click on Setup Connections

3. Click on Migrations tab.

4. Add the users that shall be able to perform the migration from dc to cloud.

Step 2. Export schema definition from datacenter

1. Download the export script to get the old schema, object type and attributes ids.

2. Put it in the Assets script folder on you Jira datacenter instance, normally located at /var/atlassian/application-data/jira/plugins/assets/groovy_scripts

3. Navigate to View and run scripts in the Manage Apps → Assets section

4. Load the script dc_export_schemas.groovy

5. Optional provide a Issue key to attach the result to an issue or leave blank to get the output only on the Jira server. Default directory is the /tmp folder.

6. Click Test Script button to run it.

Open

Step 3. Migrate Confluence pages from datacenter macro to Asset Data Studio macro

Open

1. Go to Apps → Asset Data Studio

2. Click the DC Migration tab

3. On the General tab

   Open

   

   1. There are two subtabs: Configuration and Mappings

   2. On Configuration

      1. Specify the optional attribute name of the cloud attribute holding the old datacenter key. Use this for migration to look up the new key if the configuration points directly to an object key.

      2. Select the dcKeyFormat: ID or PREFIX+ID.
         ID: object number in the datacenter instance, e.g., 134.
         PREFIX+ID: object key format, e.g., MYKEY-134.

      3. Select the connection to build the mapping table.

   3. On the Mappings subtab
      
      

      Open

      

      1. Upload the dc schema definition.

      2. Click Save to build the mapping table.
         Default attributes like, Key, Name, ObjectType, Created, Updated will not be mapped to any id it will use the default values instead.

4. On the Migrations tab

   Open

   

   1. Create a new migration.

   2. Name it as you prefer.

   3. Select spaces to convert or all.

   4. Click Save draft or Run.

   5. Run and wait for the migration to complete.

Mapping of the views

Open