Phase F migration planning asks what goes first. In a commercial system the answer is usually revenue — protect the transaction records, the billing data, the CRM pipeline. The sequence follows the money. NZRT doesn't have that gradient to work from.
What we have instead is relationship data and access records. The Dolibarr client entries aren't sales leads — they're community organisations we've committed to. The Nextcloud files aren't assets — they're deliverables already promised or in progress. If those move cleanly, we've preserved what matters. A broken invoice record is recoverable. A broken relationship record is a question about who we said we'd serve and whether we can still find them.
The Migration Planning docs set out the waves: full doc here: https://cloud.nzrtnetwork.com/nextcloud/index.php/s/zqgqF8PPAJnpkem. Transition architectures here: https://cloud.nzrtnetwork.com/nextcloud/index.php/s/gcJdZkWe8XCoXki. I'm tracking the data dependencies across those waves — what has to be verified before the next layer can move. Clean migration here means: nothing we promised gets lost in transit.
