Microsoft 365 Tenant-to-Tenant Migration Tool

Yes. Migrating data between any two different Office 365 (Microsoft 365) tenants is exactly what EdbMails Office 365 Tenant to Tenant Migration Tool is built for. It's a common task during company mergers, acquisitions, and corporate restructures, and the cross-tenant workflow is the same regardless of which scenario is driving the migration.

Microsoft 365 cross-tenant migration is the process of migrating mailboxes and workloads, including SharePoint, OneDrive, and Teams, from one Microsoft 365 tenant to a separate, independent tenant. It differs from an in-tenant migration because the source and target exist as fully separate Microsoft 365 environments with their own domains and licensing.

 Click here to know the steps to perform Office 365 Cross Tenant Migration.

Connect EdbMails to the source Microsoft 365 tenant, select the mailboxes and workloads to migrate, connect to the target tenant, confirm the mailbox mapping, and start the migration. See the step-by-step migration guide for the full walkthrough.

Migration time depends on data volume, mailbox count, available bandwidth, and Microsoft server response at the time of migration. EdbMails controls throughput through parallel mailbox migration, parallel item processing across multiple threads, automatic throttling management, and full restart/resume support if a job is interrupted. Parallel migration produces the largest speed gain, since migrating several mailboxes between tenants at the same time cuts total runtime compared to a sequential approach.

A few Microsoft-imposed limits affect migration speed regardless of migration tool:

• Individual items are capped at 25 MB by default; this can be increased to 150 MB.
• Throttling policies on both source and target tenants can affect transfer rate.
• The type and volume of data being moved affects speed.
• Network setup at the migration machine affects throughput.

For more detail, refer to this Microsoft article.

To increase throughput on a tenant to tenant project, consider increasing the number of parallel migrations or increasing throttling policy limits in Exchange Online. Learn more about increasing migration speed

Yes. The Free Trial lets you test tenant to tenant features before purchase, migrating every mailbox in scope with up to 30 items per folder transferred. That's enough to evaluate mapping behavior, incremental sync and reporting.

Yes. Language support applies regardless of source or target tenant locale. Folder names, message body content, and special characters, including accented letters, CJK characters, and right-to-left scripts, are preserved on the target.

The tool covers emails, contacts, calendars, tasks, journals, and notes across primary mailboxes, shared mailboxes, public folders, and archive mailboxes.

Yes. Shared mailboxes, In-Place Archive mailboxes, and Public Folders all migrate between Office 365 tenants with their data intact. Public folders carry over with subfolders, mail-enabled folders, items, and permission structure preserved; In-Place Archives keep historical email accessible on the destination; and shared mailboxes arrive with team-collaboration workflows functional on the target from day one.

Yes. SharePoint Online, OneDrive for Business, and Microsoft Teams are each supported as separate workload migration modules alongside mailbox migration.

For migrating mailboxes, shared mailboxes, public folders, and archive mailboxes, the Office 365 Migration license is required. Each fresh source email address consumes a license. Public folders consume 50 mailbox licenses, which lets you migrate unlimited public folders from the same domain.

 See Office 365 Migration pricing details.

For SharePoint, OneDrive, Teams, Channels, and 1:1 chats, the 'SharePoint + OneDrive + Teams' Migration license is required. The license count is based on the number of source sites for SharePoint and Teams, plus the number of OneDrive users whose data you want to migrate. Buying licenses in bulk saves you more, and any unused licenses stay available for future use.

 See 'SharePoint + OneDrive + Teams' Migration pricing details.

Yes, you can choose to let EdbMails automatically create mailboxes on the target Office 365 tenant.

 Click here to know more about automatic mailbox creation.