MSADVANCE LOGO
✕
  • Services
    • Microsoft 365 Consulting Services for Businesses
    • Migration to Microsoft 365
    • Microsoft 365 to Google Workspace Migration
    • Azure Cloud Architecture
    • Modern Workplace
    • Microsoft 365 & Azure Cybersecurity Services
    • Managed Microsoft 365 & Azure Services
    • Software License Procurement & Sales for Businesses
  • About Us
    • Success Stories
    • Microsoft Partner
    • Trust Center: Security, Privacy & Access
    • Our Methodology
  • Blog
  • Contact
  • English
    • Español
    • English
  • Services
    Microsoft Cloud services From strategy to operations Choose the service area that fits your project.
    Explore all services Talk to a specialist
    • 01 / STRATEGY Microsoft 365 Consulting Assessments, architecture and governance to guide your next steps. Assessment · Governance · Roadmap
    • 02 / MIGRATION Microsoft 365 Migrations Move email, files and tenants with planned cutover and validation. Tenant to tenant · Google · Exchange
    • 03 / WORKPLACE Modern Workplace Collaboration, devices and adoption across Microsoft 365, with governance built in. Teams · SharePoint · Intune
    • 04 / SECURITY Microsoft Cybersecurity Protect identities, data and endpoints with Microsoft security and Zero Trust. Entra · Defender · Purview
    • 05 / CLOUD Microsoft Azure Design landing zones, networks, resilience and cloud cost controls. Landing Zones · Networking · FinOps
    • 06 / OPERATIONS Managed Services Administration, support and continuous improvement for Microsoft 365 and Azure. Microsoft 365 · Azure · Security
    • 07 / LICENSING Microsoft Licensing Select, procure and optimize licenses based on usage and cost. Microsoft 365 · Azure · Copilot

    Microsoft Partner · 25+ Microsoft certifications · 51,000+ users · 500+ organizations

    Success stories Credentials Methodology Trust Center
    • Microsoft 365 Consulting Services for Businesses
    • Migration to Microsoft 365
    • Microsoft 365 to Google Workspace Migration
    • Azure Cloud Architecture
    • Modern Workplace
    • Microsoft 365 & Azure Cybersecurity Services
    • Managed Microsoft 365 & Azure Services
    • Software License Procurement & Sales for Businesses
  • About Us
    About MSAdvanceExperience, delivery and trustGet to know our company, how we work and the projects we have delivered.
    Discuss your project→
    MSAdvanceMicrosoft cloud consulting since 2010Who we areSpecialists in Microsoft 365, Azure and security. We deliver projects remotely for businesses worldwide.Get to know MSAdvance→
    • Experience→Success storiesMigration, Microsoft 365 and Azure projects: challenges, scope and outcomes.
    • Credentials→Microsoft PartnerCertifications and technical expertise across our team.
    • Project delivery→Our methodologyPhases, responsibilities and validation, from assessment through handover.
    • Security and privacy→Trust CenterConfidentiality, permissions and access controls throughout the project.
    25+ Microsoft certifications · International projectsExplore our services→
    • Success Stories
    • Microsoft Partner
    • Trust Center: Security, Privacy & Access
    • Our Methodology
  • Blog
  • Contact
  • English
    • Español
    • English
Published by MSAdvance on August 28, 2025
Categories
  • Microsoft 365 Migration
  • Quest On Demand Migration
  • tenant-to-tenant migration
Tags
  • Desktop Update Agent Quest ODM
  • Directory Sync Quest
  • Domain Rewrite Quest
  • Exchange migration Quest ODM
  • Microsoft 365 tenant to tenant Quest
  • OneDrive migration Quest ODM
  • Quest On Demand Migration
  • SharePoint tenant migration Quest
  • Teams migration Quest On Demand

Microsoft 365 Tenant-to-Tenant Migration with Quest On Demand: A Complete Step-by-Step Guide

Want MSAdvance to handle the entire migration for you?

We plan, execute, and measure your tenant-to-tenant migration with Quest On Demand—minimizing risk and preventing data loss.

Talk to our team See our Microsoft 365 migration service

Table of contents

  1. Introduction
  2. 1. What is Quest On Demand Migration (ODM)?
  3. 2. Prerequisites & permissions
  4. 3. Project methodology
  5. 4. ODM setup: project, tenants, and identity matching
  6. 5. Exchange Online (mail, calendars, shared mailboxes)
  7. 6. OneDrive (users, versions, and links)
  8. 7. SharePoint (sites, permissions, metadata)
  9. 8. Microsoft Teams (teams, channels, chats)
  10. 9. Coexistence with ODM: Directory Sync & Email/Domain Rewrite
  11. 10. Desktop Update Agent: Outlook/OneDrive/Teams switch
  12. 11. Domain cutover & DNS (MX/SPF/DKIM/DMARC)
  13. 12. Security & compliance (Purview, Conditional Access, Defender)
  14. 13. Microsoft 365 licensing after the move
  15. 14. Performance, limits, and throttling
  16. 15. Operational checklists (pre, during, post)
  17. 16. KPIs, UAT, and acceptance
  18. 17. Common risks & mitigations
  19. 18. CSV & helpful snippets
  20. 19. FAQs
  21. 20. Official resources
  22. 21. Conclusion + CTA

Introduction

In mergers, acquisitions, or reorganizations, moving collaboration and data across Microsoft 365 tenants without slowing the business is critical. This guide walks you through a tenant-to-tenant migration with Quest On Demand Migration (ODM): from granting consents and matching identities, to building wave-based batches per workload (Exchange, OneDrive, SharePoint, Teams), running coexistence with Directory Sync and Email/Domain Rewrite, and cutting the domain cleanly. We keep the language practical and add vetted external references at each step.

1. What is Quest On Demand Migration (ODM)?

Quest ODM is a SaaS platform hosted in Azure that centralizes tenant-to-tenant migration of Exchange Online, OneDrive, SharePoint, and Microsoft Teams. It adds discovery, assessment, identity mapping, dashboards, and reporting—plus coexistence options such as Directory Sync and Email/Domain Rewrite to keep users productive during the move. Think of it as a single control plane to orchestrate migration with telemetry and guardrails. :contentReference[oaicite:0]{index=0}

Why ODM? Reduce manual work, run workload-specific tasks, get granular error reports, and use coexistence (Directory Sync and Email/Domain Rewrite) to keep business running while bulk data moves in the background. :contentReference[oaicite:1]{index=1}

2. Prerequisites & permissions

Before creating a single batch, register source and target tenants in ODM and grant the application consents per workload (Exchange, SharePoint/OneDrive, Teams/Graph). Clarify scope early (users, groups, shared mailboxes; sites and permissions; teams and channels; OneDrive per user). For Exchange migrations with ODM, Quest recommends an E3 or higher license on the admin mailbox used to run EWS-based operations—CTUDM is not required for ODM because ODM performs copy-style migrations via APIs.

  • Use a global admin (or workload-specific admin) to grant app consents in both tenants.
  • Review holds, retention, and eDiscovery in the source to avoid unexpected blockers.
  • Decide identity matching strategy: identical UPNs, different suffixes, or a CSV mapping.
Pro tip: document which attributes you’ll use for matching (UPN, primary SMTP, HR object ID) and list exceptions up front.

3. Project methodology

Waves reduce friction and help you learn fast: pilot → first business areas → critical areas → stabilization. ODM supports pre-staging (load history ahead of cutover) and scheduling incremental syncs where available so Day 0 is a non-event for end users. :contentReference[oaicite:3]{index=3}

Quest ODM phases (at a glance)
PhaseActionsOutcome
DiscoveryConnect tenants; scan users, mailboxes, OneDrive, sites, teamsInventory & volumes
MappingMatch identities & groups; CSV for exceptionsMatching ready
MigrationBatches per workload; off-peak windows; retriesData pre-loaded
CoexistenceDirectory Sync + (optional) Email/Domain RewriteContinuity
Go-liveDNS cutover; validation; hypercareClean transition

4. ODM setup: project, tenants, and identity matching

Open On Demand Migration, create a project, add source and target tenants, and grant the requested consents (per workload). Then import or generate the identity matching (auto-match by UPN or upload a CSV). :contentReference[oaicite:4]{index=4}

Step-by-step

  1. Create a project in ODM and select the workloads you’ll migrate.
  2. Connect tenants (source and target) and grant consents.
  3. Run discovery (users, groups, mailboxes; OneDrive; sites; teams).
  4. Define matching (UPN→UPN). If they differ, use CSV (sample below).
  5. Plan waves and windows (pilot → wave 1 → wave 2 → cutover).

CSV sample (identity match)

Headers: SourceUPN,TargetUPN
Row 1: ana.perez@source.com,ana.perez@target.com
Row 2: juan.garcia@source.com,juan.garcia@target.com

If you manage identities on-prem, document the handling of ImmutableID/mS-DS-ConsistencyGuid to avoid misalignment later.

5. Exchange Online (mail, calendars, shared mailboxes)

Email is the heartbeat of daily work. In ODM you create mailbox migration tasks in waves, with reporting, retries, and pre-cutover syncs. A proven pattern is: discover → select mailboxes (user, shared, resource) → run a pilot → scale to waves → run a final delta → cut MX. :contentReference[oaicite:5]{index=5}

Step-by-step

  1. Select mailboxes (users, shared, resources) from inventory.
  2. Map permissions (delegations, SendAs, FullAccess) to target per rules.
  3. Create a batch in ODM and schedule during off-peak hours.
  4. Monitor progress (items migrated, errors, retries).
  5. Run a delta before cutover and validate with key users.
Tip: define mailbox size thresholds per wave; leave extra time for large shared mailboxes.

6. OneDrive (users, versions, and links)

ODM moves each user’s OneDrive content to their counterpart in the target tenant. Plan how you’ll treat version history and shared links (internal/external), and communicate the “after” state clearly. :contentReference[oaicite:6]{index=6}

Step-by-step

  1. Pre-provision users in target and validate identity matching.
  2. Select OneDrives and run migrations in groups (by department/volume).
  3. Validate permissions and critical external shares after each pass.
  4. Recertify access during the first post-go-live week.

7. SharePoint (sites, permissions, metadata)

SharePoint hosts critical libraries and automations. In ODM you can discover sites, assess size/structure, and migrate them in batches, preserving key permissions and metadata where the APIs allow. Normalize path lengths and names to avoid platform limits. :contentReference[oaicite:7]{index=7}

Step-by-step

  1. Audit owners, inheritance, and apps (extensions, flows).
  2. Choose a strategy (by site, by hub, or by critical libraries).
  3. Run batches and review error reports (long paths, invalid names).
  4. Recertify permissions when each wave completes.
Heads-up: normalize paths and file names before moving to avoid OneDrive/SharePoint limits.

8. Microsoft Teams (teams, channels, chats)

ODM supports Microsoft Teams migrations: team/channel structure, files, membership, and—based on Microsoft’s Graph migration mode—importing historical messages into Teams where applicable. The usual flow is: discover → map source teams to destination → migrate files (to SharePoint/OneDrive) → import conversations via Graph migration mode → complete the team. :contentReference[oaicite:8]{index=8}

Step-by-step

  1. Discover teams and classify by criticality (project, department, confidentiality).
  2. Define mapping (Team A → Team A′ in target; private ↔ private channels).
  3. Migrate files (land in SharePoint/OneDrive) and verify permissions.
  4. Import conversations with Graph’s migration mode; complete the team at the end. :contentReference[oaicite:9]{index=9}
  5. Validate apps/tabs (Planner, Forms, Power BI, etc.) and re-authorize connectors.
Important: Respect Teams/Graph API limits (payload size, attachment types, private/shared channel constraints) and plan windows for large histories. :contentReference[oaicite:10]{index=10}

9. Coexistence with ODM: Directory Sync & Email/Domain Rewrite

For longer coexistence or multi-domain scenarios, combine On Demand Directory Sync (keeps users, groups—and in some cases devices—synchronized, builds a unified address list) with On Demand Email/Domain Rewrite to present a single email brand across tenants while routing mail to the right mailbox. Add Exchange organization relationships for Free/Busy between tenants. :contentReference[oaicite:11]{index=11}

Exchange Free/Busy between tenants

PowerShell — organization relationship (illustrative)
Connect-ExchangeOnline
New-OrganizationRelationship -Name "Rel-Target-Tenant" `
  -DomainNames "contoso.com" -FreeBusyAccessEnabled $true `
  -FreeBusyAccessLevel LimitedDetails

10. Desktop Update Agent: Outlook/OneDrive/Teams switch

To make “the day after” smooth, deploy Quest’s Desktop Update Agent (DUA). It reconfigures the user’s Outlook profile, OneDrive client, and Teams app automatically, dramatically shrinking first-day ticket volume. Note: in some environments, the Teams step can report success even if the user remains signed into the source—plan a quick sign-out/sign-in check as part of your first-day script. :contentReference[oaicite:12]{index=12}

Step-by-step

  1. Generate the agent token in your ODM project.
  2. Deploy the MSI via GPO/Intune (transform with your TOKEN and a PASSPHRASE as per the guide).
  3. Schedule the “Switch” around your mail/OneDrive cutover.
  4. User steps: close apps, run DUA, confirm Outlook opens with the new profile and OneDrive points to the target tenant.
Tip: license users in the target (Exchange/SharePoint/Teams) before DUA runs so reconfiguration completes cleanly. :contentReference[oaicite:13]{index=13}

11. Domain cutover & DNS (MX/SPF/DKIM/DMARC)

The domain move is the visible milestone. Rehearse it and lower TTL in advance. Remove the domain from the source (no references in UPNs, proxyAddresses, groups, apps), add it in the target with MX/SPF/DKIM/DMARC, and validate delivery/signing before moving DMARC from p=none to quarantine/reject. For Microsoft 365 record formats and guidance, use the official DNS reference. :contentReference[oaicite:14]{index=14}

DNS (illustrative)
# MX to Exchange Online Protection
MX @ 0 → contoso-com.mail.protection.outlook.com

# SPF / DKIM / DMARC
TXT @ "v=spf1 include:spf.protection.outlook.com -all"
CNAME selector1._domainkey → selector1-contoso-com._domainkey.contoso.onmicrosoft.com
TXT _dmarc "v=DMARC1; p=quarantine; rua=mailto:dmarc@contoso.com"

12. Security & compliance (Purview, Conditional Access, Defender)

Harden the target tenant from Day 1: MFA + Conditional Access, Defender for Office 365 (Safe Links/Attachments, anti-phishing), and Microsoft Purview for sensitivity labels, DLP, retention, and eDiscovery. Recreate policies and review guest access after each wave. :contentReference[oaicite:15]{index=15}

13. Microsoft 365 licensing after the move

Post-migration, align licenses by profile:

Practical comparison
PlanIncludesSecurity/managementUse it when
Business BasicMail, Teams, OneDrive/SharePoint, web appsBaseline controlsLight or frontline profiles
Business StandardAll above + desktop appsHigher productivityHeavy doc editing
Business PremiumStandard + device managementIntune + advanced protectionSecurity-sensitive orgs
Enterprise (E1/E3/E5)Scale & advanced complianceDefender/Purview depth variesMid-large or regulated

Check Microsoft’s official plan comparison tables for the latest details. :contentReference[oaicite:16]{index=16}

14. Performance, limits, and throttling

Microsoft enforces service and Graph API throttling. Size your batches, choose off-peak windows, and monitor health. For Teams message import, expect specific migration-mode constraints (like 5 RPS per channel) and a “complete migration” step. :contentReference[oaicite:17]{index=17}

  • Concurrency: set batch sizes (e.g., 10–20% per wave).
  • Retries: use ODM telemetry to pinpoint failed items and relaunch.
  • Windows: schedule outside peak hours and communicate impacts.

15. Operational checklists (pre, during, post)

Before you migrate

  • Tenants connected and consents granted in ODM (per workload). :contentReference[oaicite:18]{index=18}
  • Identity matching defined (UPN/CSV).
  • Waves and windows agreed; role-based comms plan ready.
  • Pilot runs per workload (Exchange/OneDrive/SharePoint/Teams).
  • DUA packaged (MSI + transform) and token generated. :contentReference[oaicite:19]{index=19}

During migration

  • Monitor tasks; triage errors and run targeted retries.
  • Run Exchange deltas; validate critical mailboxes.
  • Recertify permissions in OneDrive/SharePoint per batch.

After

  • Domain cutover validations (MX, DKIM/DMARC). :contentReference[oaicite:20]{index=20}
  • Desktop switch with DUA (Outlook/OneDrive/Teams). :contentReference[oaicite:21]{index=21}
  • Week-1 hypercare and role-based training.

16. KPIs, UAT, and acceptance

AreaTestSuccess
MailPost-cutover delivery0 bounces; DKIM/DMARC valid
CalendarsFree/Busy during coexistenceAvailability visible
OneDriveAccess & linksNo material broken links
SharePointSite permissionsCorrect access
TeamsTeams, channels, filesStructure and content intact
SecurityMFA/CA per role100% enforced
Users migrated within window (≥ 98%)
Tickets per user in week 1 (< 0.3)
Support MTTR (< 4 h)

17. Common risks & mitigations

RiskProb.ImpactMitigation
Incomplete consentsMedHighPer-workload checklist + pilot
Invalid SPO/OD paths/namesHighHighNormalize & fix pre-move
API throttlingMedMedOff-peak windows + staggered waves
Broken shared linksMedMedComms + recertification
Teams apps not re-authorizedMedMedInventory tabs/connectors + testing

18. CSV & helpful snippets

CSV — identity matching
SourceUPN,TargetUPN
ana.perez@source.com,ana.perez@target.com
juan.garcia@source.com,juan.garcia@target.com
PowerShell — cross-tenant Free/Busy
Connect-ExchangeOnline
New-OrganizationRelationship -Name "Rel-Target-Tenant" `
  -DomainNames "contoso.com" -FreeBusyAccessEnabled $true `
  -FreeBusyAccessLevel LimitedDetails
DNS — cutover example
# MX to Exchange Online Protection
MX @ 0 → contoso-com.mail.protection.outlook.com
TXT @ "v=spf1 include:spf.protection.outlook.com -all"
CNAME selector1._domainkey → selector1-contoso-com._domainkey.contoso.onmicrosoft.com
TXT _dmarc "v=DMARC1; p=quarantine; rua=mailto:dmarc@contoso.com"

19. Frequently asked questions

What should I migrate first?

Pilot with representative roles (sales/finance/support). Then OneDrive and standard mailboxes; after that, SharePoint and Teams by business criticality.

Can I keep coexistence for weeks?

Yes. Use Directory Sync for objects and (if needed) Email/Domain Rewrite for a unified brand, plus cross-tenant Free/Busy. :contentReference[oaicite:22]{index=22}

How do I cut tickets on Day 1?

Deploy the Desktop Update Agent to reconfigure Outlook, OneDrive, and Teams automatically, and include a quick Teams sign-out/sign-in check. :contentReference[oaicite:23]{index=23}

Are there API limits?

Yes—Graph and service-specific throttling applies; plan pilots, waves, and off-peak schedules. For Teams migration mode, follow Microsoft’s import/complete steps. :contentReference[oaicite:24]{index=24}

20. Official resources

  • Quest — On Demand Migration (overview) :contentReference[oaicite:25]{index=25}
  • Quest — On Demand Migration (User Guide) :contentReference[oaicite:26]{index=26}
  • Quest — Desktop Update Agent (User Guide) :contentReference[oaicite:27]{index=27}
  • Quest — On Demand Email/Domain Rewrite :contentReference[oaicite:28]{index=28}
  • Quest — On Demand Directory Sync :contentReference[oaicite:29]{index=29}
  • Microsoft — Import messages to Teams (migration mode) :contentReference[oaicite:30]{index=30}
  • Microsoft Graph — Throttling limits :contentReference[oaicite:31]{index=31}
  • Microsoft — Create DNS records for Microsoft 365 :contentReference[oaicite:32]{index=32}
  • Quest — Exchange Online pre-requisites (EWS & licensing)
  • Quest — ODM overview video (Teams/DUA highlights) :contentReference[oaicite:34]{index=34}

Explore how we orchestrate end-to-end migrations: Microsoft 365 migrations, Azure architecture, and all our services.

21. Conclusion + CTA

A tenant-to-tenant migration with Quest On Demand is far smoother when you follow a clear path: solid consents and identity matching, wave-based pre-staging, well-designed coexistence, and a desktop switch with DUA so users barely notice the change. With measurable pilots, known limits, and honest communications, go-live becomes predictable.

Want MSAdvance to run it end-to-end?

We handle everything: assessment, coexistence, Exchange/OneDrive/SharePoint/Teams migration, domain cutover, security, and adoption.

Contact MSAdvance Explore our migration service

· We can also help with Modern Workplace and Azure Architecture · All services

Share

Related posts

November 11, 2026

Microsoft 365 tenant-to-tenant migration: a complete guide


Read more
Puentes diferenciados para colaboración de identidades y traslado de documentos / Separate bridges for identity collaboration and document migration
October 24, 2026

Cross-tenant synchronization vs tenant-to-tenant migration: differences and use cases


Read more
Documents connected to a blue cloud through migration validation checkpoints
October 12, 2026

Microsoft 365 migration acceptance: evidence before sign-off


Read more
September 20, 2026

How to Choose a Microsoft 365 Migration Company: 15 Key Criteria


Read more
MSAdvance
Microsoft 365 · Azure · Cybersecurity

Specialist consulting for Microsoft 365, Azure and cybersecurity.

MSAdvance provides Microsoft 365 consulting, migration, Modern Workplace, cybersecurity, Azure, managed services and Microsoft licensing. We work alongside the client team with a clearly defined scope, technical documentation and control throughout each phase of the project.

Microsoft Partner 25+ Microsoft certifications Established 2010 International projects
Project enquiries

Would you like us to review a project or prepare a proposal?

Send us the current environment, planned scope and target date. We will review the information and come back with the next steps and, where appropriate, a proposal.

Contact MSAdvance View success stories
info@msadvance.comInternational remote delivery
01 Services
  • All services
  • Microsoft 365 Consulting
  • Microsoft 365 Migrations
  • Modern Workplace
  • Microsoft Cybersecurity
  • Microsoft Azure
  • Managed Services
  • Microsoft Licensing
02 MSAdvance
  • About Us
  • Microsoft Partner & Certifications
  • Success Stories
  • Our Methodology
  • Trust Center
  • Blog & Technical Guides
03 Contact
General info@msadvance.com
Projects sales@msadvance.com
Support support@msadvance.com
Delivery International remote delivery
Remote delivery for organizations across Europe, the Americas and other international markets. Contact form

© 2026 MSAdvance. All rights reserved.

Legal NoticePrivacyCookies
ESEN
MSAdvance
Manage consent
To provide the best experiences, we use technologies such as cookies to store and/or access device information. Consenting to these technologies will allow us to process data such as browsing behaviour or unique IDs on this site. Not consenting or withdrawing consent may adversely affect certain features and functions.
Functional Always active
The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
The technical storage or access is used exclusively for statistical purposes. The technical storage or access is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance by your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot be used to identify you.
Marketing
The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes.
  • Manage options
  • Manage services
  • Manage {vendor_count} vendors
  • Read more about these purposes
View preferences
  • {title}
  • {title}
  • {title}