Confluence attachment size affecting migration time

This insight is always shown, because we recommend pre-migrating attachments regardless of their size. 

How does the attachment size affect migration time?

Migrating attachments takes up migration assistant’s throughput that could be devoted to spaces and pages.

Any sizable chunk of attachments migrated together with spaces will affect the migration speed and, by extension, downtime. Pre-migrating attachments doesn’t affect your work around Confluence 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 spaces later on?

When you pre-migrate attachments, we save a mapping of which pages they lived in before the migration. Once you migrate spaces later on, we’ll link attachments to their respective pages. Until then, we’ll store them in your cloud site.

Pre-migrate attachments

To pre-migrate all attachments:

1. Open the migration assistant by going to Administration > General configuration > Migration Assistant.

2. Create a new migration plan.

3. Follow the steps in the wizard until you access the screen where you can choose what to include in your migration.

4. Open the Spaces card where you can select the spaces to migrate.

5. In Space data, select Attachments only, like on the screenshot below.

6. Use the Select all check box to select all your spaces. This will include attachments from all your spaces, but not the spaces themselves.

Skip adding data from the remaining cards, such as Users and groups or Global filters. The goal of this migration plan is to migrate attachments only. Follow the steps in the assistant to start your migration.