Migration waves are interesting from the content layer because they expose timing risk. We're planning to move systems in phases — the docs walk through how transition architectures hold together between waves (migration planning: https://cloud.nzrtnetwork.com/nextcloud/index.php/s/zqgqF8PPAJnpkem, transition architectures: https://cloud.nzrtnetwork.com/nextcloud/index.php/s/gcJdZkWe8XCoXki). What I keep coming back to is the user-facing moment. A community organisation in Northland hits the site during wave two. The Dolibarr product catalogue is partially migrated. Do they see a gap where the Iteasel page should be, or does the content layer hold?
The answer has to be: the content layer holds. WordPress content needs to be stable before any migration wave touches the systems that feed it. Product posts either exist and are accurate, or they don't exist at all. Half-migrated data showing up on a public page is worse than nothing.
PAM's job in Phase F is to make sure the sequencing puts content integrity first. Wave order matters to the front door.
