JCMA duplicates all schemes and custom fields

[Lucie Mlčáková]

Hello. We tried to migrate one of our projects from Jira cloud SANDBOX to the Jira cloud PRODUCTION, using Jira cloud assistant. Despite the schemes and custom fields had the same titles in both instances --> JCMA creates duplicated schemes and custom fields. It duplicates the scheme and renames it with (migrated) word in the brackets. The same with custom fields - they are all duplicated.
Is there any way how to avoid these duplicities?

[Sanjen Bariki]

Hi @Lucie Mlčáková ,

Welcome to Atlassian community!

In the C2C migration, all the scheme and other configuration will be duplicate name If that name already exist in the target cloud site So If you want to remove the Duplicate word from the fields and others then you can directly connect with Atlassian Migration team to remove that word.

Note :- In migration, If the same name already exist in the target site then migration entity will create a new one and add the duplicate word in the field end

Regards,

Sanjen Bariki

[Taranjeet Singh]

@Sanjen Bariki I believe that the duplicated entity has the same name with the word "(migrated)" appended to the name, not the word "duplicate".

@Lucie Mlčáková I think for now, if it is just for one project, you can merge the duplicate entities manually with the original entities (i.e. change the configuration of the migrated project to use the original entities instead of the duplicated entities, if they are exactly the same) in Jira Cloud production and then delete the duplicate entities after making sure they are no longer attached/linked to any of the projects or their configuration entities.

In order to avoid this in future, make sure to go through the migration documentation of Jira Cloud-to-Cloud migration feature to ensure that this is the expected behavior of migration. If not, then make sure that the properties of the configuration entities with the same name are also exactly the same in both the source and the target Cloud sites otherwise the duplicate entities will still be created by the migration.

I hope this helps!

[Sanjen Bariki]

Hi @Taranjeet Singh ,

Thanks for the clartification on it @Taranjeet Singh .

Agreed.

Regards,

Sanjen Bariki

[David Day_ Appcento]

Hey Lucie, this is an old thread but just wanted to comment as we recently saw this issue. We hit the exact same issue during our sandbox to production migration and it was genuinely frustrating to see every single scheme and custom field duplicated with that "(migrated)" suffix.

Just to confirm what you're seeing is actually expected behavior from JCMA's side. When the tool encounters entities in the target site that share the same name as ones being migrated, it doesn't overwrite or merge them automatically. Instead, it creates new copies to avoid accidentally overwriting anything that might already be in use. It's a safety measure, but yeah, it leaves you with a mess of duplicates to clean up manually.

We ended up going through and merging the duplicates by hand for our critical fields, which took some time. For less important fields, we just archived the migrated copies and kept the originals. If your instance is anything like ours with hundreds of custom fields, it can be a slog though.

We did end up creating a script and eventually an app Migration Field Cleanup for part of our cleanup process, which helped automate some of the heavier lifting. Happy to share more details if you're interested, just let me know.
Hope this helps point you in the right direction!