SharePoint Online Tenant-to-Tenant Migration — Microsoft 365 Consolidation
IT Partner helps migrate SharePoint Online content from one Microsoft 365 tenant to another, including site collections, sites, lists, libraries, documents, permissions, design, and structure. This service is designed for organizations consolidating SharePoint Online infrastructure and documents, such as during mergers and acquisitions, and includes migration execution, verification, post-migration tasks, and a project closeout report.
What this engagement is
As organizations move to Microsoft 365 during mergers and acquisitions, they may need to consolidate SharePoint Online infrastructure and documents. This service helps migrate site collections, sites, lists, and libraries with permissions and design. The objective is to migrate documents, sites, and structure from one SharePoint tenant to another.
Success criteria
What you receive
How the work unfolds
Confirm the sites and libraries in scope, destination tenant structure, points of contact, schedule, and acceptance criteria.
Review the source SharePoint Online tenant for readiness and check compatibility with the destination tenant, including content volume and permissions.
Create the migration project, add the items to be migrated, set advanced project options, and start migrating content to the destination tenant.
Review migration results and validate representative sites, libraries, documents, permissions, and structure in the destination tenant.
Run the final migration pass to capture remaining and changed content before completing the move.
Decommission the source SharePoint Online libraries and/or accounts as agreed, verify files and structure, and prepare the closeout report.
Prerequisites
Who does what
IT Partner
- Check the source SharePoint Online tenant for compatibility with the new tenant and help fix any errors, if the destination tenant is not empty.
- Use special tools that provide a set of features and flexible options to help maintain data integrity, permission levels, version histories, and metadata.
- Use auditing and reporting tools to help plan, configure, and granularly migrate content.
- Create the Document Migration project and add the items that will be migrated to the project.
- Set the advanced project options and perform the migration.
- Upon completion of the project, prevent users from inadvertently using older SharePoint libraries by decommissioning the source SharePoint Online, libraries, and/or user accounts.
- Verify files and structure and perform post-migration tasks.
- Provide a project closeout report indicating the final project status, including evidence of meeting acceptance criteria, outstanding issues, if any, and the final budget.
Your team
- Provide a dedicated point of contact responsible for working with IT Partner and coordinate any outside vendor resources and schedules
- Configure all networking equipment, such as load balancers, routers, firewalls, and switches
- Provide access to physical and virtual servers and/or systems and services, as needed, and provide remote and/or physical access to facilities and systems required to complete the work
- Perform changes to internal and external DNS, as required
- Assist with identification of high-risk users (top executives and VIP users)
- Designate a specialist who will provide useful information about content design and structure; someone who understands all the business processes inside your company
What's not included
Limitations & technical notes
Frequently asked questions
What is included in IT Partner’s SharePoint Online tenant-to-tenant migration service?
IT Partner’s SharePoint Online tenant-to-tenant migration service includes migrating SharePoint Online site collections, sites, lists, libraries, documents, structure, permissions, and design from one Microsoft 365 tenant to another. The engagement also includes creating the migration project, configuring advanced migration options, performing the migration, verifying files and structure, completing post-migration tasks, and providing a project closeout report.
Who is this SharePoint Online tenant-to-tenant migration service designed for?
This service is designed for organizations that need to consolidate SharePoint Online infrastructure and documents between Microsoft 365 tenants, often during mergers, acquisitions, divestitures, or tenant consolidation projects. It focuses on moving SharePoint Online content and structure from a source tenant to a destination tenant in an agreed timeframe.
How much does the SharePoint Online tenant-to-tenant migration service cost?
The service is priced at $100 per site plus a $2,500 tenant fee, quoted in writing before work begins — you pay after you approve delivery. Confirm the site count and the final scope with IT Partner before kickoff; the final budget is documented in the project closeout report.
How long does a SharePoint Online tenant-to-tenant migration take?
The stated duration for this SharePoint Online tenant-to-tenant migration service is 1 week. The actual plan may vary depending on the customer’s needs, the number of sites, the source environment condition, and the agreed migration scope.
What SharePoint Online content can be migrated between tenants?
IT Partner can migrate SharePoint Online documents, sites, site collections, lists, libraries, structure, permissions, and design from one tenant to another. The service also uses migration tools intended to help maintain data integrity, permission levels, version histories, and metadata.
Does the service migrate SharePoint permissions?
Yes, migrating SharePoint Online permissions is part of the stated service scope. IT Partner uses specialized tools and advanced migration options to help maintain permission levels along with content, structure, version histories, and metadata.
Does the service preserve SharePoint metadata and version history?
The service uses tools that provide flexible options to help maintain metadata and version histories during the SharePoint Online tenant-to-tenant migration. Exact preservation behavior can depend on the source content, destination configuration, and migration tool settings, so any critical metadata or versioning requirements should be confirmed during planning.
What are the prerequisites for this SharePoint Online migration service?
The customer must have a Microsoft 365 tenant with SharePoint Online licenses, admin access to SharePoint Online, and a planned site structure and permissions model for the destination SharePoint Online environment. These prerequisites are important because the migration depends on valid licensing, administrative access, and a clear target structure.
What happens during the SharePoint Online tenant-to-tenant migration engagement?
The engagement typically includes a kickoff meeting, a pre-migration source system health check, the start of data migration, migration verification, final migration, and post-migration tasks. IT Partner also creates the document migration project, adds the items to be migrated, sets advanced project options, and verifies the migrated files and structure.
What is not included in this migration service?
Customer team training, users' folder migration, mail server migration, SharePoint consulting and development, and desktop software settings are not included in the standard scope; several of these can be added as separate services. Documentation beyond the project closeout report can be provided for an additional fee.
How does IT Partner verify that the migration was successful?
IT Partner verifies files and structure after the SharePoint Online migration and performs post-migration tasks. The project is considered successful when all agreed data has been moved from one tenant to another correctly within the agreed timeframe, and the closeout report includes evidence of meeting acceptance criteria and any outstanding issues.
What happens to the old SharePoint Online libraries after migration?
After the migration is completed, IT Partner can decommission the source SharePoint Online, libraries, and/or user accounts to help prevent users from inadvertently continuing to use older SharePoint libraries. This is part of the post-migration tasks included in the stated service scope.