SharePoint Modernization Blueprint

• A SharePoint Server support window closing, with no migration plan behind it
• InfoPath forms and SharePoint Designer or Nintex workflows still running the business — on technology Microsoft has retired or is retiring
• A merger or acquisition that means consolidating tenants nobody fully understands
• Copilot on the horizon and a quiet fear: "Copilot finds every file your permissions let it find. Are you sure about your permissions?"
• File shares migrating into SharePoint faster than anyone can impose structure
• Nobody who can say how many sites exist, who owns them, or what the workflows actually do

Microsoft set your deadlines already. The question the Blueprint answers is what those deadlines actually require of you — which is almost never "move everything, as is, immediately."

• Site, storage, and permission inventory — every site, its size, its owners, and how its permissions actually resolve
• Workflow and InfoPath/Nintex census — the deadline-driven artifact: every form and workflow on retired or retiring technology, catalogued with owner and business function
• Information-architecture and findability review — how content is structured, why people can't find things, and what that costs a modernization
• Teams and Power Platform dependency map — the apps, flows, and Teams that will break if content moves without them
• Risk and complexity matrix — every site and workload scored, so effort goes where risk lives
• Target-state information architecture — what the estate should look like on the other side
• Migration waves with effort ranges — sequenced groups, each with an effort range rather than a single false-precision number
• Hypercare plan — how the first weeks after each wave get supported

Deep tier adds: coverage for large or multi-tenant estates, a records and retention review, and per-workflow modernization mapping — which forms become Power Apps, which workflows become Power Automate, and which should simply be retired.

• Read access to the estate, or ShareGate/script-based inventory output if you already have tooling in place. We work with either; nothing is modified.
• Two to three workshops with IT and the business owners of key sites and workflows.
• Any existing migration or governance documentation, if it exists. It's fine if it doesn't — that's often why we're here.

Three weeks for the focused tier. Deep engagements run four to five weeks depending on estate size and tenant count. Both end with a readout workshop, not a document handoff.

• Estate census workbook — sites, storage, permissions, workflows, forms, owners, dependencies — in one place, for the first time
• Risk and complexity matrix — the scored view that tells you where the migration will actually be hard
• Workflow and InfoPath exit map — what's on retired technology, what each item does, and what happens to it (deep tier: per-item modernization mapping)
• Target-state IA and migration wave plan — the sequenced plan with effort ranges and a hypercare approach
• Findings deck and readout workshop — written for both the technical team and the executives funding the migration

Deep pricing is fixed within that band once we've sized the estate on the qualification call — you'll have a single number before anything starts.

Fee credit: 100% of the focused-tier fee is credited toward any implementation engagement of $25,000 or more signed within 90 days of your readout.

The Blueprint is not a migration. No content moves, no workflows are rebuilt, no permissions are changed. It's the plan that makes those projects predictable, and it keeps the diagnosis honest, because there's no build revenue hiding inside it. Migrations fail on permissions, workflows, and information architecture, not on file transfer; the Blueprint is where those failures get found while they're still cheap.

Findings are never scoped to the entry topic. If the census turns up Power Platform governance risk or a Copilot oversharing problem, it goes in the findings. That's the standing rule on every IMP0WER assessment, and the Power Platform Health & Governance Gauge exists when that side needs its own diagnosis.

Most clients move into migration and modernization implementation with the wave plan as the contract backbone — waves, effort ranges, and hypercare are already defined, so scoping is fast and accurate. Workflow and form rebuilds flow into Power Apps and Power Automate work; many estates follow the Blueprint with Microsoft 365 optimization or a Copilot readiness push, since a cleaned, well-permissioned estate is what makes Copilot safe. Our founder's Microsoft delivery career runs back to 2008, including SharePoint migrations with ShareGate and AvePoint tooling, and the plan is written so any competent team, including yours, could execute it.