Using the migration assistant
The assistant is a five-step rail. Two of those steps are decisions, two are selection, and the last one is watching it happen.
The options step comes before you have seen a single count, and the wizard never brings you back to it, so it is worth understanding what each setting does before you get there.
The run lives in your browser tab. The run happens in this browser tab. You cannot close it and come back, and nothing notifies you when it finishes.
#In this section
Migration behaviour versionsThe version picker is a behaviour choice, not a release stamp: it decides whether diagram history and standalone app content come across.Migration optionsSkip errors, Keep source macros, the classic draw.io layout and the admin key: what each one changes, and which ones you can undo.Narrowing what gets migratedThe search filter, the space-level entry point, and why there is no page picker.Step 1: Introduction and acknowledgementsFour acknowledgements stand between you and the wizard, and each one is there because somebody learned it the hard way.Step 2: Choosing your optionsBehaviour version, error handling, and the two advanced switches, all chosen before you have seen a single count.Step 3: Selecting appsCapable counts how many pages carry each app's macros, and you tick the apps you are moving away from.Step 4: Selecting macrosOne row per macro, each with its own count, its own support badge, and an expander telling you what it will and will not do.Step 5: Running and watchingVerification first, then the real run, with a live progress header and four clickable stat cards.
#Related
Verify, read it, then migrate.
