SEE ALSO:
Should you migrate your Jira Server to Cloud or decide to split a profile into two independent profiles for easier management, our migration tool will help with transferring synced data to a new profile.
Beta migration support currently has limitations, and it is not available publicly by default. It can be enabled by support upon request.
Limitations of beta version
The migration is designed to update synced entities in order to support the switch to a new profile.
- Only migration of entities is supported in beta version. Attachments, Comments and Sprints will not migrate to new profile.
- Entities will migrate if the same issue Keys are kept in the Jira of the destination profile and type mappings of both profiles match.
- Beta version is enabled for Jira integration only.
Public release after beta is not yet planned on the roadmap but will support comments and sprints. It will also work for Azure DevOps to Targetprocess integration and Targetprocess to Targetprocess integrations.
Use Case 1: Departments / Teams processes start becoming different and field mappings are difficult to manage in one profile. Considering that teams work independently, two separate profiles may be preferred.
Use Case 2: Your Jira is moving from Server edition to Cloud, and you do not want to move all projects with Jira server backup that will be restored in Cloud. If you use Jira Cloud Migration Assistant (JCMA), then all entities will transfer to Cloud keeping the same Keys.
In this case, Attachments, Comments and Sprints that do not have Jira Keys will not be supported in the migration – their mappings are tied to IDs and those IDs change after migration to Cloud with JCMA.
Recommendations for the migration from Jira Server to Jira Cloud with the Targetprocess beta migration tool:
- Create new profile, copy mappings, and adapt your JS mappings, if needed, to Jira Cloud API specifics.
- Test sync of the new profile with test project scopes and filters. Mind that if Jira Cloud has a webhook for the new profile, then all new or modified Jira issues that match profile scopes will be created as new in Targetprocess if auto-push is enabled.
- Optional, relevant for Jira migration from Server to Cloud. Disable auto-push in the new profile for the project scopes that are planned for data migration from the Jira Server.
- After Jira Server projects are moved to Jira Cloud, Targetprocess migration can be started. Go to Integrations > Integration profile > Migrate to new profile. Enter the JQL filter for the current Jira instance and move to new profile with only issues that match the JQL filter. If you choose the destination profile without additional JQL filter, then all issues synced with current profile will be searched for in the Jira instance of the destination profile and attempted to switch their sync to new profile mappings.
5. As soon as migration is completed successfully, remove scopes from initial profile to exclude cross-profiles sharing (if split is within one tool and two profiles). Enable auto-pull in new profile.
Error details explaining failed or impossible migrations you can find in the messages log
Still have a question?
We're here to help! Just contact our friendly support team.
Find out more about our APIs, Automation Rules, Mashups and custom extensions.