Microsoft 365 migration tools: comparison and selection

How to compare migration tools beyond just looking at brand names

Microsoft 365 migration tools should be evaluated against a matrix of the actual project scope. Each row should represent an object or function that must be preserved, with each tool option indicating whether it migrates, transforms, requires manual intervention, or excludes that item. A generic claim such as “supports Teams” does not clarify how chats, meetings, files, applications, or specific channel types are handled.

The analysis must also distinguish between copying, moving, and preserving data for reference purposes, as these actions can have different effects on the source and destination environments. Before selecting a tool, it is essential to verify requirements regarding identity, licensing, permissions, destination readiness, and error handling. The most suitable option is the one that aligns with the project design and allows for the verification of results.

In a comparative test, two different solutions might copy the same document yet produce different outcomes regarding metadata or permissions. Therefore, a pilot phase should use a consistent data sample and uniform evaluation criteria. The resulting report should document any discrepancies and necessary manual tasks, ensuring that the license cost does not obscure the additional effort required by each alternative.

Operational capabilities to evaluate during a pilot

The ability to investigate errors is just as important as the ability to initiate a data transfer. The team must be able to locate the affected item, understand the root cause, and know the consequences of repeating an operation. It is necessary to test how the tool handles retries, subsequent changes, and incremental updates (where supported). Assuming these features are present without verification can jeopardize the entire workflow.

The selection process should also account for the project’s final deliverables: exportable reports, documentation of mappings, a record of granted permissions, and the steps required to revoke access that is no longer needed. If multiple tools are involved, their functions must be clearly defined to prevent them from modifying the same content without established coordination. Any combination of tools must be justified by specific requirements and validated before being applied to the entire environment.

Before comparing tools: define what you are migrating

One of the most common mistakes in Microsoft 365 projects is to start by asking: “Should we use Quest, ShareGate, or BitTitan?” The right question should come later. First, we need to know: where we are starting from and where we want to end up..

Migrating 5 TB of folders from a server can be conceptually much simpler than migrating 500 GB from SharePoint—if the latter contains unique permissions, metadata, sites linked to Teams, and automations. Therefore, volume alone does not determine complexity..

The four categories of Microsoft 365 migration tools

Before looking at specific brands, it is best to categorize tools by their function.

This distinction prevents the comparison of tools that address completely different problems.

What Microsoft currently offers for migrations

Microsoft’s native catalog has grown considerably. Currently, we can distinguish between two broad scenarios. Migrations from external platforms to Microsoft 365. Microsoft primarily uses Migration Manager and specific tools, such as SPMT, to ingest content from file shares, SharePoint Server, and various cloud services.

Migrations between Microsoft 365 tenants

Microsoft provides:

It is important to understand that these native tools do not automatically consolidate a full Microsoft 365 migration into a single process.Identity, domains, Teams structures, applications, devices, and other components still require specific planning. Official reference: Microsoft – Microsoft 365 Migration Overview.

SharePoint Migration Tool (SPMT)

SharePoint Migration Tool This is a free tool from Microsoft, primarily intended for moving content from SharePoint Server and file shares to Microsoft 365. It is a very useful tool when the problem to be solved is fundamentally document-related. When is SPMT a good fit? It can be a good option for:

It can also be used to move content into libraries that are subsequently accessed via Teams—though this does not mean that SPMT migrates Microsoft Teams as a complete workload. A key advantage: pre-migration scanning. SPMT can analyze SharePoint Server before the migration begins to identify potential incompatibilities. Microsoft is actively enhancing this specific functionality. Support for the legacy SharePoint Migration Assessment Tool is scheduled to end on October 1, 2026; Microsoft recommends using the SPMT scanning feature to analyze SharePoint Server sites.

When SPMT falls short. SPMT is not a comprehensive tenant-to-tenant migration platform. It is not designed to provide an end-to-end solution for: Exchange Online, Microsoft Teams, chats, identity, domains, applications, or cross-tenant coexistence. Furthermore, one should not assume that existing customizations in SharePoint Server can be directly transferred to SharePoint Online. Conclusion regarding SPMT. It is an official, useful tool that requires no additional license—particularly well-suited for well-defined document migrations.

When a project involves complex transformation, extensive governance, Microsoft Teams, or multiple workloads, it is worth comparing it against specialized platforms. Official reference: Microsoft – SharePoint Migration Tool.

Microsoft Migration Manager

Migration Manager This is the platform that Microsoft currently uses to manage various content migrations into Microsoft 365 from external systems. It should no longer be described solely as a tool for file shares. Microsoft currently integrates content migration scenarios within Migration Manager from:

The goal is to centralize discovery, migration tasks, and monitoring within the Microsoft ecosystem. New “Migration Administrator” role. Microsoft now offers the role of Migration Administrator, designed to grant the necessary access to Migration Manager without requiring the assignment of the full SharePoint Administrator role. From a security perspective, this is a significant improvement, as it aligns more closely with the principle of least privilege.

File shares and agents. For file share migrations, Migration Manager uses agents installed on servers or machines that have access to the source content. Tasks can be distributed across multiple agents and managed from the console. When to use Migration Manager. It is particularly useful when you need to bring large volumes of document-based content from a supported source into Microsoft 365, and the project scope does not require advanced tenant-to-tenant transformation capabilities.

What Migration Manager is not. It should not be confused with Migration Orchestrator.

Official reference: Microsoft – Migrate your content to Microsoft 365.

Mover.io: a recommendation that is now outdated

Mover Still appears in numerous articles about Microsoft 365 migrations. It should no longer be recommended as a primary tool. Microsoft retired Mover for managed migrations and integrated the capabilities to migrate from Google Drive, Box, Dropbox, and Egnyte into Migration Manager.

Native Microsoft tools for tenant-to-tenant migrations

For migrations between two Microsoft 365 tenants, Microsoft currently offers workload-specific tools and an orchestrator for certain user workloads. This makes native capabilities a viable alternative that is worth comparing against third-party products. However, “native” does not necessarily mean simpler, free, or sufficient for every scenario.There are requirements regarding licensing, identity, preparation, PowerShell, and architecture that must be reviewed beforehand.

Microsoft 365 Migration Orchestrator

Migration Orchestrator It is designed to coordinate user data during migrations between tenants. Current Microsoft documentation, published in July 2026, specifies four workloads that can be included when creating a batch:

The primary value of the product lies in coordinating the sequence of related workloads. For example, Microsoft establishes dependencies between mailbox migration and Teams meetings. Migration Orchestrator does not migrate identities. This point is fundamental. Microsoft explicitly states that the technology moves content, not identities. Users must be properly prepared in both the source and destination environments, and a compatible identity mapping is required.

What is excluded. Current documentation explicitly states that Cross-Tenant User Data Migration does not move shared data, such as: Teams, Channels and SharePoint Sites. This does not mean that Microsoft lacks a solution for SharePoint—there is “Cross-Tenant SharePoint Migration”—but rather that such content is not part of the same user data flow handled by the Orchestrator. Licensing. Microsoft currently requires a “Cross-Tenant User Data Migration” license per user for such moves.

Licensing must be reviewed before preparing the project, as the migration will fail if this requirement is not met. A change compared to previous versions. Microsoft’s current documentation now presents “Migration Orchestrator” as a product available to EA, CSP, Web Direct, Small Business, and EDU customers; therefore, one should not rely on older articles that described it merely as a future feature without first verifying the current information.

Official reference: Microsoft – Migration Orchestrator Overview.

Cross-Tenant Mailbox Migration

Microsoft allows for the movement of Exchange Online mailboxes from one tenant to another using native Exchange mechanisms, such as MRS and Exchange Online PowerShell. This is not an IMAP migration, nor does it involve exporting and importing PST files. The recipient must be correctly prepared in the destination environment… MailUser …with the attributes required by Microsoft to link the two objects.

Key areas to review

Following a successful move, Microsoft converts the source mailbox into a “MailUser” object and configures routing to the destination, which facilitates certain coexistence scenarios. Official reference: Microsoft – Cross-Tenant Mailbox Migration.

Cross-Tenant OneDrive Migration

Microsoft also offers a native cross-tenant OneDrive migration solution. A key difference compared to many specialized third-party tools lies in its operational model. It is a “one-and-done” migration process. Microsoft does not support incremental passes or delta migrations using this method. The OneDrive is moved to the destination tenant, and Microsoft leaves a redirect in place from the original location. During a portion of the process, the user’s OneDrive may be set to read-only mode.

Queue capacity. Microsoft currently allows for the scheduling of up to 4,000 OneDrive accounts for migration at any given time. When this might be a good alternative. When a “one-and-done” migration model aligns with the project requirements and there is no need for multiple pre-migration passes. When to consider a specialized third-party tool. When you require: An extended pre-staging phase, multiple delta passes, consolidated reporting across different workloads, data transformations, or a different operational workflow.

Official reference: Microsoft – Cross-Tenant OneDrive Migration.

Cross-Tenant SharePoint Migration

Microsoft now allows for the migration of SharePoint sites between tenants using SharePoint Online PowerShell. This is a significant distinction from older comparisons, which described this capability exclusively as being in “preview” status.

Key features

A particularly important restriction is that the target site must not already exist. The native tool is not designed to merge two SharePoint sites that already contain data. This limitation can be a deciding factor when choosing between Microsoft’s native tools and third-party products that allow for different types of mapping, merging, or restructuring. Official reference: Microsoft – Cross-Tenant SharePoint Migration.

Quest On Demand Migration

Quest On Demand Migration This is a SaaS platform specifically designed for Microsoft 365 tenant-to-tenant migrations. Its primary advantage is the ability to manage various workloads from a single platform, following a workflow that includes discovery, matching, collections, migration, and reporting. What Quest currently covers. Quest currently provides capabilities within its platform for:

Discovery and assessment. One of Quest’s key strengths is its ability to perform discovery prior to execution. For example, in Teams, it can generate data on size, activity, number of channels, and membership, helping to determine which teams should be migrated. Collections. Quest allows objects to be grouped into “collections” to organize pilot programs, departments, and migration waves. This is particularly useful for large-scale projects where managing thousands of users or sites as a single batch is not practical.

Coordination between SharePoint and Teams. Quest correctly distinguishes between migrating a Team and migrating the additional content within its associated SharePoint site. This is important because a Teams migration does not necessarily move every single object existing within SharePoint. Security and permissions. Quest provides a specific reference regarding permissions and, in certain scenarios, allows the use of Sites.Selected to narrow the scope of access to SharePoint and OneDrive.

This may be relevant for organizations that wish to minimize the use of global permissions during a project. When should you consider Quest? Especially regarding: Mergers, acquisitions, carve-outs, multi-workload projects, migrations involving significant Teams and SharePoint usage, hybrid identity, or extended coexistence. Official reference: Quest – On Demand Migration.

ShareGate

For years, ShareGate was primarily associated with SharePoint and Microsoft Teams. By 2026, that description is no longer complete. ShareGate now offers a much broader tenant-to-tenant strategy that encompasses identities, mailboxes, and content.. SharePoint. This remains one of its core strengths. ShareGate allows you to work with: site collections, sites, lists, libraries, documents, folders, items, metadata, permissions, and structure—depending on the features supported in each specific scenario.

Microsoft Teams. The platform enables the migration of elements such as:

Exchange Online. ShareGate now includes tenant-to-tenant migration for Exchange Online. Its offering includes user mailboxes, shared mailboxes, rooms, resources, and archives, as well as various mailbox elements and supported configurations. This means that older comparisons—which would automatically rule out ShareGate whenever Exchange was involved—are no longer valid. Microsoft Entra ID. ShareGate currently offers: Entra ID Migration (in preview).

Allows for the management of users, security groups, Microsoft 365 Groups, memberships, and license assignments within supported plans. As this is a new feature, it is advisable to verify its current status and limitations immediately before starting your project. When to consider ShareGate. Especially when: SharePoint and Teams play a major role, there is a need to reorganize content, a visual interface is required, and the goal is to reduce the number of tools used for a cloud-to-cloud migration.

Official reference: ShareGate – Tenant-to-Tenant Migration.

AvePoint Fly

AvePoint Fly It is a migration platform with broad coverage for both Microsoft 365 and other source environments. It is particularly well-suited for large organizations or projects that, beyond simply moving content, involve significant requirements regarding metadata, permissions, labels, reporting, or governance. Workloads and sources. AvePoint provides support for scenarios including:

AvePoint and identity. AvePoint is expanding Fly to include identity-first migrations and is currently offering migration for Active Directory and Microsoft Entra ID as part of a private preview. Therefore, while this functionality is worth keeping an eye on, it should not be included in project budgets as a generally available capability until its specific availability is confirmed.

A highly relevant topic: migrating from EWS to Microsoft Graph.

Microsoft is retiring Exchange Web Services (EWS) in Exchange Online, and AvePoint is adapting Fly to use Microsoft Graph. As of the August 2026 commercial update for AvePoint Online Services, Fly uses Microsoft Graph by default for supported Exchange Online operations in tenants where Graph is available. However, there are still API gaps for certain content types, such as: Microsoft 365 Group mailboxes, archive mailboxes, and public folders—for which AvePoint is temporarily maintaining EWS support until Microsoft completes the equivalent APIs.

This type of transition is precisely why it is advisable to review a tool’s documentation immediately before starting a project. When to consider AvePoint. Especially regarding: Large organizations, complex consolidations, significant SharePoint and Teams projects, Power Platform, metadata, labels, or governance and reporting requirements. Official reference: AvePoint – Fly Migration.

BitTitan MigrationWiz

MigrationWiz A well-known SaaS platform, primarily for email migrations, though its portfolio also covers other Microsoft 365 workloads. Its model is based on various project types, endpoints, and licensing options. Exchange and email. MigrationWiz remains particularly common for: Exchange Online, Exchange Server, IMAP, Google Workspace, and other email systems. SharePoint, OneDrive, and Teams. BitTitan also offers specific project types for documents and Microsoft Teams.

Therefore, it is important to select the correct project type; do not assume that a mailbox license automatically covers all workloads.

Teams Private Chat: significant change in July 2026

BitTitan updated its migration procedure for Teams Private Chat in July 2026. The current implementation utilizes Microsoft Teams import APIs and supports the migration of: 1:1 chats, group chats, and meeting chats—though with certain limitations. BitTitan currently sets a maximum concurrency of 20 users for these projects. Additionally, some elements cannot be migrated—such as certain external users, Copilot chats, mentions, or specific shared files—which makes a pilot phase especially important.

Multi-pass. The current implementation of Teams Private Chat allows for multiple passes, provided that the final “Clean Up” process has not yet been executed. This can be useful for reducing the amount of pending content prior to the cutover. When to assess BitTitan. Especially when: Email is a key focus; the requirement is for a SaaS platform that offers guided projects, or one where the scope aligns well with the various MigrationWiz bundles.

Official reference: BitTitan – MigrationWiz.

Cloudiway

Cloudiway It covers Microsoft 365 tenant-to-tenant migrations as well as various cross-platform scenarios. Its documentation is organized by workload, allowing for the construction of projects that incorporate different components. Microsoft 365 Tenant-to-Tenant. Cloudiway currently provides guides for:

Microsoft Teams. Cloudiway utilizes Microsoft Teams Import APIs for certain conversation-related processes. Its workflow distinguishes between discovery, preprocessing, and migration. During the preprocessing phase, it can prepare Teams and channels in the destination environment, while the migration phase handles the data included within the project scope. An important aspect: mappings. Cloudiway emphasizes the need to maintain a comprehensive mapping between source and destination users. This makes sense, as Teams, SharePoint, and permissions contain references to identities that must be correctly converted.

When to consider Cloudiway. Especially in scenarios involving: multi-workload, cross-platform, Microsoft 365 tenant-to-tenant, Intune, devices, or coexistence. Official reference: Cloudiway – Migration Documentation.

CodeTwo Office 365 Migration

CodeTwo Office 365 Migration It has a much more specific focus than Quest, ShareGate, or AvePoint. Its specialty is Exchange and mailbox migration. This is not a disadvantage; for certain projects, it is exactly what is needed. What it can migrate.

Automatching and provisioning. CodeTwo provides a guided interface that can create destination mailboxes, assign licenses, and perform source-to-destination matching. Delta Migration. It allows for subsequent migration passes to move items that appeared after the initial migration. This can facilitate a “pre-stage” of mailboxes before the final cutover window. When to consider CodeTwo. When the project is primarily focused on: Exchange Server → Microsoft 365, hosted Exchange → Microsoft 365, or Exchange Online tenant-to-tenant migrations.

If the project also includes SharePoint and Teams, CodeTwo will need to be supplemented with other technology. Official reference: CodeTwo – Office 365 Migration.

PowerShell and Microsoft Graph

PowerShell and Microsoft Graph are involved in virtually all Microsoft 365 projects, but they should not be directly compared to tools like Quest or ShareGate; their functions are different. What we use PowerShell and Graph for:

Microsoft Graph vs. AzureAD/MSOnline. For new development and automation, Microsoft Graph PowerShell should be used whenever a supported alternative exists, rather than building new processes based on the legacy AzureAD or MSOnline modules.

Example: User inventory

Install-Module Microsoft.Graph -Scope CurrentUser

Connect-MgGraph -Scopes "User.Read.All"

Get-MgUser -All -Property Id,DisplayName,UserPrincipalName,Mail,AccountEnabled |
    Select-Object DisplayName,
                  UserPrincipalName,
                  Mail,
                  AccountEnabled |
    Export-Csv "C:\Temp\usuarios.csv" -NoTypeInformation -Encoding UTF8

Example: Exchange Online mailboxes

Install-Module ExchangeOnlineManagement -Scope CurrentUser

Connect-ExchangeOnline

Get-EXOMailbox -ResultSize Unlimited |
    Select-Object DisplayName,
                  UserPrincipalName,
                  PrimarySmtpAddress,
                  RecipientTypeDetails |
    Export-Csv "C:\Temp\buzones.csv" -NoTypeInformation -Encoding UTF8

Scripts must be adapted and tested before being run in a production environment.

A practical comparison of Microsoft 365 migration tools

Which tool to consider based on the workload

Email and Exchange Online. If Exchange is the primary workload, it is worth comparing: Microsoft Cross-Tenant Mailbox Migration, CodeTwo, BitTitan, Quest, ShareGate, AvePoint, and Cloudiway. The relevant questions are: Are there archives, shared mailboxes, delegations, holds, or public folders? Is a pre-stage required? Will there be a period of coexistence? SharePoint. For SharePoint Server, SPMT (SharePoint Migration Tool) may be sufficient. For tenant-to-tenant migrations or more complex environments, it is worth comparing: Microsoft Cross-Tenant SharePoint Migration, ShareGate, Quest, AvePoint, Cloudiway, and BitTitan.

OneDrive. Microsoft’s native solution is attractive if a “one-and-done” migration fits your needs. When multiple synchronizations are required before the final cutover, you should compare it against tools that support an incremental model. Microsoft Teams. Teams warrants a separate comparison. It is not enough for a product sheet to simply state “Teams: supported.” You should ask about:

Fidelity: “migrating” does not mean the same thing across all tools

A table full of green checkmarks can be misleading. Two different tools might both claim to migrate SharePoint, yet yield very different results. SharePoint. You should review: Versions, metadata, unique permissions, content types, term store, hub associations, sharing links, lists, pages, and customizations. Exchange. You should review: Archives, calendars, contacts, inbox rules, auto-replies, delegations, shared mailboxes, resources, meetings, and public folders. Teams. You should review: Message author and date, mentions, attachments, external users, reactions, private channels, Planner, tabs, and meeting links.

OneDrive. You should review: versions, sharing links, permissions, files shared via Teams, and redirects. The term “supported” should always be translated into a specific, functional description.

Pre-migration, deltas, and “one-and-done” models

The ability to perform multiple passes can be a deciding factor in how you design the cutover. Consider 5 TB of data in OneDrive: if a tool allows for pre-migration over several days, the final cutover can be limited to just the new or modified data. If the technology requires a single, definitive move, the planning process will be different.

This point should be reviewed before selecting a tool—not after the licenses have already been purchased.

Coexistence: something often overlooked in feature comparison tables

A migration that takes place over a single weekend versus one that lasts six months are completely different types of projects. During a migration occurring in waves, the following may be required: Mail routing, free/busy availability, cross-tenant Teams collaboration, identity synchronization, temporary domain coexistence, and access to information still residing in the source environment.

Quest, Cloudiway, and other platforms offer specific coexistence capabilities depending on the product. Microsoft also enables coexistence through its own services, though this typically requires coordinating several independent configurations.

Tool permissions and security

A migration platform may need to access a large portion of corporate information. Therefore, in addition to asking what is being migrated, we must also ask: how it accesses the data.

The project must include a decommissioning phase. Following the migration, the following should be reviewed and removed once they are no longer needed: Service accounts, App Registrations, Enterprise Applications, certificates, administrative permissions, and tool-specific consents.

How to compare the true cost of a tool

The license price is only one part of the cost. A proper comparison should take into account:

A more expensive platform may result in a lower total cost if it significantly reduces technical hours. Conversely, a free tool might be the best choice if it truly covers the entire scenario.

The pilot phase should be part of the selection process

Documentation helps rule out certain tools. A pilot project helps confirm your decision.

If a critical feature doesn’t behave as expected, it is far better to discover this during a pilot phase than after migrating 500 users.

A practical method for choosing a migration tool

1. Inventory the environment. Gather actual data on users, mailboxes, OneDrive, SharePoint, Teams, applications, and domains. 2. Define what needs to be preserved. Simply saying “SharePoint” is not enough. Define versions, metadata, permissions, links, and applications. 3. Decide on the cutover approach. A one-time migration versus one involving multiple delta syncs requires different tools. 4. Define the coexistence strategy. Determine how long the source and destination environments will coexist.

5. Review identity requirements. Cloud-only users, hybrid users, AD, Entra ID, and devices. 6. Review applications. Do not select a tool based solely on visible workloads. 7. Compare licensing. Calculate the total cost, not just the unit price. 8. Compare current documentation. Tools are constantly changing. 9. Run a pilot. Test difficult use cases. 10. Make a decision. The final technology for critical workloads should only be decided upon after the pilot phase.

Common mistakes when selecting migration tools

Checklist before purchasing licenses

Frequently asked questions about Microsoft migration tools 365

Is there a better tool for all migrations?

The choice depends on the source, the destination, and the functions the company needs to retain. A solution suitable for email might not address collaboration, permissions, or applications. The comparison should be based on the scope and a representative test, incorporating technical requirements and manual tasks, in addition to licensing costs.

What should a useful tool comparison show?

It should indicate which objects and properties each method handles, along with their requirements, limitations, and expected outcomes. It should also outline how to validate results and correct errors. A simple “yes/no” checklist for each product is insufficient when a migration workload contains components that require different procedures.

How do you compare a native solution with a third-party one?

You evaluate the same scope and verify the results using a common sample set. Factors such as availability requirements, licensing, preparation of identities and the destination environment, and any tasks that fall outside the scope must be considered. The decision should be based on project suitability and evidence from the pilot—not on the assumption that one category of tool is always preferable.

Why is it necessary to test retries and updates?

Because their behavior determines how errors are corrected and how information that changes during the project is captured. Not all methods support the same operations or handle existing elements in the same way. The pilot must document which actions can be repeated, what requires additional preparation, and how to prevent duplicates or inconsistent results.

Final recommendations: there is no single “best” tool; there is only the right tool for each specific migration.

The landscape of Microsoft 365 migration tools has evolved considerably. Microsoft now offers a much broader range of options: SPMT and Migration Manager for content onboarding; cross-tenant capabilities for Exchange, OneDrive, and SharePoint; and Migration Orchestrator for coordinating specific user workloads between tenants. This does not eliminate the need for specialized tools. Quest On Demand Migration continues to excel in multi-workload, tenant-to-tenant projects and in scenarios that combine Microsoft 365, identity, and coexistence.

ShareGate has evolved from its traditional strength in SharePoint and Teams into a platform that now also includes Exchange Online, as well as Entra ID migration capabilities currently in preview. AvePoint Fly offers very broad coverage and is particularly well-suited for enterprise-level migrations, SharePoint, Teams, and Power Platform, as well as scenarios where metadata and governance play a significant role. BitTitan MigrationWiz remains a key alternative for email and other workloads through its SaaS-based project model, and it has recently updated how it handles Teams private chats.

Cloudiway combines Microsoft 365 tenant-to-tenant migrations with cross-platform, Intune, and device-related scenarios. CodeTwo maintains a much more specialized focus and can be an excellent choice when Exchange is clearly the core of the migration. Meanwhile, PowerShell and Microsoft Graph remain essential tools for automating, preparing, and inspecting environments—though they should not be mistaken for a comprehensive migration platform. Therefore, before purchasing licenses, it is better to ask a more useful question than simply, “Which tool is the best?”: What combination of technology will allow for the migration of this specific environment while preserving what truly matters, all while maintaining a reasonable level of risk, effort, and cost?

The process begins with an inventory, continues with a technical comparison, and should be validated through a pilot project.

Official documentation and recommended resources

Microsoft – Overview.

• Microsoft – Microsoft 365 Migration Overview
• Microsoft – Migrate your content to Microsoft 365

SharePoint Migration Tool and Migration Manager.

• Microsoft – SharePoint Migration Tool
• Microsoft – Migration Manager
• Microsoft – What’s New in Migration Manager.

Microsoft Tenant-to-Tenant.

• Microsoft – Plan a Microsoft 365 Tenant-to-Tenant Migration
• Microsoft – Migration Orchestrator Overview
• Microsoft – Cross-Tenant Mailbox Migration
• Microsoft – Cross-Tenant OneDrive Migration
• Microsoft – Cross-Tenant SharePoint Migration

Quest On Demand Migration.

• Quest – On Demand Migration
• Quest – On Demand Migration User Guide
• Quest – Permissions Reference Guide.

ShareGate.

• ShareGate – Tenant-to-Tenant Migration
• ShareGate – Exchange Online Migration.
• ShareGate – Microsoft Teams Migration
• ShareGate – Entra ID Migration

AvePoint.

• AvePoint – Fly Migration
• AvePoint – Fly for Power Platform.

BitTitan.

• BitTitan – MigrationWiz
• BitTitan – Supported MigrationWiz Scenarios.
• BitTitan – Teams Private Chat Migration Guide

Cloudiway.

• Cloudiway – Migration Documentation
• Cloudiway – Cross-Tenant Microsoft Teams Migration.

CodeTwo.

• CodeTwo – Office 365 Migration
• CodeTwo – Microsoft 365 Tenant-to-Tenant Migration

PowerShell and Microsoft Graph.

• Microsoft – Microsoft Graph PowerShell Overview
• Microsoft – Connect-ExchangeOnline
• Microsoft – Teams PowerShell Overview