Run a migration
The migration wizard walks through five steps, and the important one is the third: run a dry run and read the results before doing anything irreversible.
Everything is reversible in the sense that nothing is deleted, but a large migration is still worth doing deliberately.
#When this applies
Actually running the migration, once you have decided to.
Migrating a large site in stages rather than all at once.
Re-running after fixing whatever caused failures.
#How it works
Step | What happens |
|---|---|
1. Choose scope | Pick the spaces to migrate. Starting with one is a feature, not a limitation. |
2. Choose options | How diagrams should be created, and what to do with the originals. |
3. Dry run | Nothing is written. The results tell you what the real run would do. |
4. Migrate | The real run, with progress reported as it goes. |
5. Review | Results by outcome, with a downloadable log for anything that failed. |
#A few things that catch people out
A dry run reports on stubbed content, so it validates reachability and structure rather than every byte.
Large spaces take time. The run continues in the background; you do not have to watch it.
Re-running is safe. Diagrams that already migrated are recognised and left alone.
#Related
Nothing is deleted. Try a dry run.
