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.
I need to use JIRA site import to migrate our instance to the cloud and I have a question about the checklist there.
Pre-migration checklist item #3 says
Ensure that the backup file is correctly structured for import. If you have a large instance, we recommend into a database file containing your activeobjects.xml and entities.xml, and a separate one for your attachments and other media.
This can help avoid timeout errors and reduce the risk of issues on import.
My question is: What is considered large? My entities.xml + activeobjects.xml file sizes are 1.8GB only when unzipped. Is that large?
For environments with more than 5GB, you might need to split the attachments into 2-5GB chunks and upload the attachments after the site import.
See more https://support.atlassian.com/migration/docs/use-jira-site-import-to-migrate-from-server-to-cloud/#Troubleshooting-this-step.1
Another alternative would be asking Atlassian to enable the CFU feature which is a solution for customers with large attachments (>10GB), which is your case.
See more https://confluence.atlassian.com/cloudkb/pre-loading-your-jira-and-confluence-attachments-for-a-migration-1079348121.html
I didn't know about the existence of the CFU it's a good thing to know!