Attachment size affecting migration time
This insight is always shown, because we recommend pre-migrating attachments regardless of their size. The median migration rate for attachments is 600 GB per 24 hours.
How does the attachment size affect migration time?
Migrating attachments take up migration assistant’s throughput that could be devoted to projects and issues.
Any sizable chunk of attachments migrated together with projects will affect the migration speed and, by extension, downtime. Pre-migrating attachments doesn’t affect your work around Jira or block any user actions, so you can add them to a separate migration plan and send to cloud any time before the production migration.
How will attachments be linked to projects later on?
When you pre-migrate attachments, we save a mapping of which issues they lived in before the migration. Once you migrate projects later on, we’ll link attachments to their respective issues. Until then, we’ll store them in your cloud site.
Pre-migrate attachments
To pre-migrate all attachments:
Open the migration assistant by going to Administration > Migrate to cloud.
Create a new migration plan.
Follow the steps in the wizard until you access the screen where you can choose what to include in your migration.
Open the Projects card where you can select the projects to migrate.
In Project data, select Attachments only, like on the screenshot below.
Use the Select all check box to select all your projects. This will include attachments from all your projects, but not the projects themselves.
Skip adding data from the remaining cards, such as Users and groups or Apps. The goal of this migration plan is to migrate attachments only. Follow the steps in the assistant to start your migration.
Was this helpful?