×

You're using an outdated browser

For a better experience, keep your browser up to date. Check here for the latest version.

Manual

Migrate a Backbone synchronization to a new Jira instance

Matthias Gaiser

Matthias Gaiser Last update: Oct 31, 2018

This guide explains how to migrate a Backbone synchronization from one Jira instance to another so that the sync works for the project(s) just as it did before migration.

Possible scenarios

You are synchronizing two projects on two different Jira instances. Let's call them Project A on Jira instance A, and Project B on Jira Instance B.

  • Migrate a synchronized project to another Jira instance
    The synchronization is configured in the Jira instance A. You want to migrate Project A to another instance, but after moving, you want Project A to sync with Project B just like before the migration.
    You should first migrate the project A as described in the Atlassian docs, then follow the steps below.
  • Migrate a synchronization from a workaround solution to a real one
    The synchronization is configured in another Jira instance, e.g. because you started to sync two cloud instances before Backbone officially supported it. Please follow the steps below.

Required steps

  1. Stop the original running synchronization
  2. Export the sync config for this synchronization
  3. Download the synced issue data for this synchronization (open the sync config and click ••• > Download synchronized issues)
  4. Go to (the new Jira instance for) Project A and create a new synchronization with Project B
  5. Import sync config that you exported in step 2
  6. Upload the synced issue data for this issues in this project that you exported in step 3 (click ••• > Pair existing issues > Pair existing issues synced with Backbone before)
  7. In the synchronization config, check every tab ('Issue types', 'Fields - mappings' etc.) for validation errors – these will appear in yellow warning boxes. These are called by custom IDs (issue type IDs, field IDs, etc) being different in the new Jira instance. Find any errors and correct them.
  8. Start the new synchronization
  9. 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.
  10. Once you have verified everything is working correctly, delete the original synchronization. This will also delete the old information in the sync info panel.
2x$versions.current.name
We use cookies to create a secure and effective browsing experience for our website visitors and to understand how you use our site (i.e. Google Analytics). For more information: click here.
Ok