Before you uninstall the old app
It is tempting to uninstall the app you are migrating away from as soon as the run finishes. Do not, yet.
Rollback restores page content, and the previous version of every page still holds the original vendor macro. Those macros only render while the vendor app is still installed.
#The checklist
Check | Why |
|---|---|
Every wave has been run, including a final unfiltered sweep | The sweep catches what no filter selected |
Every run's log has been downloaded and kept | Repair and rollback both need the specific run's log |
Failures have been reviewed and either fixed or accepted | A failure is a macro still on the page |
Reported-only macros have a plan | They were never going to convert; they still need a decision |
Sample pages have been opened and read by their owners | Rendering problems do not appear in logs |
Keep-source-macro duplicates have been cleaned up | If you used that option, the pages render twice |
After uninstalling, rollback becomes much less useful. The old page versions are still in history, but the macros in them will not render. Roll back before you uninstall, not after.
#A safe order
Migrate, review, and fix. Keep both apps installed throughout.
Leave a gap. A week of normal use surfaces what a review misses.
Then uninstall the old app, and only then let its licence lapse.
#A few things that catch people out
An expired licence on the old app can stop its macros rendering, which looks exactly like a failed migration.
Reported-only macros will still be on your pages after uninstalling, and will render as broken macros.
Assets the migration created stay in place whatever you do. Rollback does not remove them.
#Related
Roll back before you uninstall. Not after.
