Migration Between Data Center Sites

1

On target site

2

Install the Snapshots App and configure the application link with Jira

3

Using Atlassian native tools to migrate to the new site

Use Atlassian tools to transfer Confluence spaces and Jira projects to the target site.

If you are migrating several Spaces, plan to migrate all of them in one flow. The Snapshot migration step will transition all the snapshots on the site in one go- so its advisable to migrate snapshots after all spaces and projects are migrated.

💡 At this stage, on the Target site: migrated pages with Snapshots will show that Snapshots has no data. Leave them like this- the snapshots migration tool will bring the data to those Snapshots.

4

On source site

The steps on the source site should be carried out at the same point of time as when the Space export is done, to ensure the Atlassian backup and the Snapshots backup are consistent with each other.

5

The tab: Export

Download the snapshots export file

A zip file is downloaded.

The zip contains two files:

• snapshot-migration.json: This is the export of the snapshots database.

• jira-data-migration.json: This file lists all the Jira custom fields that are used in snapshots across your source Confluence. It is likely you will need to modify it when you migrate the data to the target Confluence (see more in the next steps)

6

On target site

7

Prepare the Jira metadata export (json file) for the migration

If Jira projects moved to a new site, prepare the Jira metadata export file for the migration. This file was generated on the source Confluence site in previous steps, and it needs to be augmented with data about the custom fields in the target Jira.

1. Open the file and review the list of custom fields that are used by snapshots.

2. Each customfield entry in the json file has this element

   1. “newJiraId”=””
      

3. For each custom field in the json file:

   1. Find the equivalent custom field in your new Jira site.

   2. If the custom field id on the new Jira is identical to the one on the old Jira: you can leave the field “newJiraId” in the json file empty (or complete with the same id)

   3. If the custom field id on the new Jira is different from the one on the old Jira: complete the field “newJiraId” accordingly.

4. You do not need to update any other field or element in the json.

In this example, two custom fields are appearing in Snapshots:

1. The custom field “Approvers” retained its id, so the newJiraId field is left empty.

2. The custom field “Comments_Automation” has a new id in the new Jira. That id was added manually by the administrator who carries out the migration.

{
  "fromJiraHost": "https://vdxtest.atlassian.net",
  "fromJiraCloudId": "a7ceb685-a4a1-4795-b2e0-5d6a24caba98",
  "customFieldsMapping": {
    "customfield_10003": {
      "oldJiraId": "customfield_10003",
      "oldJiraName": "Approvers",
      "newJiraId": ""
    },
    "customfield_10076": {
      "oldJiraId": "customfield_10076",
      "oldJiraName": "Comments Automation",
      "newJiraId": "customfield_10106"
    }
  }
}

💡 If a custom field has a new name in the target site, that new name will automatically appear in Snapshot- when the first Snapshot data (for that macro) is taken at the new site.

8

The tab: Import
Upload the two files:

• Cloud migration data: snapshot-migration.json--> This file is not modified manually. It is uploaded exactly as it was downloaded in the Source system

• Custom fields data: jira-data-migration.json--> this is the modified file from the previous step

This file is not modified manually. It is uploaded exactly as it was downloaded.
After this step Snapshot feature will be restored:

1. The Snapshot table will be populated

2. The DIFF feature will show the complete history of the Snapshots.

3. When reviewing historical versions of the page, the correct snapshot data is shown.

4. When taking a new Snapshots, data will be retrieved correctly (including from custom fields)

5. Stickers existing in the source file are retained in the migration.

1

Saved diff view are not included in the migration

Please contact us ( support@radbee.com ) if this is required for your migration

2