Summary: An Office 365 tenant to tenant migration involves moving mailboxes, OneDrive data, and SharePoint sites from one Microsoft 365 environment to another. This is usually triggered by company mergers or rebranding. Because Microsoft does not provide a “one-click” button for this, you must choose between a manual PowerShell-based migration or a professional automated Office 365 Tenant Migration tool to ensure zero data loss.
The Microsoft 365 Cross Tenant migration can’t be accomplished without completing the pre-migration tasks. Here, we will know all about the basics that one should know before the migration and Office 365 tenant-to-tenant migration best practices.
Phase 1: Pre-Migration Planning & Requirements
The success of an Office 365 tenant to tenant migration depends entirely on the preparation phase. In 2026, Microsoft’s security protocols and data throttling are stricter than ever. Skipping a single technical prerequisite here can cause the entire migration to fail mid-way.
To ensure a smooth Office 365 to Office 365 migration, you must complete these four critical steps before moving a single byte of data.
1. Comprehensive Data Inventory
Before starting, you must know exactly what you are moving. This isn’t just about mailbox size; it’s about the type of data.
- Mailboxes – Identify primary mailboxes, shared mailboxes, and archive folders.
- SharePoint & OneDrive – Calculate the total storage and note any custom permissions or “Unique Permissions” that may not transfer easily.
- Teams Data – Note that Teams chat and channel history require specific API permissions to migrate.
2. Identity Matching (SMTP & UPN)
For a seamless user experience, the source identity must match the target identity.
- SMTP Mapping – Create a CSV file mapping every source email address to its corresponding target email address.
- UPN Consistency – Ensure User Principal Names (UPNs) are ready in the target tenant. If the identities don’t match exactly, users will lose access to their encrypted files and calendar invites.
3. Target Tenant Licensing
This is a common “Day 0” failure. You cannot migrate data into a “Shadow” or “Unlicensed” user account.
- Active Licenses – Ensure the target tenant has enough active licenses (E3, E5, Business Premium, etc.) to cover every migrating user.
- Service Plans – Verify that the specific services (like Exchange Online or OneDrive) are provisioned and “Green” in the Microsoft 365 Admin Center before the migration starts.
4. The Communication & Cutover Plan
An Office 365 tenant migration is a major event for end-users.
- The “Blackout” Window – Define exactly when the MX records will switch.
- User Instructions – Provide a clear guide for users on how to recreate their Outlook profiles and re-sync their mobile devices once the migration is complete.
Expert Note for Admin:– To avoid “Access Denied” errors, we recommend creating a dedicated “Migration Admin” account in both the Source and Target tenants. This account should have Global Administrator rights and, crucially, should have MFA (Multi-Factor Authentication) temporarily disabled or set to “Trusted IP” during the migration to prevent automated scripts or tools from getting blocked by security prompts.
Phase 2: Domain Preparation and DNS Settings
This phase is often considered the most “high-stakes” part of an Office 365 to Office 365 migration. Because a single domain (e.g., @https://www.google.com/search?q=yourcompany.com) cannot exist in two Microsoft 365 tenants at the same time, precision in your DNS timing is the difference between a seamless switch and a total email blackout.
1. The Domain Removal Rule (Identity Conflict)
Microsoft uses a “Unique Identity” system. Before you can verify your custom domain in the Target Tenant, it must be completely removed from the Source Tenant.
- The Challenge: This removal triggers a period where your custom domain is “in limbo.”
- The Solution: You must strip the custom domain from all user objects, groups, and aliases in the source tenant and revert them to the initial .onmicrosoft.com address before the domain can be released.
2. TTL (Time to Live) Adjustment: Speeding Up Propagation
DNS changes don’t happen instantly; they depend on the TTL (Time to Live) settings of your records. If your TTL is set to 24 hours, the rest of the internet might still try to send mail to your old tenant for a full day after you’ve moved.
- The Expert Move: At least 72 hours before the migration, log into your DNS provider (GoDaddy, Cloudflare, etc.) and lower the TTL of your MX and Autodiscover records to 3600 seconds (1 hour) or less.
- The Result: When you finally swap the records to point to the new tenant, the change will propagate globally in minutes rather than hours, significantly reducing downtime.
3. Coexistence: The .onmicrosoft.com Email Forwarding
To make sure no emails are lost during migration, we temporarily use an onmicrosoft.com address to safely route emails until the domain transfer is complete.
- How it works – By setting up “Forwarding” from the source .onmicrosoft.com addresses to the target .onmicrosoft.com addresses, mail continues to flow through Microsoft’s internal backbone even while your public-facing custom domain is technically offline.
- Why it’s critical – This ensures that if a client sends an email during the 30-minute window while you are verifying the domain in the new tenant, the message is queued and delivered rather than bouncing back with a “User Not Found” error.
Pro Tip from the Field:- Always verify your “Identity Cleanup” twice. If even one hidden “Discovery Mailbox” or “Distribution Group” is still using the custom domain in the source tenant, Microsoft will block the domain removal, potentially delaying your entire migration schedule by hours.
Phase 3: Executing the Office 365 to Office 365 Migration
Once your planning is done and your DNS is ready, it is time to move the data. Deciding which method to use for your Office 365 tenant to tenant migration depends on two things: how much data you have and how much downtime your company can afford.
Step 1: The Manual Approach (Best for < 10 Users)
The manual method is essentially a “Download and Upload” process. It is free, but it is very slow and involves a high risk of human error.
- Exporting to PST: You must log into every individual user’s Outlook account and manually export their entire mailbox into a PST file.
- Re-importing to the New Tenant: Once the new accounts are ready in the target tenant, you must manually import those PST files back into the new Outlook profiles.
- The Big Limitations: This method only moves emails. You will lose all Teams chat history, SharePoint sites, and OneDrive files. It also creates a massive amount of “local” data traffic, which can crash your office internet if you try to do too many users at once.
Step 2: The Professional Approach (Shoviv Solution)
For a business-grade Office 365 tenant to tenant migration, using a professional tool is the only way to ensure 100% data integrity. It connects directly to the Microsoft cloud (Tenant to Tenant) without downloading files to your local computer.
- Auto-Mapping Technology – Instead of matching users one by one, the tool automatically matches source users to target users based on their email addresses. This saves hours of manual work and prevents data from going to the wrong person.
- Filter-Based Migration – You don’t have to move 10 years of data at once. You can use “Date Filters” to move only the last 3 months of email first. This allows your team to start working in the new tenant immediately while the older archives move quietly in the background.
- Advanced Job Scheduling – Migration can be heavy on your network. With job scheduling, you can set the migration to start at 10:00 PM and stop at 6:00 AM. This ensures that your company’s bandwidth is fully available for your employees during work hours.
Why Professionals Skip the Manual Way
In 2026, data isn’t just email. It’s collaboration. Manual PST moves are “disconnected”—they break the link between your files and your conversations. A professional Office 365 to Office 365 migration tool keeps everything linked, ensuring that when a user logs in on Monday morning, their folders, permissions, and attachments are exactly where they left them.
Overview of Shoviv Exchange Server Suite (Professional Office 365 Tenant Migrator)
Shoviv Exchange Server Suite is a multitasking, advanced software solution for Office 365 Tenant to Tenant migration. Moreover, the software facilitates user-centric features and processing to effortlessly migrate. Have a look at its features:
- The software provides proficient, accurate, and handy Office 365 Tenant to Tenant migration.
- It allows adding multiple mailboxes as a source to export. Being a multi-tasking tool, it can add EDB Files, Office 365, and Exchange Server as a source.
- Moreover, the software offers to export Office 365 mailboxes into the on-premise Exchange mailboxes, Office 365 mailboxes, and Outlook PST
- To facilitate users, it provides a filter option, a search option, a folder mapping option, and a preview option.
- The Shoviv Exchange Server Suite provides the complete recovery of EDB, PST, and OST
- A free demo version of this software is also available to download.
Note: Shoviv Software offers multiple utilities to handle various migration tasks, like:
- OneDrive to OneDrive Migration: Migrate Multiple OneDrive accounts in a single go.
- SharePoint Migration: Speedily migrate SharePoint sites to another tenant.
Avoiding Throttling and Data Loss (Technical Architecture)
The biggest risk in an Office 365 tenant to tenant migration isn’t moving the data—it’s getting blocked by Microsoft while doing it. To ensure a successful move, you need to understand the “under-the-hood” engineering that prevents data loss and server-side delays.
1. Modern Connectivity: Microsoft Graph API vs. Legacy IMAP vs. EWS Method
In the past, migrations relied on IMAP, an old protocol designed only for basic email text. IMAP is “blind” to modern Office 365 features like Teams chats, shared calendars, and complex permissions.
For a decade, EWS was the professional standard for migration. It can “see” calendars and contacts, but it has reached its end of life. Microsoft has officially scheduled the full retirement of EWS for October 2026. Starting now, many tenants are already seeing EWS access blocked for Kiosk and Frontline (F1/F3) licenses.
The Modern Way: A professional migration tool uses the Microsoft Graph API. This is the native language of the Microsoft 365 cloud. It allows for a deeper, faster connection that can “see” and move everything—including your folder structures, contact groups, and file permissions—with much higher security.
2. Managing “Requests Per Second” (Throttling Challenge)
Microsoft 365 is a shared environment. To keep the service fast for everyone, Microsoft uses “Throttling.” If you try to move too much data too fast, Microsoft will flag your account as “suspicious” and temporarily block your migration (often showing a 429 Too Many Requests error).
How to Bypass It: Professional tools use Smart Request Management. Instead of hitting the server with a “wall” of data, the tool monitors Microsoft’s response in real-time. If it senses a throttle is coming, it automatically adjusts the “threads” and “pacing” of the migration to stay just under the limit, keeping the data flowing 24/7 without getting blocked.
3. Preserving Metadata Integrity
When you move an email manually, it often looks “new” to the target tenant. You might lose the original “Received Date,” or all your emails might suddenly show as “Unread.” This destroys your ability to search through old records.
- Metadata Preservation: A high-level migration ensures that the Digital Fingerprint of every email stays 100% intact. This includes:
- Header Accuracy: Keeping the original “From,” “To,” “CC,” and “BCC.”
- Time-Stamping: Ensuring the “Date Received” doesn’t change to today’s date.
- Folder Hierarchy: Keepingn your “Invoices > 2026 > Paid” structure exactly as it was.
- Read/Unread Status: Saving your users from having to sort through thousands of “new” messages on Monday morning.
Why “Incremental Migration” Matters?
During a large Office 365 tenant to tenant migration, users continue to receive mail in the source tenant until the very last second. Shoviv Exchange Server Suite uses Incremental migration to identify only the new emails that arrived since the last backup. This allows you to do a “pre-migration” of 99% of the data and then a 5-minute “delta sync” for a perfect, zero-downtime cutover.
Phase 4: Post-Migration Cleanup & Verification
The data has moved, but your Office 365 tenant to tenant migration isn’t finished until the “lights are on” for every user. Phase 4 is about the final cutover—ensuring that new emails arrive in the right place and that users can actually access their data on “Day 1.”
1. Finalizing DNS Records: The “Switch”
Now that the data is in the Target Tenant, you must tell the rest of the world where to send new emails. This requires updating your DNS records to point away from the old source and toward the new target.
- MX (Mail Exchange) Record: Update this to the new Microsoft 365 value provided in your target admin center. This stops mail from going to the old tenant.
- SPF, DKIM, and DMARC: These are critical for Email Deliverability. If you don’t update your SPF record to include the new tenant’s IP range, your outgoing emails will likely end up in the recipient’s spam folder.
- Autodiscover: Update the CNAME record for Autodiscover so that Outlook apps can find the new mailbox automatically.
2. The Outlook Profile Reset (Why It’s Mandatory)
A common mistake in an Office 365 to Office 365 migration is trying to use the old Outlook profile. Because the “Unique ID” of the mailbox has changed, the old profile will constantly prompt for a password or show “Disconnected.”
- The Fix: Every user must create a New Outlook Profile (Control Panel > Mail > Show Profiles > Add).
- The Benefit: A fresh profile downloads the newly migrated folder structure correctly and prevents local “cached” errors from the old tenant from interfering with the new connection.
3. Data Verification: The “Day 1” Checklist
Before telling the team that the migration is 100% successful, perform a final audit. A professional Office 365 tenant migration isn’t complete without a verification report.
- Spot Check Mailboxes: Verify that the folder hierarchy (Inbox, Sent, Custom Folders) matches the source.
- OneDrive & SharePoint Audit: Ensure that “Shared with Me” permissions and internal file links are functioning.
- Calendar Sync: Confirm that upcoming meetings and recurring appointments have migrated without losing the “Organizer” status.
Post-Migration Pro Tip: Don’t Delete the Source Tenant Immediately. Even after a successful cutover, keep the source tenant active for at least 15–30 days. This acts as a “Safety Net” in case a user realizes a specific legacy archive or a hidden shared mailbox was missed during the initial discovery phase.
Wrapping up:
By going through the article, we can easily conclude that the manual Office 365 Tenant to Tenant migration is not a work of genius, as it comes with too many glitches and hurdles. Doing pre-migration tasks is good for always. And to migrate professionally and effortlessly with the hundred percent efficiency, Shoviv Exchange Server Suite is the best choice. Moreover, to check its work and efficiency, it also provides a demo/trial version of the software, which allows exporting the first 50 files per folder.
Frequently Asked Questions:
It depends on data volume. Manual moves can take days of downtime. Automated tools like Shoviv allow for background syncing, meaning the final “cutover” often takes less than an hour, regardless of mailbox size.
No. The migration process creates a copy. Your original data remains safe in the source tenant until you choose to decommission it or cancel the subscription.
Yes. While manual PST methods only handle email, a professional migration tool can run parallel jobs to move Mail, OneDrive, and SharePoint data simultaneously, saving significant time.
Yes, Shoviv also provides other utilities for the M365 Tenant to Tenant Migration. Users can migrate OneDrive to OneDrive and SharePoint to SharePoint. With an appropriate license you can achieve each task secretly.
Yes, you can. A free demo of this tool is available to download. It allows processing the first fifty items per folder.
Yes, Shoviv provides a 24*7 technical support facility for all Shoviv’s utilities. If you face any issues with Shoviv’s tool, feel free to contact Shoviv’s technical support team.
