Does the Jira Cloud Migration Assistant create new issue ids? (internal ids, not keys)

[Chad Crume]

Does the Jira Cloud Migration Assistant create new issue IDs? (internal ids, not keys)

I'd like to find out the answer to help plan our migration. We use FiveTran to sync Jira data into our data warehouse, with models that rely on the ID for joins. If the IDs change, the sync could require a full refresh of all issue data, and require a new mapping to the old IDs found in historic sync data.

[Nic Brough -Adaptavist- · Accepted solution]

Yes, it has to - the target system almost certainly already has issues with the ids the source system also has.

This is one of the reasons I always tell people not to use database access (I know FiveTran uses REST, that's a good thing), the ID is not the right thing to be keying your data models from.

[Chad Crume]

I figured, just verifying so we can scope work related to the migration. Thanks!