Welcome to the Atlassian Community!
A migration, done properly, will not need to worry about custom field IDs. The only type of migration that would is where you're trying to do it with SQL, directly amending the database, and there is no question that this is the worst possible way to do any migration and you should never use it.
Your migration/merge should be done by exporting and importing issues. There are many options for doing that, but none of them use the IDs in the transferred data, they all map them to use existing data or create new ones.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Malli - Welcome to the Atlassian Community!
No, you should not try to change those as they are connected in many places. What are you trying to accomplish that you would need to change the ID of a custom field?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
we are planning to merge two different instances ,is there any chance that we face issue related custom field ID's, status ID's or Transition ID's
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.