Limits for transferring Jira data
Copy limits help reduce failures and delays when transferring large amounts of data.
For organizations where Units is activated, enforced limits apply to your transfer selection. You can’t proceed while an applicable limit is exceeded and will have to adjust your copy scope accordingly.
For organizations where Units is not activated, these new enforced limits do not apply. The soft-limit recommendations below continue to apply.
In the table below, we’ve described some soft limits. We also describe the impact on performance, stability, and success when moving data more than the recommended soft limit in a single copy plan. We recommend actions you can take if the size of your data falls outside the soft limits.
Our soft-limits are based on first-hand experiences dealing with some of our largest customers, but they might not represent every organization’s experience.
Hard limits after units activation
These hard limits apply only to organizations where unit is activated. You can’t proceed with a transfer that exceeds an applicable limit. Reduce your selection or contact Atlassian Support to discuss your options.
Area | Hard limit |
|---|---|
Jira project scope | 200 projects per run. |
Confluence scope | 200 spaces per run. |
Media and attachments | Fewer than 5 million files. |
Concurrency | Jira: 3 on Standard shards and 8 on MC shards. Confluence: 6 concurrent space migrations. |
Assets | Object count: 2 million. Object history count: 22 million. One concurrent export/import; move reference-based Assets data rather than all schemas. |
Users and groups | Fewer than 150,000 users and fewer than 60,000 groups. |
The transfer flow checks the number of selected projects or spaces, attachment counts, and users and groups. Follow the limit messages shown for your transfer.
A project or space that exceeds its attachment limit may be unavailable for selection. If your combined selection exceeds a project, space, user or group limit, reduce the selection before continuing.
When you select Next after choosing projects or spaces, the transfer flow checks users and groups. If a limit is exceeded, deselect some projects or spaces, then select Next to check again.
Some user and group copy options may be unavailable because they exceed a copy limit.
Number of projects per copy plan
Soft limit | 200 projects |
|---|---|
How to find this number | When you select projects while transferring data, you can see the total number of selected projects at the bottom of the Select projects page. You’ll also be able to see the number of selected projects on the Review your selections page. |
Impact | When you transfer more than 200 projects at once in a single copy plan, some projects may fail to copy. |
Recommendations | We recommend copying projects in batches of 200. If your transfer exceeds a copy limit Reduce the selected scope or divide it into smaller copy plans where possible. If a single project or space exceeds a limit, or you can’t reduce your selection sufficiently, contact Atlassian Support. Include the source and destination URLs, the limit message, the affected projects or spaces, and the copy-plan ID if one is available. Support will assess your transfer and the available options. Contacting Support does not automatically raise a limit. |
Amount of text in the comments field
Soft limit | 32K (32767) characters in the comment field |
|---|---|
Impact | When you transfer data you’ve migrated from the Jira Data Center or Server into cloud, these errors may occur:
|
Recommendations | If your projects exceed this limit, or if you see trimmed comments, contact support |
Number of attachments
Soft limit |
|
|---|---|
Impact | Copying data takes longer as the number and size of attachments increase. |
Recommendations | If you think the number of attachments exceeds this limit, contact support |
Was this helpful?