Workstreams to track
- ✓Identity and Entra ID users, groups, roles, MFA, Conditional Access, devices, and guest users.
- ✓Domains, DNS, mail routing, MX, SPF, DKIM, DMARC, Autodiscover, and coexistence.
- ✓Exchange Online mailboxes, shared mailboxes, aliases, distribution groups, calendars, and delegated access.
- ✓SharePoint, OneDrive, Teams, Microsoft 365 groups, permissions, labels, retention, and external sharing.
- ✓Power Platform environments, connections, flows, apps, service accounts, and integration dependencies.
- ✓Security, compliance, communications, training, support model, and hypercare.
Key mapping fields
- ✓Source object, target object, business owner, technical owner, business unit, migration wave, dependencies, validation owner, rollback consideration, and hypercare notes.
- ✓Domain dependency, source authentication method, target identity decision, license plan, device impact, and user communication group.
- ✓For SharePoint and Teams: source URL, target URL, owner, members, guests, associated Team, hub, label, retention requirement, and external sharing requirement.
Product accelerator
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.
Product accelerator
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.
Cutover questions
- ✓When do domains move and what must be frozen before they move?
- ✓Which users require coexistence, staged access, or special support during cutover?
- ✓How will mail flow, Teams access, SharePoint permissions, OneDrive sync, and mobile clients be validated?
- ✓What forms, workflows, service accounts, and integrations must be available on day one?
- ✓Who approves completion for each wave and what is the escalation path if validation fails?