Jira Cloud Migration Assistant

I have used Cloud Migration Assistant for a test migration before using it in production from Server to Cloud migration. Full migration was from Cloud [ project ] -> Server -> Another Cloud instance. My migration scenario was to migrate a single project ( 10 active users and 30 in active users from past and 4 user groups based on their role permissions ) out of 50 projects and 1100 ( 300 active users and 800 inactive old users ). Migration moves all users and group thought they are not used in single project you are migrating. You have to manually remove the users and groups before migration if you do not want them. Any options to avoid this would be very helpful. Overall, the migration was smoother than anticipated. I am yet to do real production migration. -- Completed Production migration as well. Few more points to consider when you are migrating few projects to existing cloud instance 1. You can not take cloud backups whenever you want. There is a 48hr gap between backups. Plan accordingly. Support was able to help me get over this quickly 2. Make sure your projects have custom Schemes, otherwise they may overwrite the existing field schemes etc and which will impact existing projects 3. For some reasons, User roles are duplicated with text (migrated) 4. If you tweaked Priorities, there are no custom priorities in Cloud. You may have to downgrade / other projects may have additional priorities 5. Ability to select users and groups for migration would be very helpful. 6. In some tickets ticket history is not showing, but comments and transitions is shown fine hence not a big deal. Overall, much smooth experience than anticipated.

This tool is a blessing. Thanks for providing such a handy support. Few suggestions 1. Provide some more migration checks - something like DB Integrity checker like find missing Priorities, Dangled resolutions etc. Every time we miss a check , I have lost approx. 2 hours redoing it. This is the very reason I have been spending my weekend as I prioritized saving time for my team by doing their migration over a weekend 2. Provide some way to do a stepped migration and do not let people go over the same steps again.E.g Give a choice to select User& Group Migration for each projects successively. Thats painful. How about using containers innovatively? 3. Provide additional migration supplement tools for removing unwanted METADATA before migration. That's very much essential 5. Provide Migration Information such as Start time, end time , Steps progress to user. 6. Start a CHAT / Interactive support during migration that having a sequential communication over Support portal Overall kudos! We look for a great migration experience

Thanks! This is awesome. One request, can you please add Jira Service Desk project support?

Its great to see this up and running! nice work to the team! There are optimisations that could do to be made to improve performance when used on large instances, and there is no current way to migrate projects of large AD backed on-prem instances as all the users and groups need to be migrated (this has been noted by the team and hopefully addressed soon).