-
Written By Amit Chandel
-
Updated on November 3rd, 2026
User Query:
We are currently working on reorganizing our company and need to move SharePoint sites, documents, folders, and permissions between our SharePoint tenant to tenant migrations. What would be the best way of moving all of these in bulk with the preservation of folder structures & metadata to meet our exact migration requirements?
Michael Johnson (IT Manager), New York
Moving SharePoint sites, documents, and folders involves more than simply copying files. The company must factor in folder hierarchy as well as metadata, user access rights, and requirements of the destination tenant. The selection of a proper cross tenant SharePoint migration method depends on the amount of data being migrated. This guide explains how to plan a SharePoint migration. It explains Microsoft’s native method with the SysInfo Microsoft SharePoint Migration Tool and explores managed migration services (MSPs) for businesses that need assistance with specific migration requirements.
The process involves migrating SharePoint Online resources from one M365 tenant to another, including their contents and associated accounts. This differs from moving around data in a single tenant since the domain, Entra ID directory, and all the users from whom the content has been taken are new. Identity mapping therefore anchors the work.
OneDrive follows a parallel path. A cross tenant OneDrive migration moves individual accounts with Start-SPOCrossTenantUserContentMove, while sites use Start-SPOCrossTenantSiteContentMove. A Teams-connected site arrives without channels or chats; only its site content moves.
When there’s a major disruption in the business that requires data to cross the boundary from one Microsoft 365 setup to another, Managed Service Providers (MSPs) and IT teams typically need to step up and manage a tenant to tenant SharePoint migration.
Here are the most common situations where this happens:
Planning determines whether your cutover window stays quiet or turns into an administrative crisis. Based on official Microsoft guidelines, structure your migration around these critical steps:
You can carry out an unassisted migration of your business’s SharePoint either by using Microsoft’s built-in migration tools or SysInfo for SharePoint Tenant to Tenant Migration. Or you can opt to use our managed migration service (MSP).
Self-service SharePoint migration enables users to migrate SharePoint sites, document libraries & files with little or no IT involvement. There are some tools such as SharePoint Migration Tool (SPMT) and Professional Microsoft SharePoint Migration Tool, which assist users to perform migration tasks according to their needs and available features.
The SharePoint Migration Tool (SPMT) is Microsoft’s free tool for migrating supported on-premises SharePoint content and file shares to Microsoft 365. It does not support direct migration between two SharePoint Online tenants. The file shares are being migrated from existing SharePoint systems to Microsoft 365.
This tool migrates content from several on premises sources to SharePoint. These include SharePoint Server 2010, 2013, 2016, and 2019, SharePoint Foundation 2010 and 2013, and file shares. It can also migrate certain workflows from these supported SharePoint versions. Including SharePoint Server 2010 out-of-the-box workflows and SharePoint Designer 2010 and 2013 workflows.
These are the steps you have to follow to migrate the SharePoint data:
The SharePoint Tenant Migration Tool is a comprehensive solution for cross tenant SharePoint and cross tenant OneDrive migration. It is designed to migrate sites and site collections, data files, shared lists, fields/columns, file versions, document libraries, and metadata without loss of information. The tool is specially designed for all technical and non-technical users of Windows and macOS, and it is packed with many smart features. It features integrated site mapping, selection filters, real-time progress monitoring, and a deduplication engine for accurate migration projects.
Note: If you need more help, then you can visit the SharePoint Tenant Migration software official guide of SysInfo software.
MailConverterTools’ migration services may be an option for companies that do not have the time or skills to handle their cross tenant SharePoint migration on their own. With managed migration services, the migration journey starts with a discussion of the migration strategy, an evaluation of the source and target environments, and a determination of the work to be done.
The migration plan would be aligned with the organization’s SharePoint data and technological practices. This method may be appropriate for organizations in need of advice on planning, executing a migration, or solving specific issues. Prior to starting the project, ensure you check the supported workloads that can be moved, as well as the scope of migration and available customizations.
Need assistance with your SharePoint migration? Contact MailConverterTools to discuss your cross tenant shared data migration requirements and available services.
Cross-tenant SharePoint migration requires careful planning for permissions, identity mapping, file-size limits, and link preservation. Addressing these issues before migration can help prevent errors and reduce rework. For specific troubleshooting steps, see SharePoint Migration Issues: How to Fix and Avoid Them in 2026.
Big Files and the 250 GB Limit: Files larger than 250 GB cannot be moved as single items; they must be divided, compressed, or left out and sent through other means.
Broken Links After Moving: Check for documents with a lot of internal cross referencing before moving and inform their owners so they will change the source hyperlink after the new links become live.
“Access Denied” Messages: Make sure the migration account receives the Site Collection Administrator privileges on the destination site and double check it before running the task.
Missing Names and Paths: Do the path-and-character check on the source library prior to migrating and ask file owners to rename items that appear on the list.
Orphaned Users: Dealing with orphaned users can be accomplished before migration by running SharePoint Online PowerShell or Microsoft Graph against the User Information List.
Licenses and Compliance: Make sure the destination tenant has the legitimate Microsoft 365 licenses and verify whether Purview labels or barriers will come into place on the destination.
Use these best practices to help avoid errors during migration, protect your access to SharePoint content, and get ready for a successful migration. MSPs and IT teams need to do the following checks before performing the migration.
Cross Tenant SharePoint migration planning is crucial to prevent content transfer errors, permission issues, broken links, and identity mapping problems. Businesses should review their source environment, validate licenses, establish user mappings, and verify file names and paths before starting the migration process. Microsoft’s standard approach is appropriate if tenants meet established criteria for qualified migration. Third parties provide a graphical interface for controlling the migration and other migration options. Managed migration services are needed when MSPs and IT staff need help planning or performing the migration or have specific migration requirements.
Ans. Cross tenant SharePoint migration securely transfers sites, document libraries, and metadata across separate Microsoft 365 boundaries. Organizations can choose between self-service software like the mentioned SharePoint Migration Tool or specialized managed migration services.
Ans. Prerequisites depend heavily on the chosen method. For mentioned tool, you must authenticate both tenants using Global Admin credentials via OAuth 2.0, and the rest of the process is handled by the software.
Ans. You can migrate core assets, including site collections, modern and classic pages, document libraries, files, shared lists, customized fields/columns, metadata, and full file version histories. However, advanced customizations like active Power Automate flows, Power Apps connections, and sensitivity labels with user-defined permissions.
Ans. The native tool operates on a strict “one-and-done” architecture that does not support delta (incremental) passes. Additionally, the target landing site or OneDrive must not exist before execution, or the move will fail. It is also limited to moving underlying SharePoint document files, completely skipping Teams channel structures and chat histories.
Ans. Advanced software applications provide integrated site and user mapping dashboards. This process ensures historical file authorship, edit trails, and access rights transfer correctly to the target accounts with ease.
Ans. Yes. Internal user permissions and access settings are preserved provided a comprehensive identity map is uploaded before the migration begins. When using the tool’s cloud backend, the platform also deploys permanent redirect links at the source to ensure users clicking old URLs are automatically forwarded to the new target destination.
Ans. For the recommended cross-tenant migration tool, each SharePoint site or OneDrive account must remain within the supported limit of 5 TB or 1 million items. The item count includes files, folders, and file versions. The combined source content path and destination URL must also remain within the 400-character limit.
Ans. MSPs should pivot to a professional tool or managed migration services when a project requires multiple incremental delta passes rather than a single cutover or when target sites have already been pre-created. Third-party tools are also preferred if you need selection filters to exclude certain file extensions.
About The Author:
Meet Amit, an experienced SEO expert and content planner. He uses his creativity and strategy to create content that grabs attention and helps brands reach their goals. With solid skills in digital marketing and content planning, Amit helps businesses succeed online.
Related Post