Incremental migration to Jira Cloud

[crprivitera]

We are currently running Jira Server v8.6.1 with ~75 active projects and ~300 active users.  The Jira Migration Assistant recommends "Choose what to migrate" but Atlassian recommends a "Lift and Shift" method for communities with less than 10,000 users.  We have been running Jira Server for many years and our projects are highly customized.  As such, I would prefer to migrate our projects over time as opposed to all at once.  That means that we would migrate some projects to Jira Cloud while others continue working in Jira Server until it is their turn to migrate.  Repeat until all projects are migrated (probably over the course of a couple months).  The documentation suggests that this is possible but has anyone actually done it?  If so, did you encounter any pitfalls or regrets about this approach?   

[Jehan Bhathena]

HI @crprivitera ,

The "Chose what to migrate" option works well if you're not sure of what your projects will behave like in the cloud (since a few customization and plugins are not available on Cloud), the biggest task you'll face when you migrate multiple times is the creation of duplicate admin entities.

With each migration you'll be creating a new custom field, an associated scheme, workflows etc. This duplication will have to be cleaned up (or is at least suggested to), if prior to full fledged usage on the Cloud, else you'll end up storing the same information across a different set of fields and configurations.

PS: One app that can help manage configurations on the cloud is https://marketplace.atlassian.com/apps/1231935/revyz-configuration-manager-for-jira?hosting=cloud&tab=overview