
Homepage " IT infrastructure " Microsoft 365 Tenant-to-Tenant Migration
Microsoft 365 Tenant-to-Tenant Migration
Identities, mailboxes, Teams, and SharePoint—without data loss or disruption to business operations
Migrating and consolidating Microsoft 365 tenants is one of the most challenging projects in the Microsoft ecosystem. Every decision regarding which tool to choose—CTIM, ShareGate, BitTitan, or Quest—depends on a single variable that most teams evaluate too late.
Scope of the migration—what we're transferring
| Migration Area | What We Transport | As part of the standard scope |
|---|---|---|
| Identities and Accounts | Users, groups, contacts, guest accounts | Yes |
| Exchange Online Mailboxes | Email, calendars, contacts, archives | Yes |
| SharePoint Online | Pages, document libraries, permissions | Yes |
| OneDrive for Business | User Files and Folders | Yes |
| Microsoft 365 Groups | Groups and Related Resources | Yes |
| Microsoft Teams |
Channels, Teams files, team structure Chat history — the scope depends on the tool you choose | It depends on the tool |
| Local Active Directory |
Hybrid environments require a separate planning layer See the AD migration service → | Optional |
| Microsoft 365 Licenses | Licensing consulting and support for transferring licenses to a new tenant | Optional |
What does the migration project look like?
1
2
3
4
5
6
Frequently Asked Questions
The time required depends on the scale of the project and the scope of the elements being migrated. At ISCG, we most often carry out projects involving between 100 and 500 accounts—with this volume, the migration is usually completed within a few weeks. We complete projects involving up to 1,000 users within one month. We set the schedule after analyzing the environment—based on this analysis, we can provide a realistic timeframe for a specific organization, rather than an estimate.
Pricing is always customized, as the cost of a project depends on several factors: the number of users and accounts, the volume of email data, the location and method of archive management, the scope of migrated components (mailboxes, Teams, SharePoint, OneDrive), and the complexity of the environment. Projects for organizations with a simple architecture and a single location start at several tens of thousands of zlotys. Multi-location projects with a high degree of complexity—featuring extensive archives and a wide range of services being migrated—can reach several hundred thousand zlotys.
A well-planned tenant-to-tenant migration does not require any production downtime. We migrate data in phases or during a maintenance window—depending on the scale of the project and the organization’s requirements. Users maintain uninterrupted access to email and files throughout the entire migration process. We determine the detailed cutover model during the pre-implementation analysis.
Hybrid environments require an additional layer of planning.
There is no single "best" tool—the decision depends on the environment's architecture, the presence of a local AD, the scope of the content being migrated, and the pricing model. You can find a detailed comparison in our article
M365 Tenant-to-Tenant Migration – Which Entra ID Migration Tool Should You Choose?

