Plan your Cloud migration
Documents to help you prepare to migrate your Atlassian Server products.
Soft limits are data size recommendations to help you assess the impact of your migration and make decisions about your cloud-to-cloud data movement. We base the soft limits on first-hand experiences dealing with some of our largest customers, but they might not represent every organization’s experience.
Some things to know before you plan a migration
We have observed a higher success rate with migrating cloud-native projects within these soft limits. We recommend migrating all projects with cloud-native data and then moving the other projects.
Cloud-to-cloud migration is currently in beta. This feature may function differently than a generally available feature and may have less scope of functionality. Some issue fields, configurations, and other project types are not yet supported.
In the table below, we’ve described the performance and stability impacts we’ve observed in a single migration and recommended actions you can take if you suspect you fall outside the soft limits.
Content type | Number of projects per migration plan |
---|---|
Soft limit | 200 projects |
How to find this number | Use this link to find all the projects in your migration - https://<sitename>.atlassian.net/jira/projects |
Impact | We've observed these problems when above the soft limit:
|
Recommendations | If you have more than 200 projects per migration plan, we recommend migrating in batches of 200 projects each. |
Content type | Amount of text in the comments field |
---|---|
Soft limit | 32K (32767) characters in the comment field |
Impact | We've observed these problems when above the soft limit:
|
Recommendations | If you suspect your projects exceed this limit, contact support |
Content type | Number of attachments |
---|---|
Soft limit |
|
Impact | We've observed these problems when above the soft limit:
|
Recommendations | If you suspect your projects exceed this limit, contact support |
Was this helpful?