Data transfer from a cloud instance to another cloud

[Devarajan Mani]

While using the Data transfer option under Data Management in https://admin.atlassian.com to transfer a space from a cloud instance to another cloud instance, the custom fields and schemes are getting duplicated as shown below

Scheme: Default notification scheme ---> Default notification scheme (Migrated)

Custom field: Action Required ---> Action Required  (Migrated)

What could be the reason?

Thanks in Advance

Dev

[John Funk]

Hi Dev - I suggest you check out the Revyz Configuration Manager for Jira (configurations only) or the Revyz Command Center for Jira (configs AND data). You can do a free trial and do your move. It will NOT duplicate the names of the configuration components (fields, statuses, etc.). 

[Hana Kučerová]

Hi @Devarajan Mani ,

the configurations need to be exactly the same in the both sites. If they are not and they use the same name, the new migrated scheme from the source site is renamed to Original name (migrated).

[zoltanersek _outpostlabs_dev_]

yep, those are always annoying, watch out for the naming as @Hana Kučerová suggested

[Jason Krewson]

Hello Dev!

I believe this is a known behavior, you can find information on this at Jira Cloud Migration Assistant duplicates and tracking entities 

From the page:

How the Jira Cloud Migration Assistant works

We're rolling out changes that will allow the migration assistant to check if entities are identical – they have the same underlying properties. Learn how the migration assistant merges identical entities

The Jira Cloud Migration Assistant is non-destructive, so it will save a record of each entity (e.g. workflow or custom field) it migrates for the first time. In subsequent migrations to the same cloud site, the migration assistant will check to see if it already has a record of that entity.

• If an entity in your migration has the same name as an entity in the cloud site, and wehave a record of migrating it, we will link your data to the existing entity in the destination site. We will not re-migrate this entity.

• If an entity in your migration has the same name as an entity in the cloud site, and wedon'thavea record of migrating it, we will modify the name by adding (migrated) to avoid duplicates and ensure there's no data loss (we cannot guarantee that a field with the same name is exactly the same field). For example, an entity called Custom field A will be renamed to Custom field A (migrated) after migration.

[Devarajan Mani]

Hi Jason,

Thank you for your reply. Will JCMA work for cloud to cloud migration?

For Example: 

I have two cloud sites (abc.atlassian.net and def.atlassian.net) I want to move a space from one site to another without duplications. Please suggest a solution for the same.

Thanks in Advance

Dev

[Shubham Yahoo]

Hi Dev,

For C2C migration the option is Data transfer which works in backend same process as jcma, basically if you would like to avoid duplication rename the source site configuration with some suffix like default scheme-  Abc 

and the migrate the space from source to target!

this is required when you have different properties with same name for configurations!

if you have same settings it will auto merge to same name configuration, which is not most likely condition hence best option is to rename duplicated pre/post migration and if required to delete migrated one and use existing on target then reassign!