Migrating from one Microsoft 365 "tenant" (your organization's dedicated space for Microsoft services like email and files) to another can seem like a monumental task, especially if you're not a tech expert. This often happens during company mergers, acquisitions, or organizational restructuring. But don't worry! Tools like MigrationWiz by BitTitan are designed to make this process as smooth as possible. This guide will walk you through each step in simple, easy-to-understand language.
Think of a Microsoft 365 tenant as your company's digital headquarters. A tenant-to-tenant migration is like moving all your digital assets – emails, documents, calendars, and team collaboration spaces – from an old headquarters to a new one. MigrationWiz acts as your expert moving company, handling the heavy lifting for you.
MigrationWiz is a cloud-based tool, meaning you don't need to install any software on your computer. It automates the transfer of data, which helps to:
Good preparation is the secret to a smooth migration. This phase happens before you even log into MigrationWiz.
You'll need administrator-level access to both your current Microsoft 365 tenant (the "Source") and the new Microsoft 365 tenant (the "Destination"). If you don't have this, you'll need to work closely with someone who does. These admin accounts allow MigrationWiz to access the data it needs to move.
Make a list of all the data you need to transfer. Common items include:
Knowing exactly what needs to move helps you choose the right type of migration project in MigrationWiz.
Before any data can be moved, user accounts must exist in the new (Destination) tenant. For example, if Jane Doe's email is jane.doe@oldcompany.com in the Source, you'll need to create an account for her in the Destination, like jane.doe@newcompany.com.
Ensure that all user accounts in the Destination tenant have the necessary Microsoft 365 licenses assigned to them before you start migrating their data. If a user doesn't have a license for, say, Exchange Online, their mailbox data cannot be migrated to the new tenant.
If you don't already have one, create an account on the BitTitan website. This will give you access to the MigrationWiz dashboard, your control center for the migration.
MigrationWiz requires licenses to move data. Typically, you'll need one license per user whose data is being migrated (e.g., a User Migration Bundle license which can cover mailboxes, documents, and personal archives). BitTitan offers different license types, including Tenant Migration Bundles for comprehensive projects. Purchase these through your MigrationWiz account.
To help you understand the overall flow, here's a mindmap outlining the key stages of a tenant-to-tenant migration project using MigrationWiz. This illustrates the journey from initial planning through to completion and support.
With preparation complete, it's time to configure your migration project within the MigrationWiz platform.
Log in to your MigrationWiz account.
From the dashboard, click on "Create Project." MigrationWiz will ask you what type of migration you want to perform. For a full tenant-to-tenant move, you might create separate projects for Mailboxes, Documents (OneDrive/SharePoint), and Teams, or use a bundled project type if available.
Give your project a clear name, like "Company X to Company Y Mailbox Migration."
Endpoints tell MigrationWiz where to get the data from (Source) and where to put it (Destination).
You'll need to create a "New Endpoint" for your Source. Select "Microsoft 365" as the type and provide the admin credentials for your old tenant. MigrationWiz will guide you through granting necessary permissions, which usually involves signing in with your admin account and consenting to allow MigrationWiz to access the data.
Similarly, create a "New Endpoint" for your Destination. Select "Microsoft 365" and provide the admin credentials for your new tenant, again granting necessary permissions.
Now, tell MigrationWiz whose data to move.
If you're migrating mailboxes, you'll add users to the project. You can do this one by one, or for many users, you can "Bulk Add" them using a CSV file (a simple spreadsheet). The CSV file typically needs columns for the Source Email Address and the Destination Email Address.
Example CSV content:
SourceEmail,DestinationEmail
john.doe@oldcompany.com,john.doe@newcompany.com
jane.smith@oldcompany.com,jane.smith@newcompany.com
Upload this file to MigrationWiz. It will then list all the users ready for migration.
Before you start the actual migration, it's vital to check that MigrationWiz can connect to both tenants correctly for all users.
Select all users in your project and run the "Verify Credentials" action (often found under the "Start" button menu). This tests the connection for each user and flags any access issues. Resolve any errors before proceeding. This might involve checking permissions or password details.
MigrationWiz offers several advanced options:
It's wise to perform a small test migration with a few non-critical user accounts. This helps you get familiar with the process and identify any potential issues before migrating everyone.
Select a few users, choose the "Full Migration" option (or a Pre-Stage followed by Full), and start it. Check their destination accounts afterwards to ensure data (emails, calendar appointments, files) has arrived as expected.
The following radar chart provides a visual comparison of key aspects when using a tool like MigrationWiz versus attempting a more manual or less automated migration approach. This highlights areas where MigrationWiz typically excels, contributing to a smoother process for non-technical users.
This chart illustrates that MigrationWiz generally scores higher in areas beneficial for a smooth, less technical migration, such as automation and ease of setup, while requiring less technical skill.
If you've opted for a pre-stage, select your users and start the "Pre-Stage Migration." Choose what to migrate (e.g., mail older than 30 days, calendars older than 14 days). This can run in the background over several days if needed, without impacting users.
Once the Pre-Stage is complete for all users, and you are ready for the final cutover (switching users to the new tenant), perform a "Full Migration" pass. This pass migrates all new and changed items since the last pass (it's a "delta" sync). This is typically scheduled during a weekend or off-peak hours to minimize any disruption.
The MigrationWiz dashboard provides real-time updates on the migration. You can see:
If errors occur for specific users, you can often select those users and "Retry Failed Items."
Once MigrationWiz reports that the migration is complete, there are still a few important things to do.
Have a few users log in to their new Microsoft 365 accounts and confirm that their emails, calendars, contacts, and files are present and correct. Spot-check a few mailboxes and OneDrive accounts.
This is a critical step if you are keeping the same email domain (e.g., yourcompany.com). You'll need to update your domain's MX records (Mail Exchange records) in your DNS settings to point to the new Microsoft 365 tenant. This directs new incoming emails to the new mailboxes. This change can take some time to propagate across the internet (usually a few hours, but can be up to 48). Plan this carefully, often over a weekend. Your IT administrator or domain registrar can help with this. MigrationWiz does not do this step; it must be done manually.
Communicate clearly with your users about the migration: when it's happening, what to expect, and any actions they need to take (like logging into their new accounts or reconfiguring email on their phones).
Users will likely need to set up new Outlook profiles on their computers to connect to their mailboxes in the new tenant. Mobile devices will also need to be reconfigured for email. BitTitan offers a separate tool called DeploymentPro that can automate Outlook profile configuration, which can be a huge time-saver.
BitTitan's DeploymentPro can help automate Outlook profile configuration for users after migration.
Once you are completely confident that all data has been successfully migrated, everything is working correctly in the new tenant, and users are comfortable, you can begin the process of decommissioning the old (Source) tenant. Do not rush this step. Keep the source tenant accessible for a period as a backup or for reference until you are absolutely sure it's no longer needed.
For a visual walkthrough of the MigrationWiz interface and initial setup, the following video provides a beginner-friendly introduction. Watching this can help you become more familiar with the tool before you start your own project.
A beginner's introduction to using BitTitan's MigrationWiz tool.
Here's a quick reference table summarizing the main phases and key actions involved in your MigrationWiz tenant-to-tenant migration:
| Phase | Key Actions | Focus for Non-Technical Users |
|---|---|---|
| 1. Preparation | Understand scope, secure admin access, prepare destination accounts & licenses, get MigrationWiz account & licenses. | Clearly list what data needs to move. Ensure user accounts are ready in the new "home." |
| 2. Project Setup | Create MigrationWiz project(s), configure Source & Destination Endpoints, add users/items (e.g., via CSV). | Follow on-screen prompts carefully. Use the CSV template for adding many users. |
| 3. Configuration & Testing | Verify credentials, set migration options (like Pre-Stage), run a test migration for a few users. | Always run "Verify Credentials." Test with a small group first to catch surprises. |
| 4. Execution | Run Pre-Stage migration pass, then Full (Delta) migration pass. Monitor progress. | Schedule main migration for off-hours. Keep an eye on the dashboard for status. |
| 5. Post-Migration | Verify data, perform DNS cutover, communicate with users, reconfigure devices, eventually decommission source. | Plan user communication. Get help for DNS changes if needed. Don't rush decommissioning. |
To deepen your understanding or explore related topics, consider these queries: