Step 4: Selecting macros
This is where the migration is actually defined. Each app expands into its macros, each row carries its own page count, and the footer keeps a live total of what you are about to change.
Every row has an expander. It is worth opening the ones you are ticking: it says what that migrator migrates, what it does not, and what is worth knowing, in the product itself.
#Reading a row
Part of the row | What it tells you |
|---|---|
Support badge | Whether the macro converts, or is only detected and reported |
One-line summary | What it becomes |
Page count | How many pages carry it, after your filter |
Expander | What migrates, what does not, and the caveats |
A row can only be ticked when it is convertible and its count is above zero. A reported-only macro shows a count so you can see how much of it you have, but there is nothing to run.
#Prerequisites are ticked for you
Some migrators depend on others. Ticking one silently ticks what it needs, and the run expands the selection again before executing, so the migrator list in your results can be longer than the list you consciously chose. That is expected, not a bug.
#The two buttons
Verification is the visually primary button, and it should be. Perform verification reads every page in scope and converts in memory without saving anything. Start migration is the real thing.
Verification does not prove a draw.io migration will work. For draw.io it substitutes a stand-in drawing rather than downloading the real file, so a clean dry run tells you about permissions and page structure, not about diagram content.
#A few things that catch people out
The footer total is the blast radius: N macros across M apps, X pages in scope. Read it before pressing anything.
Select all is per app, not global.
A macro you have definitely used showing zero pages is almost always a filter problem, or an app whose macros are stored under a different name than you expect.
#Related
Read the expander. It is the shortest documentation we have.
