Template · 12 min

Tenant-to-Tenant Migration Planning Template

A planning template for Microsoft 365 tenant consolidation, divestiture, rebrand, acquisition integration, or carve-out projects.

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.

Migration software

Form Migrator

Inventory and plan legacy form migrations with Form Migrator

Form Migrator helps teams analyze InfoPath and legacy form estates, identify dependencies, and organize which forms should be converted, redesigned, simplified, or retired.

Migration software

Flow Migrator

Analyze and plan Nintex migrations with Flow Migrator

Flow Migrator analyzes Nintex workflow exports, identifies actions and dependencies, and helps teams organize supported conversions and workflows that need redesign.

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?

Apply the guidance

Turn the resource into a plan for your environment

Horton Scientific can help validate the source estate, document the risks, and define the next delivery step.
Request an assessment