Rolling back a migration
Undoes a migration by restoring every page the run changed.
Find it under Repair, then the "Roll back pages" card. Log only..
#What it changes
Restores each page to the version immediately before that run's "Migrated by Capable" edit, using Confluence's own restore, which creates a new version holding the old content. Nothing is deleted, and the rollback itself is undoable from page history. Writes a version labelled as a rollback.
#What to know before running it
Restores page content only. Assets the migration created are left in place, and the original vendor macros only render again while the vendor app is still installed, so this is not a full undo of the migration. It needs that exact run's downloaded log and refuses to run against a different site. It classifies each page and skips pages someone edited after the run unless you opt in. It analyses every page in the log, including ones the run never changed, which is why analysing a big log is slow and the skip count is large. Bulk rollback stays locked until you have rolled back and checked one page.
Every write is a new page version with its own version message, so the repair itself is visible in page history and can be undone from there.
#A few things that catch people out
Bulk operation stays locked until you have fixed and checked one page by hand.
It only looks at the pages you hand it. It never sweeps the site.
Cancel stops the queue between pages; anything already in flight still writes.
#Related
Fix forward. Nothing is deleted.
