Migrate large number of issues from Server to Cloud. Can we migrate data in stages?

[Tom Gross]

We have about 300,000 issues in JSM that we need to migrate from server to cloud.

Is there a way to batch up issues (lets say 50,000) and migrate them separately in stages?

[Michael Andolfatto]

Hi @Tom Gross , welcome to the Community!

Yes, the Jira Cloud Migration Assistant (JCMA) now supports migrating data from JSM projects so this is possible (if you are migrating multiple projects).

The plugin should already be installed on your Server instance (it is free and can be installed from the marketplace if not) and allows you to migrate project data from a Server instance to a Cloud instance.

Since projects are the scope, you can choose to move some (and their issues) now and then move others later. The only caveat here is if you are moving one large project with 300,000 issues. If so, you will have to do a different migration method such as CSV exporting/importing.

[mgalmes]

Hello,

I have another question about this. I need to migrate several projects with around 50,000 tickets each. Can I use the Atlassian migration tool? Do you know how long the migration process might take for 50,000 tickets? The issue with these projects is that they are currently in use, and we need to ensure service continuity. Thank you all very much.

Thank you so much in advance 

[Tom Gross]

Thanks for responding.

By doing a CSV export, don't you loose all the history?  It's just the basic issues, right? What about all of the attachments?  How would you migrate those?

I need to set expectations with the client on what they're going to get

[Michael Andolfatto]

Hey @Tom Gross , yes you will lose all history with the CSV migration. Only issue data (fields, comments, etc.) get migrated, issue metadata does not. Attachments can be migrated (please check this doc) but it's not always the most enjoyable process.

For your situation, an alternative may be to create a project specifically for migrations on the source site and to clone issues from the main project into the migrations project in batches based on the date created using JQL. It's definitely not an ideal method and may require multiple projects/move operations on both the source and target instances since JCMA likes to migrate unique workspaces only, but it is possible if this is a requirement on your side.