Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Cloud-to-cloud migration using BETA feature limitation

Hi community,


We are using the Cloud-to-cloud migration feature migrating jira projects

Which is not applicable for

- team-managed




Is there any known limitations or restrictions?

It looks like:

- automation rules (could be solved via export-import)

- dashboards

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.


Thank you.

1 answer

1 accepted

0 votes
Answer accepted
Walter Buggenhout _ACA IT_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Apr 03, 2023

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!

Suggest an answer

Log in or Sign up to answer
Site Admin
AUG Leaders

Atlassian Community Events