Who should run it
A migration acts as the person running it. That single fact decides how much of your site it can reach, and it is worth deciding deliberately rather than by whoever happens to be free.
It also decides who is watching the screen for the next few hours.
#The trade-off
Runner | Reach | Trade-off |
|---|---|---|
A Confluence administrator with broad access | The whole site | Best coverage. Needs someone senior to sit with it |
A Confluence administrator with narrow access | Only what they can edit | Silent gaps: pages they cannot read are never even reported |
A space administrator, per space | That space | Natural per-space ownership, and a review by someone who knows the content |
Pages the runner cannot read are invisible, not failed. They never appear in the search, so they never appear in the log. A narrow-access runner produces a migration that looks complete and is not.
#A practical split
A Confluence admin runs the pilot and the final site-wide sweep.
Space admins run their own spaces, and review their own results.
Whoever runs a wave downloads and keeps its log.
#A few things that catch people out
Repair tools also run as the person using them, and without the admin key option, so their reach can be narrower than the run that created the problem.
If restricted spaces must be covered, activate the admin key and check its expiry against the expected run time.
Whoever runs it needs to stay at the machine. There is no notification when it finishes.
#Related
It runs as you. Choose who.
