You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
We are using the Cloud-to-cloud migration feature migrating jira projects
Which is not applicable for
Is there any known limitations or restrictions?
It looks like:
- automation rules (could be solved via export-import)
are not transferring.
Could you complete the list of restrictions according to your experience please?
Any advises of how to perform these additional migration steps will be appreciated.
Hi @Alex Kiselev,
You can find the list of what gets migrated and what doesn't with the cloud to cloud migration assistant in this support article.
For team managed projects, you can either migrate them to company managed before your migration or manually create a project in the target site and use csv export / import to transfer your data. That last option is also a way to migrate JSM data.
For a number of items that can't be migrated with the assistant, the article I referenced does list what you should do (e.g contact the vendor of marketplace apps, ask users to update their avatar, ...). For other items the solution is very often to fix things manually pre or post migration. For those things, make sure to document very well what you need before the migration, test your migration, adapt and document again and then follow your plan when migrating for real in your production environment.
Hope this helps!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.