Server to Cloud → Cloud to Cloud
This article guides you through the steps to take for the migration of a Server to Cloud synchronization to a Cloud to Cloud synchronization.
- You are migrating from your Server instance to a Cloud instance
- Your (new) Cloud instance has Backbone installed
- You are synchronizing to a Cloud instance which also has Backbone installed
- There are no errors in the troubleshooting tab of the configuration. If there are, please solve these first.
Things to Keep in Mind
- In a Cloud to Cloud synchronization, both partners have access to the synchronization
- You don't need a synchronization user anymore, this is replaced by an automatically created user "Backbone Issue Sync for Jira"
- 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
These steps assume the following setup:
- Project A - project that is migrated from Server to Cloud
- Project B - partner project already on Cloud
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: Create a new synchronization
- Go to (the new Jira Cloud instance for) Project A and create a new synchronization with Project B. Note: it's important to set the synchronization up on project A, not on project B.
- Accept the synchronization request in Project B on Instance B
- Import the synchronization config that you exported in step 2
- Upload the synced issue data for these issues in this project that you exported in step 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.
Step-3: 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 email@example.com.