Large multi-department SharePoint migrations rarely fail on the technical transfer of content alone. They falter when cutover timing collides with business cycles, when teams lose access to records they depend on, or when the communications plan leaves staff uncertain about where their information now lives. For government and enterprise organisations moving to SharePoint Online and Microsoft 365, the sequence in which departments move is as important as the tooling used to move them. A disciplined wave plan converts a high-risk programme into a series of controlled, recoverable steps.
Wave planning is the practice of grouping content, sites, and users into deliberate migration batches and ordering those batches to respect operational and records dependencies. The objective is to keep each department productive before, during, and after its cutover, while maintaining a clear trail of what moved and when. This article sets out how to build a wave and communications plan that aligns cutover timing with departmental needs, records obligations, and the realities of a working organisation.
Sequencing without a dependency map is guesswork. Before assigning any department to a wave, catalogue the relationships between sites, libraries, shared content, and the business processes that rely on them. A finance team may draw on records owned by procurement, a policy unit may reference material held by legal, and shared reference libraries may serve the entire organisation. Moving one group ahead of a dependency it relies on creates broken links, duplicated content, and periods where staff cannot complete their work.
Equally important is understanding integration and automation dependencies. Power Automate flows, Power Apps, Teams channels connected to SharePoint sites, and third party line of business systems all bind content to specific locations. Document these connections during discovery so that each can be reconfigured or revalidated as its underlying site moves. Overlaying this technical map with departmental business cycles, such as reporting periods, grant rounds, or end of financial year activity, reveals the windows in which each group can tolerate a cutover and the windows it cannot.
With dependencies understood, group departments into waves that move related content together or in a logical order. Early waves should favour lower risk, lower complexity areas that let the migration team prove the process, refine runbooks, and build organisational confidence. Shared and foundational content, such as organisation-wide reference libraries and common templates, often belongs in an early wave so that later departmental moves can point to settled, authoritative locations rather than content still in transit.
Size each wave to match the capacity of the team and the tolerance of the business, rather than the calendar alone. A wave that is too large concentrates risk and overwhelms support channels on cutover day, while waves that are too small stretch the programme and prolong the period of dual running. Microsoft provides native tooling to support this staged approach, including Migration Manager within the SharePoint admin centre and the SharePoint Migration Tool, which allow administrators to schedule and track batches in a controlled manner. Build explicit rollback and pause points into the plan so that a problem in one wave does not cascade into those that follow.
Government and aged care organisations carry statutory recordkeeping obligations that must survive the migration intact. Retention labels, disposal authorities, metadata, version history, and audit trails all need to be preserved or deliberately reconstructed in the destination. Sequencing should recognise which departments hold records under active legal hold, formal retention schedules, or sector-specific requirements, because these groups demand additional validation and may warrant dedicated waves with tighter controls.
Treat records integrity as an acceptance criterion for closing each wave, not an afterthought. Before a department is signed off, confirm that retention settings apply correctly in Microsoft Purview, that permissions reflect the intended access model, and that content owners can locate and open their material. This verification step gives records managers and information governance teams the evidence they need to attest that obligations remain met, and it prevents compliance gaps from accumulating silently across successive waves.
A wave plan is only as effective as the communication that surrounds it. Each department needs to know when its cutover will occur, what will change, where to find relocated content, and how to raise problems quickly. Tailor messages to each audience and stage them to match the wave schedule, giving advance notice, a reminder close to cutover, and clear confirmation once a move is complete. Generic, organisation-wide announcements rarely give individual teams the specific guidance they need to keep working.
Support arrangements should scale with each wave rather than relying on business as usual channels. Identify departmental champions who can field local questions, prepare short reference guidance for common tasks such as accessing migrated libraries, and brief the service desk on the schedule so that incidents are recognised and resolved promptly. Capturing lessons from early waves and feeding them back into communications for later ones steadily improves the experience, reducing both disruption and the volume of support requests as the programme progresses.
Treat every wave as an opportunity to validate assumptions and refine the approach. Define clear entry and exit criteria, measure how each cutover performed against them, and review what worked and what did not before committing to the next batch. This cadence keeps the programme adaptive, so that sequencing decisions made months earlier can be adjusted as the organisation learns more about its own content and behaviour.
The combined effect of careful dependency mapping, sensible wave structure, disciplined records validation, and staged communication is a migration that the business barely notices. Departments retain access to the information they need, compliance obligations remain demonstrably intact, and the organisation arrives in Microsoft 365 with confidence rather than disruption. That outcome is the real measure of a well planned cutover.

Level 7, 12 St Georges Tce
Perth WA 6000
[email protected]
Ph 1300 NOVATA

In the spirit of reconciliation Novata Solutions acknowledges the Traditional Custodians of country throughout Australia and their connections to land, sea and community. We pay our respect to their Elders past and present and extend that respect to all Aboriginal and Torres Strait Islander peoples today. This land always was, and always will be Aboriginal Land.

Novata Solutions is committed to embracing diversity and eliminating all forms of discrimination through education. We welcomes all people and is respectful of individual identities.