# Microsoft 365 Migration Readiness Checklist

A practical preflight checklist for Microsoft 365, SharePoint, Teams, OneDrive, Exchange, Power Platform, Azure, and legacy system migrations.

## 1. Define the migration thesis

Before running tools or collecting exports, agree on why the migration is happening. A deadline-driven SharePoint move, a tenant consolidation, and a workflow modernization effort require different sequencing, owners, and validation gates.

- ✓ Document the business driver, required deadline, risk tolerance, and success criteria.
- ✓ Separate mandatory scope from optional cleanup, nice-to-have modernization, and later-phase governance work.
- ✓ Create an explicit decision log so scope changes, tool choices, and target architecture decisions are traceable.

## 2. Build the source inventory

- ✓ Inventory users, groups, domains, licenses, mailboxes, shared mailboxes, aliases, sites, Teams, channels, OneDrive accounts, file shares, workflows, forms, integrations, and storage volume.
- ✓ Identify inactive users, orphaned owners, stale sites, duplicate Microsoft 365 groups, unmanaged guests, direct permissions, external sharing links, unsupported templates, and custom solutions.
- ✓ Mark every object as migrate, modernize, archive, retire, consolidate, or defer. Do not let ambiguous objects silently become migration scope.
- ✓ Capture business owners and validation owners. Technical ownership alone is not enough for a successful cutover.

## Move legacy forms with Form Migrator

For organizations with InfoPath or legacy form sprawl, Form Migrator gives the modernization effort a product-led path instead of a one-form-at-a-time rebuild cycle.

Where Form Migrator fits:

- ✓ Inventory and rationalize forms before rebuilding them in Microsoft-native patterns.
- ✓ Prioritize high-value forms by business criticality, usage, data complexity, and owner readiness.
- ✓ Support a repeatable migration motion across Power Apps, Power Automate, SharePoint, Dataverse, and governance workstreams.

## Move Nintex workflows with Flow Migrator

For teams moving Nintex and legacy workflow estates into Power Automate, Flow Migrator helps turn discovery, mapping, and rebuild planning into a repeatable migration motion.

Where Flow Migrator fits:

- ✓ Identify workflow candidates, dependencies, owners, triggers, approvals, and failure points.
- ✓ Separate direct rebuilds from processes that need redesign, governance, or integration architecture.
- ✓ Accelerate migration planning from Nintex into supportable Power Automate patterns.

## 3. Confirm target tenant readiness

- ✓ Confirm Entra ID model, Conditional Access baseline, MFA, break-glass accounts, privileged roles, admin consent process, and security defaults.
- ✓ Review SharePoint and OneDrive sharing settings, Teams governance, naming policies, sensitivity labels, retention, DLP, audit logging, and external collaboration rules.
- ✓ Define Power Platform environment strategy, DLP policies, connection ownership, service account usage, solution strategy, and support boundaries.
- ✓ Confirm licensing assumptions for Power Apps, Power Automate, Teams, Exchange, security, compliance, and migration tooling.

## 4. Map dependencies before waves

- ✓ Link forms to workflows, workflows to lists, lists to reports, reports to decision-makers, and sites to business processes.
- ✓ Identify mail-enabled systems, service accounts, scheduled jobs, webhooks, APIs, custom scripts, document templates, and line-of-business integrations.
- ✓ Flag processes that cannot tolerate downtime, partial migration, permission drift, or stale data.
- ✓ Create a migration dependency map that shows what must move together and what can safely be sequenced later.

## 5. Execute with controls

- ✓ Build a source-to-target mapping workbook with owners, waves, dependencies, validation requirements, rollback considerations, and issue owners.
- ✓ Run pilot migrations with representative users, site types, permissions, file sizes, forms, workflows, Teams, and mailbox scenarios.
- ✓ Use go/no-go checkpoints before every production wave. Validate business outcomes, not only item counts.
- ✓ Create cutover runbooks, communication templates, hypercare coverage, and post-migration governance tasks before the first production wave.

## Want this applied to your environment?

We can turn the worksheet into an inventory, risk register, migration roadmap, and product-backed execution plan.