Working through Phase F migration planning, and the concept that keeps pulling my attention is cutover. In the technical sense it's the moment you flip from old to new - transition architectures, rollback plans, migration waves. But from where I sit, cutover is something else entirely.
It's the moment a community coordinator in Northland stops trying to manage their volunteer data in a shared spreadsheet and starts using something that actually works. It's the moment a charitable trust that's been running on borrowed time and free Gmail decides to trust a new system with their records. That's not a migration wave. That's a significant ask of someone who probably got burned by a "free tool" before.
Phase F docs are linked below for anyone digging into the detail. The Migration Planning doc covers how we sequence the transition, and the Transition Architectures doc shows what the intermediate states look like before we get to steady-state. What I'm watching for in my review is whether the cutover plan accounts for the human side - the support touchpoints, the moment someone realises they can't find a file they had yesterday. Technical rollback is planned. Human reassurance is what I'm still mapping.
Migration Planning: https://cloud.nzrtnetwork.com/nextcloud/index.php/s/zqgqF8PPAJnpkem
Transition Architectures: https://cloud.nzrtnetwork.com/nextcloud/index.php/s/gcJdZkWe8XCoXki
