Repeat Jira Cloud to Cloud migration

[Petter Topp]

I'm about to Perform a cloud-to-cloud migration for Jira, but due to activity and changes in the source site, I'm wondering if a repeat of the initial migration will migrate changes?

IOW will a re-migration move changes on source site that has happened between the first and second migration?

This way we will not have any down time on the source system while I figure out if the new site is working (Need to migrate Confluence as well).

Br

Petter

[Walter Buggenhout · Accepted solution]

Hi @Petter Topp and welcome to the Community!

That is not how it works, unfortunately. You do not only migrate data, but also configuration, users, attachments and so on.

The idea is you migrate a project with its issues once in production and then you switch over to the migrated environment. You can choose to migrate a subset of projects e.g. today and other projects tomorrow, but if they share configuration items (schemes, fields, ...), you may end up with duplicate configuration in your cloud site that you'll need to clean up afterwards.

To test things out, it is best to migrate to a test instance first, verify if everything is as you expect, document the additional things you need to do to get everything in working condition and use that as a plan for your production migration (that's a very short and high level description of what you should prepare for).

Hope this helps!

[Petter Topp]

Thanks Walter for making this clear. 

However setting up a test instance feels quite daunting as we have set up a site with Azure AD with SAML SSO and on top of this is the matter of licensing - I guess that I will need set up at test site with at least a Standard license.

Are my assumptions correct?

[Walter Buggenhout]

A test site is free for 30 days. You can set up as many as you need, on the plan you want. But you should not set up SSO to that test site. You use it to validate the technical migration aspects.

From your questions, I get the impression that you have not reached out to Atlassian Migration Support. Definitely do so, because you may need technical support during or post migration that only Atlassian can deliver (e.g. to review error logs, fixing links between Jira and Confluence, ...). You can do so by raising a migration support ticket here. 

[Petter Topp]

Thanks Walter, I will take a few steps back and start with reaching out to migration support.

Best regards

Petter