Server (with Backbone) to Server → Cloud to Server (with Backbone)

This article guides you through the steps to take for the migration of a Server (where Backbone is configured) to server synchronization to a Cloud to Server (where Backbone is configured) synchronization.

Prerequisites

You are synchronizing to a Server instance which also has Backbone installed
You have configured/set up the synchronization on your instance
Only you are migrating your Server instance to Cloud
There are no errors in the troubleshooting tab of the configuration. If there are, please solve these first.

Things to Keep in Mind

You can't set up the synchronization on the Cloud side which means that your partner will need to set up/configure the synchronization
If you are syncing comments and want to sync them in the new migrated use case as well, some will be duplicated. We are working on a fix for this: BAC-1449 - Some comments get duplicated when the syncuser changes Released

Migration Steps

Step-1: Export your synchronization data

Stop the original running synchronization
Export the synchronization config for this synchronization
Download the synced issue data for this synchronization (open the synchronization config and click ••• > Download synchronized issues)

Step-2: Modify exported data

Open the exported file you created in step 1.2
1. Change the order of the connectors, therefore put the "firstConnector" under the "secondConnector"
Open the file with the synced issue data created in step 1.3
1. Change the order of the connectors, therefore put the "firstConnector" under the "secondConnector"

Downloaded synced issue file

{
  "firstConnector": [
    {
      "id": 255,
      "connectorKey": "CON-48-PA",
      "localIssueKey": "PA-1",
      "remoteIssueKey": "PB-1",
      "firstSyncDate": 1603723138019,
      "lastOutgoingChange": 1603723222613,
      "lastChangeSeen": 1603723219588,
      "outgoingMessageSequenceId": 2,
      "lastIncomingChange": 1603723152692,
      "incomingMessageSequenceId": 1,
      "incomingChangesIgnored": false
    }
  ],
  "secondConnector": [
    {
      "id": 256,
      "connectorKey": "CON-49-PB",
      "localIssueKey": "PB-1",
      "remoteIssueKey": "PA-1",
      "firstSyncDate": 1603723142536,
      "lastOutgoingChange": 1603723147985,
      "lastChangeSeen": 1603723228249,
      "outgoingMessageSequenceId": 1,
      "lastIncomingChange": 1603723228308,
      "incomingMessageSequenceId": 2,
      "incomingChangesIgnored": false
    }
  ]
}

CODE

Altered synced issue file

{
  "firstConnector": [
    {
      "id": 256,
      "connectorKey": "CON-49-PB",
      "localIssueKey": "PB-1",
      "remoteIssueKey": "PA-1",
      "firstSyncDate": 1603723142536,
      "lastOutgoingChange": 1603723147985,
      "lastChangeSeen": 1603723228249,
      "outgoingMessageSequenceId": 1,
      "lastIncomingChange": 1603723228308,
      "incomingMessageSequenceId": 2,
      "incomingChangesIgnored": false
    }
  ],
  "secondConnector": [
    {
      "id": 255,
      "connectorKey": "CON-48-PA",
      "localIssueKey": "PA-1",
      "remoteIssueKey": "PB-1",
      "firstSyncDate": 1603723138019,
      "lastOutgoingChange": 1603723222613,
      "lastChangeSeen": 1603723219588,
      "outgoingMessageSequenceId": 2,
      "lastIncomingChange": 1603723152692,
      "incomingMessageSequenceId": 1,
      "incomingChangesIgnored": false
    }
  ]
}

CODE

Step-3: Create a new synchronization

Go to Project B and start a new sync with project A (on Cloud)
Import synchronization config that you exported and changed in step 1.2
Upload the synced issue data for this issues in this project that you exported and changed in step 1.3 (click ••• > Pair existing issues > Pair existing issues synced with Backbone before)
In the synchronization config, check every tab ('Issue types', 'Fields - mappings' etc.) for validation errors – these will appear in yellow warning boxes. These warnings can appear due to custom IDs (issue type IDs, field IDs, etc) being different in the new Jira instance. Find any errors and correct them.
1. Note: if you are using a user field mapping, make sure to set it to "User Passthrough Mapping (by email)"

Step-4: Start the synchronization

Start the new synchronization
In the new synchronization, trigger a resync in both directions (with only the summary field, so the resync doesn't take long). This is done in order to recreate the information in the Sync info panel.
Once you have verified everything is working correctly, delete the original synchronization. This will also delete the old information in the sync info panel.

Still Unclear? Reach Out to Us

If you need help with any of these migration steps, reach out to us via help@k15t.com.