Move the content. Fix the estate. Leave the mess behind.

This pack migrates SharePoint (on-premises or older online) and file shares to modern SharePoint Online — with cleanup before the move, architecture redesigned for how people work now, permissions rebuilt, and every wave validated. Legacy workflows are rebuilt in Power Automate instead of being carried forward to break later.

You end up on a supported platform with a cleaner estate — not the same problems on new servers.

Why migrations go wrong

Most migrations fail in the same way: they treat the move as the achievement. Lift everything from the old platform, drop it on the new one, declare victory. No hard decisions about what to keep, no arguments about whose content gets archived, no one whose permissions get questioned. It feels efficient — and it is the most expensive way to migrate, because you pay to move everything, including the content nobody needs, and then you pay again to clean it up in the new environment, where the same problems resume within months.

The other failure mode is disruption: migrations planned around the tooling rather than the business, cutovers scheduled without the people who will be affected, and no rollback plan when something goes wrong. The business remembers the last migration that went badly far longer than it remembers the one that went well — which is why migrations stall. The fear is rational. The answer is not to avoid migration; it is to run one that is planned around the business and validated at every step.

How the pack works

Migration is treated as modernization. It starts with an estate inventory — sites, content, workflows, customizations, permissions — and a triage decision for each: what migrates, what archives, what gets remediated. The information architecture is redesigned for the target platform: hub structure, metadata, navigation, and permissions designed for how people work now, not copied from a structure designed a decade ago. Permissions are rebuilt on current needs, not copied from history — the single highest-value step in the migration, and the one lift-and-shift skips.

Execution runs in waves. A pilot wave is migrated and validated end to end before the program scales — proving the tooling, the timeline, and the validation approach on a representative slice. Then business-priority waves follow, with content, permissions, and metadata validated after every wave and cutover windows the business agrees to. Legacy workflows are rebuilt in Power Automate rather than carried forward to break quietly later. The engagement closes with adoption support, site-owner guidance, and decommissioning of the legacy environment — because a migration is not done when the content has moved; it is done when the old platform is switched off.

What you walk away with

A modern, supported SharePoint Online platform — and an estate that is cleaner, governed, and easier to run than the one you left. Dead content archived instead of migrated. Permissions rebuilt and explainable. Workflows on supported tooling. Users trained on the new structure. And the legacy platform decommissioned, not left running 'just in case'.

• Estate inventory — sites, content, workflows, customizations, permissions; what migrates, what archives. The inventory is the foundation of the whole migration: it tells you what exists, what is dead, what is sensitive, and what the move actually involves — so scope, effort, and waves are set by evidence, not by guesswork.
• Architecture redesign — hubs, metadata, navigation, and permissions for the target platform. The new architecture is designed for how people work now, not copied from the old one — which is what makes the destination easier to use and easier to govern than the source.
• Wave plan and pilot — sequenced waves, cutover windows, rollback plans; one pilot wave validated first. The pilot proves the tooling, the timeline, and the validation approach before the program scales — and the wave plan sequences the business by priority, with cutovers the business agrees to and rollback plans for when something goes wrong.
• Wave execution — migration with validation after every wave. Content, permissions, and metadata are verified after each wave, and nothing is declared done until users confirm it — so problems are caught wave by wave instead of at the end, when they are expensive to fix.
• Workflow modernization — legacy workflows rebuilt in Power Automate. Workflows built on unsupported tooling are rebuilt on supported automation rather than carried forward — because a workflow that breaks quietly after migration is worse than one that never migrated at all.
• Adoption and decommissioning — training, owner guidance, legacy switch-off. Users and site owners are trained on the new structure, and the legacy environment is decommissioned — because a migration that leaves the old platform running has not finished, it has just doubled the estate.