This use case describes how you can migrate while keeping the the old and new Jira instance in sync. This can be helpful when:

  • You are not migrating all your projects at once and thus want both systems to have the same data available

  • You are not migrating all your users at once, and thus users might update the wrong (old)project

  • You want to use the old (server) instance for searching

Backbone helps in automatically keeping issues up to date. When you are looking for an issue on server, you can be sure to find the most relevant information on the ticket. Next to that, on the server ticket you can find a link to the new cloud issue, which makes it easy to navigate between the two. Therefore, Backbone helps out in smoothing the transition between server and cloud.

Configuration Guide

  1. Migrate to cloud with the Jira migration tool

  2. Restrict your server projects so no one (except the Backbone sync user) can make any edits

  3. Create a synchronization between your server and cloud project

  4. Configure the sync
    1. Set the issue type mapping to bidirectional (this will be changed later but is necessary for step 5)
    2. Set the field mappings, attachments, comments and workflows to be unidirectional
    3. Save your configuration but don't start the sync yet!
  5. Pair your issues automatically based on the issue key

  6. Set the issue type mapping to unidirectional and save the configuration
  7. Start your synchronization

From this point, all updates made on the cloud project will also be synchronized to the server project.

Good to know

  • Keep the sync info panel enabled. With the sync info panel you can also find the related new issue.

  • Make use of the correlation field Id in the advanced settings. This way a custom field can be set with the new issue key. 

  • Create a project banner to inform your users about the moved issue on Server.