Four decisions to make before moving a SharePoint estate

The migration tool is rarely the first hard problem. The hard problem is deciding what still matters, what each dependency does, and what evidence will count as a successful move.

Who owns the outcome?

A site owner in an old directory export is not necessarily the person who can accept the target. Confirm the accountable business owner, the operational support owner and any records or security authority. Unowned content should not silently become owned by the migration team.

What should happen to it?

Give every workload an explicit disposition: migrate, rebuild, retire, archive or temporarily rehost. Copying content because it exists preserves duplication and obsolete permissions. Retiring or archiving safely is often more valuable than moving another terabyte.

What does it depend on?

Legacy SharePoint applications frequently cross IIS, SQL, Active Directory, certificates, scheduled tasks, email relays, file shares and third-party services. A scanner sees some of this. Interviews, configuration recovery and runtime evidence reveal the rest.

Test the hardest workflow, external-user journey and integration before applying a per-site migration rate.

What proves the move worked?

Counts alone are insufficient. Acceptance must cover information integrity, permissions, search, records controls, workflows, integrations, accessibility, performance and recovery. Sample ordinary content and deliberate exceptions.

When a fixed price becomes honest

Once ownership, disposition, dependencies and acceptance are controlled, a delivery team can define repeatable work packages and credible assumptions. Before then, a fixed price either contains a large risk allowance or relies on future variations. Discovery is what turns uncertainty into a priceable scope.