Does Jira Cloud-to-Cloud data transfer preserve the original numeric issue.id values, or does it generate new issue IDs on the destination site? We need to know whether integrations relying on issue.id can continue working without ID remapping.
Welcome @Vitalii Starshinin
No, Jira C2C migration doesn't perserve issue.id values. It generates entirely new auto-incremented numeric database IDs on the destination Jira Cloud site.
Thanks for the clear answer, Nikola. Vitalii, it is worth saving a simple mapping of the old issue key and numeric ID before you move, then switching the integration to use the issue key instead. A small test move first should show what needs remapping before the full migration.
One integration risk to add to the remapping advice: an old numeric ID may also exist on the destination site but refer to a completely different work item. A successful API response therefore isn't enough to prove the integration found the migrated item. For the cutover, I'd keep a reconciliation table with source site + source ID + source key, then destination site + destination ID + destination key. On the destination, resolve the expected key with GET /rest/api/3/issue/{issueIdOrKey}, confirm the returned key/project matches the migrated record, and store its destination ID. If the migration plan renames any keys, establish that key mapping first rather than assuming they stayed the same. Jira's Get issue endpoint accepts either ID or key and returns both: https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issues/#api-rest-api-3-issue-issueidorkey-get Before allowing writes, I'd validate a small migrated sample against that table and deliberately test an old ID that exists on both sites. Keep the source/destination site in the integration's identifier too; neither the number alone nor the key alone identifies a work item across multiple Jira sites.
Important points covered in the above answers :) One additional point to consider is before assigning or using a mapped numeric ID on the destination site, verify that the ID isn't already assigned to another issue. Maintaining a source-to-destination mapping and validating the migrated records before updating integrations can help avoid incorrect references.
For larger Jira migrations or instance consolidations in future, @Vitalii Starshinin, you may consider this migration tool that can help manage data migration and reconciliation, making it easier to account for these dependencies during the transition.
Hope it helps!
==
It looks like you're new here. Sign in or register to get started.