Impacts of doing a C2C migration

[Hansika Wijenayake]

Hey all,

We are planning to do a C2C migration. Our env structure is as below. Please note that these 2 envs are from two different organizations.

1. A = Source PROD env

2. B = Destination PROD env

We are planning to try out a TEST migration first and for it we created two TEST envs based on the above PROD envs. So these two TEST envs are also from two different organizations.

As we are aware, person who does the migration needs to be an org admin of source and destination env. Currently we have one org admin per each PROD env. All technical migration activities are done by a seperate internal resource. If we appoint the internal resource as an org admin, we need to do the said change in the PROD env also, becuase TEST envs were created based on the PROD envs.

If we appoint our technical resource as an org admin temporary in PROD, and if we let him to run the TEST migration, will it create any kind of impact to our production sites?

Cheers,

Hansi 

[Pramodh M]

Hi @Hansika Wijenayake 

If you have a premium plan create a sandbox environment or create a new trial site and follow the below documentation to migrate the data

https://support.atlassian.com/migration/docs/perform-a-cloud-to-cloud-migration-for-jira

Record the steps while performing a migration

Here's the record of what is migrated

https://support.atlassian.com/migration/docs/what-migrates-in-a-cloud-to-cloud-migration-for-jira/

Thanks,
Pramodh

[Hansika Wijenayake]

Hey Pramodh,

Thank you so much for the feedback. We have a SandBox env created and it is in used for some operational activities, so it cannot be used for the moment. That's why we had to create 2 new TEST envs

Cheers,

H