Organizations move SharePoint sites between Microsoft 365 tenants for many reasons. A company merger may require two separate Microsoft 365 environments to become one. A business restructuring project may require departments to move into a new tenant. A divestiture may require separating users, data, and collaboration spaces into another Microsoft 365 environment.
Whatever the reason, migrate SharePoint site to another tenant is not the same as copying files from one location to another. A SharePoint site contains much more than documents. It may include:
- Document libraries
- Lists
- Metadata
- Permissions
- Users and groups
- Version history
- Site settings
- Sharing configurations
- Workflows
- Apps
- Customizations
- Microsoft 365 Group connections
- Teams-related dependencies
A successful migration requires planning the source environment, preparing the target tenant, mapping identities, moving data, and validating the final result.
Microsoft provides a native Cross-tenant SharePoint migration capability for eligible Microsoft 365 environments. Organizations can also use third-party SharePoint migration tools when they require additional controls, reporting, filtering, or migration scenarios outside the native capability.
This guide explains how SharePoint tenant-to-tenant migration works, what preparation is required, how Microsoft’s approach works, what limitations exist, and when another migration method may be appropriate.
Quick Answer: How Do You Migrate a SharePoint Site to Another Tenant?
You can migrate a SharePoint site from one Microsoft 365 tenant to another using Microsoft’s native Cross-tenant SharePoint Migration capability if your tenants meet Microsoft’s requirements.
The general process includes:
- Preparing the source and target Microsoft 365 tenants
- Establishing a cross-tenant trust relationship
- Preparing user and group identity mapping
- Creating or preparing the target SharePoint site
- Running migration commands through SharePoint Online PowerShell
- Monitoring migration progress
- Validating content, permissions, and user access after completion
Organizations that need additional migration controls, advanced filtering, detailed reporting, or support for more complex migration scenarios may evaluate third-party SharePoint migration tools.
The correct approach depends on:
- Tenant configuration
- Data volume
- Migration requirements
- Compliance needs
- Required level of automation
- Supported Microsoft scenarios
What Is SharePoint Tenant-to-Tenant Migration?
Understanding Microsoft 365 Tenants
A Microsoft 365 tenant is a dedicated instance of Microsoft cloud services that belongs to an organization.
When a company creates Microsoft 365 services, Microsoft creates a tenant containing:
- Users
- Groups
- Domains
- SharePoint Online
- OneDrive
- Teams
- Exchange Online
- Security settings
- Compliance configurations
For example:
Company A:
oldcompany.onmicrosoft.com
Company B:
newcompany.onmicrosoft.com
These are separate Microsoft 365 tenants.
Even if both organizations use Microsoft 365, their SharePoint environments are isolated.
What Is SharePoint Online?
SharePoint Online is Microsoft’s cloud-based platform for:
- Document management
- Team collaboration
- Intranet sites
- Knowledge sharing
- Business applications
A SharePoint site may contain:
Document Libraries
Locations where users store files.
Locations where users store files.
Example:
Marketing Documents
HR Policies
Project Files
Contracts
Lists
Structured collections of information.
Examples:
- Employee directories
- Project trackers
- Issue lists
- Asset records
Metadata
Additional information attached to files or items.
Examples:
A document may have:
Department: Finance
Status: Approved
Document Type: ContractPermissions
Controls that define who can:
- View content
- Edit content
- Share documents
- Manage sites
What Does Tenant-to-Tenant Migration Mean?
A SharePoint tenant-to-tenant migration means moving SharePoint content from one Microsoft 365 tenant to another separate Microsoft 365 tenant.
Example:
Source Tenant
https://oldtenant.sharepoint.com/sites/Marketing
↓
Migration
↓
Target Tenant
https://newtenant.sharepoint.com/sites/MarketingThe goal is to move the SharePoint workload while preserving important information such as:
- Files
- Libraries
- Lists
- Metadata
- Permissions
- User relationships
However, not every SharePoint feature automatically transfers exactly as it existed in the source tenant. Some components require preparation or rebuilding.
Why Do Organizations Migrate SharePoint Sites to Another Tenant?
Organizations usually perform SharePoint tenant migration because of business changes rather than technical reasons.
1. Company Mergers and Acquisitions
When two companies combine, they often have separate Microsoft 365 environments.
Example:
Company A uses:
companyA.sharepoint.com
Company B uses:
companyB.sharepoint.com
After acquisition, leadership may decide to consolidate collaboration into one Microsoft 365 tenant.
A SharePoint migration helps move:
- Department documents
- Project files
- Internal knowledge bases
- Team sites
into the new environment.
2. Tenant Consolidation
Large organizations sometimes operate multiple Microsoft 365 tenants because of:
- Previous acquisitions
- Regional deployments
- Separate business units
- Historical IT decisions
Maintaining multiple tenants can increase:
- Administration effort
- Security management complexity
- Licensing management challenges
A consolidation project can bring SharePoint sites into a centralized tenant.
3. Business Separation or Divestiture
Sometimes organizations need the opposite approach.
A business unit may become an independent company and require its own Microsoft 365 tenant.
Migration may involve separating:
- Department sites
- Documents
- User access
- Collaboration spaces
4. Domain or Organizational Changes
Organizations may move tenants because of:
- Company rebranding
- New corporate identity
- Legal restructuring
- Regional separation
The migration allows business data to move into the correct Microsoft 365 environment.
5. Moving From Legacy Environments
Some organizations created Microsoft 365 tenants years ago with different structures.
Over time they may need a cleaner environment with:
- Better governance
- Updated security policies
- Improved administration
- Standardized SharePoint architecture
What Should You Check Before Migrating a SharePoint Site?
A successful SharePoint migration begins before moving any data.
The following checklist separates migration requirements from recommended planning checks.
SharePoint Tenant Migration Pre-Migration Checklist
| Check | Required or Recommended | Why It Matters |
| Source tenant administrator access | Required | Needed to prepare and start migration |
| Target tenant administrator access | Required | Needed for destination configuration |
| SharePoint Administrator role | Required | Required for tenant-level operations |
| Microsoft licensing | Required | Migration capability depends on licensing |
| Site ownership review | Recommended | Helps identify responsible users |
| Site size analysis | Recommended | Large sites need additional planning |
| File count analysis | Recommended | Helps estimate migration complexity |
| Permission review | Recommended | Prevents access issues |
| User mapping | Required | Connects source identities with target identities |
| Group mapping | Required | Ensures correct permissions |
| External sharing review | Recommended | Guest access may need attention |
| Microsoft Teams connection review | Recommended | Teams migration requires separate planning |
| Workflow review | Recommended | Some workflows need rebuilding |
| Power Automate flow review | Recommended | Connections may require updates |
| Apps review | Recommended | Custom apps may need recreation |
| Hub site review | Recommended | Navigation relationships may change |
| Retention policies | Recommended | Compliance settings may affect migration |
| Sensitivity labels | Recommended | Protected content requires review |
| Multi-Geo configuration | Recommended | Requires additional planning |
Source Tenant Preparation
Before migration begins, administrators should inventory the source SharePoint environment.
Important information to collect:
Site Inventory
Record:
- Site URL
- Site owner
- Site type
- Storage usage
- Number of files
- Number of libraries
- Number of lists
- Permission structure
Example:
| Site | Owner | Size | Purpose |
| Marketing | Marketing Manager | 350 GB | Campaign files |
| HR | HR Director | 120 GB | Employee documents |
| Finance | CFO Office | 500 GB | Financial records |
Review SharePoint Site Types
SharePoint environments may contain:
- Communication sites
- Team sites
- Microsoft 365 Group-connected sites
- Classic SharePoint sites
Each type may have different migration considerations.
Check Microsoft 365 Group Connections
Many modern SharePoint team sites are connected to Microsoft 365 Groups.
A group-connected site may also include:
- Microsoft Teams
- Planner
- Group mailbox
- Calendar
Moving the SharePoint site does not automatically mean every connected Microsoft 365 service moves with it.
Teams migration requires separate planning.
Review Permissions Before Migration
Permissions are one of the most important parts of SharePoint migration.
A site may contain:
Site-Level Permissions
Example:
Marketing Team
Members: Edit
Executives
Owners: Full Control
Library Permissions
Example:
Finance Library
- Finance Team → Edit
- Employees → Read
Item-Level Permissions
Individual files or folders may have unique permissions.
Example:
Salary.xlsx
Only HR Managers can access
Before migration, administrators should identify:
- Broken permission inheritance
- Unique permissions
- Guest users
- External sharing
- Old inactive accounts
Check File and Folder Structure
Long paths are a common migration issue.
SharePoint has limits related to:
- URL length
- Folder depth
- File naming rules
Before migration, review:
- Deep folder structures
- Invalid characters
- Very long file names
- Unsupported file types
Example:
Problem:
/Projects/2026/Regional/Department/Customer/Contracts/Final Version/Approved Documents/Very-long-file-name.docx
This structure may require cleanup before migration.
Review Workflows and Applications
SharePoint sites often contain business processes.
Examples:
- Approval workflows
- Power Automate flows
- Custom SharePoint Framework solutions
- Third-party apps
- Forms customization
These should be documented before migration.
Do not assume every workflow or application will continue working automatically after tenant migration.
Microsoft Cross-Tenant SharePoint Migration
Microsoft’s native solution is called Cross-tenant SharePoint migration. It is designed specifically for moving SharePoint Online sites between Microsoft 365 tenants.
This is different from the older SharePoint Migration Tool.
How Microsoft’s Native Migration Works
The process generally includes:
- Establishing communication between tenants
- Creating trust relationships
- Preparing identity mapping
- Preparing migration settings
- Initiating site moves
- Monitoring migration status
- Validating migrated content
Step 1: Connect to Source and Target Tenants
Administrators use SharePoint Online PowerShell to connect to the required tenants.
Example connection:
Connect-SPOService -Url https://sourceadmin-admin.sharepoint.com
For the target tenant:
Connect-SPOService -Url https://targetadmin-admin.sharepoint.com
These commands connect PowerShell to SharePoint Online administration endpoints.
The exact tenant URLs must be replaced with your organization’s admin URLs.
Step 2: Establish Cross-Tenant Trust
Microsoft requires a trust relationship between the source and target tenants.
The purpose of this trust is to allow Microsoft services to recognize that:
- Tenant A allows migration
- Tenant B is the destination
- Identity mapping can occur
Administrators configure this relationship before migration starts.
Step 3: Prepare Identity Mapping
Users in the source tenant and users in the target tenant have different identities.
Example:
Source:
[email protected]
Target:
Microsoft needs a way to understand:
“This old identity should become this new identity.”
This process is called:
Identity mapping
Without proper mapping:
- Permissions may not resolve correctly
- Users may lose access
- Ownership information may become incorrect
Step 4: Prepare Target SharePoint Site
The target environment must be ready before migration.
Administrators should verify:
- Correct site URL
- Correct permissions
- Required licenses
- Required administrators
- Available storage
The target site should not conflict with existing content.
Step 5: Start Migration
After preparation:
- Migration jobs are created
- Source sites are selected
- Target locations are defined
- Migration is started
Microsoft manages the transfer process through the SharePoint migration service.
Step 6: Monitor Migration Status
Administrators should monitor:
- Migration progress
- Errors
- Warnings
- Failed items
- Completed sites
Migration logs should be reviewed before users start working in the new tenant.
Microsoft SharePoint Cross-Tenant Migration Requirements
Before starting a SharePoint tenant-to-tenant migration, administrators should verify that both Microsoft 365 environments meet the required conditions.
The exact requirements can change as Microsoft updates the service, so administrators should always confirm current requirements in Microsoft documentation before beginning production migration.
SharePoint Tenant Migration Requirements Checklist
| Requirement | Why It Matters |
| Source tenant access | Administrators need permission to prepare and initiate migration from the original environment |
| Target tenant access | Required for configuring the destination environment |
| SharePoint Administrator role | Needed for SharePoint Online administrative operations |
| Microsoft 365 licensing | Required licensing depends on Microsoft’s current migration program requirements |
| Cross-tenant trust relationship | Allows Microsoft migration services to recognize the source and destination relationship |
| User identity preparation | Ensures migrated permissions connect to the correct users |
| Group preparation | Helps preserve access control relationships |
| Target site readiness | Prevents migration failures caused by incorrect destination configuration |
| Available storage | Destination tenant must have enough capacity |
| Site compatibility review | Unsupported configurations may require changes before migration |
Supported SharePoint Site Types
Microsoft’s cross-tenant SharePoint migration supports modern SharePoint Online scenarios, but administrators must review each site before migration.
Common SharePoint site types include:
Communication Sites
Communication sites are typically used for:
- Company intranets
- News portals
- Department information pages
- Internal announcements
These sites may contain:
- Pages
- Libraries
- Lists
- Navigation elements
Microsoft 365 Group-Connected Team Sites
Modern team sites are often connected to Microsoft 365 Groups.
They may include:
- SharePoint site
- Microsoft Teams connection
- Planner plans
- Group mailbox
Important:
Migrating a SharePoint site does not automatically mean every Microsoft 365 Group service moves with it.
Teams and other Microsoft 365 workloads require separate migration planning.
Classic SharePoint Sites
Older SharePoint environments may still contain classic sites.
Before migration, administrators should review:
- Custom solutions
- Classic workflows
- Custom master pages
- Legacy components
Some older customizations may require redesign.
What Happens to SharePoint Data During Cross-Tenant Migration?
A SharePoint site contains many types of information. Migration behavior can differ depending on the type of content.
The following explains common data categories.
Documents and Files
Documents stored in SharePoint libraries are one of the primary migration targets.
Examples:
- Word documents
- Excel files
- PowerPoint presentations
- PDFs
- Images
- Project files
Migration planning should include:
- Number of files
- File size
- Folder structure
- File versions
- Metadata
Large document libraries should be tested through pilot migrations before production migration.
Document Libraries
Document libraries usually contain:
- Files
- Folders
- Columns
- Views
- Metadata
Administrators should verify after migration:
- Library availability
- Views
- Columns
- Permissions
- User access
Lists and List Items
SharePoint lists may store business information such as:
- Employee records
- Issue tracking
- Project tasks
- Asset information
Validation should confirm:
- List structure
- Columns
- Items
- Permissions
- Formatting
Metadata Migration
Metadata helps organizations organize and search content.
Examples:
A document may have:
| Metadata Field | Value |
| Department | Legal |
| Status | Approved |
| Owner | John Smith |
| Document Type | Agreement |
Metadata preservation is important because losing it can affect:
- Search
- Filtering
- Compliance
- Document management
Version History
Many organizations rely on version history for:
- Auditing
- Compliance
- Reviewing previous changes
Administrators should verify version history after migration according to the supported migration behavior for their scenario.
Site Structure
A SharePoint site may contain:
- Pages
- Libraries
- Lists
- Navigation
- Permissions
- Settings
However, not every connected Microsoft 365 component is automatically transferred.
Example:
A Teams-connected SharePoint site may migrate SharePoint content, but Teams channels, conversations, meetings, and apps require separate planning.
What Happens to SharePoint Permissions During Tenant Migration?
Permissions are one of the most sensitive parts of SharePoint tenant migration.
A migration that successfully moves files but breaks access control is not considered complete.
Understanding Identity Mapping
Each Microsoft 365 tenant has separate identities.
Example:
Source tenant:
[email protected]Target tenant:
[email protected]Although the person is the same, Microsoft sees these as different identities.
Identity mapping connects:
Old identity
↓
New identity
This allows permissions to continue working after migration.
Types of Permissions That Need Review
Site Permissions
Example:
Marketing Site
Owners:
Marketing Managers
Members:
Marketing Employees
Visitors:
All Employees
Library Permissions
Example:
Finance Documents
Finance Team:
Edit
Employees:
Read
File-Level Permissions
Some files may have unique permissions.
Example:
Salary Information.xlsx
Access:
HR Managers Only
These require careful validation.
Permission Migration Example
Before migration:
Sales Site
John:
Edit
Sarah:
Read
Sales Group:
Full Control
After migration:
New Tenant
John:
Mapped identity → Edit
Sarah:
Mapped identity → Read
Sales Group:
Mapped group → Full Control
If users or groups are not mapped correctly, they may lose access.
What Happens to SharePoint Sharing Links After Migration?
Sharing links are a common concern during tenant migration.
Organizations often have:
- Internal sharing links
- Guest sharing links
- File links
- Folder links
Migration behavior depends on Microsoft’s supported migration scenario and current documentation.
Administrators should not assume every old URL will continue working exactly the same way.
Internal Links
Internal users may need updated links if:
- The tenant domain changes
- Site URLs change
- Content locations change
External Sharing
Guest users require special attention.
Check:
- External user accounts
- Sharing permissions
- Guest invitations
- Access policies
Old Tenant URLs
Example:
Old:
https://oldtenant.sharepoint.com/sites/project
New:
https://newtenant.sharepoint.com/sites/project
Applications, bookmarks, documentation, and integrations may need updating.
SharePoint Migration Limitations You Should Know
A successful migration requires understanding what the native Microsoft solution does not automatically solve.
1. Existing Target Site Conflicts
A common migration problem occurs when the destination site already exists.
Example:
Source:
Marketing Site
Target:
Marketing Site
already contains different content.
Migration planning should avoid conflicts.
Tenant-to-tenant migration is not the same as merging two SharePoint sites together.
2. Identity Mapping Limitations
Permissions depend on correct identity mapping.
Problems occur when:
- Users do not exist in target tenant
- Groups are missing
- Accounts changed
- Guest identities are unmanaged
3. Teams Content Is Not Automatically the Same as SharePoint Migration
Many administrators assume:
“Move SharePoint site = Move Teams.”
This is incorrect.
A Teams-connected SharePoint site contains files behind Teams channels, but Teams includes additional workloads:
- Conversations
- Meetings
- Apps
- Tabs
- Team settings
These require separate planning.
4. Workflows May Require Attention
SharePoint environments often include:
- SharePoint Designer workflows
- Power Automate flows
- Approval processes
Connections and authentication may need updating after migration.
5. Apps and Custom Solutions
Custom solutions may include:
- SharePoint Framework components
- Third-party apps
- Custom forms
- Integrations
These should be documented before migration.
6. Multi-Geo Environments
Organizations using Microsoft 365 Multi-Geo should carefully review:
- Data locations
- Tenant configuration
- Supported migration scenarios
Microsoft documentation should be checked before planning Multi-Geo migrations.
7. Compliance and Security Features
Review:
- Retention policies
- Sensitivity labels
- Information protection
- Encryption settings
- Compliance requirements
Some security configurations may require additional configuration after migration.
Can You Migrate a SharePoint Site Without Downtime?
The short answer:
A SharePoint tenant migration can often be planned to reduce disruption, but organizations should not assume zero downtime.
Migration Preparation Phase
Before migration:
- Inventory content
- Prepare users
- Test migration
- Communicate changes
Migration Window
During final migration:
Organizations may need to control user activity to prevent:
- New documents being created
- Changes being missed
- Conflicting updates
Cutover
The final stage usually includes:
- Completing migration
- Validating content
- Updating users
- Confirming access
The goal is minimal business interruption.
How Long Does SharePoint Tenant-to-Tenant Migration Take?
There is no universal migration speed because every SharePoint environment is different.
Migration duration depends on:
| Factor | Impact |
| Total data size | More data requires more migration time |
| Number of files | Millions of items increase complexity |
| File versions | Version history increases workload |
| Number of permissions | Complex permissions require additional processing |
| Lists and items | Large lists need validation |
| Customizations | Additional review may be needed |
| Number of sites | Multiple sites increase planning effort |
| Migration method | Different tools have different workflows |
A small departmental site may migrate quickly, while a large enterprise environment may require multiple migration waves.
Common SharePoint Tenant Migration Problems
Problem: Target Site Already Exists
Cause:
The destination site conflicts with the migration target.
Solution:
Review target environment design before migration and avoid conflicting destinations.
Problem: Users Cannot Access Migrated Files
Cause:
Identity mapping or permissions mapping was incomplete.
Solution:
Review:
- User mappings
- Groups
- Site permissions
- Library permissions
Problem: Migration Reports Failed Items
Cause:
Possible reasons include:
- Unsupported content
- Permission issues
- Invalid file names
- Long paths
Solution:
Review migration logs and correct failed items.
Problem: Workflows Stop Working
Cause:
Workflow connections may reference old tenant resources.
Solution:
Review and recreate or update workflows.
Problem: External Users Lose Access
Cause:
Guest accounts may not exist or permissions may not transfer as expected.
Solution:
Review external sharing configuration and guest identity management.
Problem: Links Do Not Work
Cause:
URLs may reference the old tenant.
Solution:
Update:
- Internal documentation
- Applications
- Bookmarks
- User guides
How to Validate a SharePoint Migration
Migration is not complete when the transfer finishes.
Validation confirms that users can continue working normally.
Post-Migration Validation Checklist
| Area | Validation Task |
| Files | Confirm documents open correctly |
| Libraries | Check library structure |
| Folders | Verify folder hierarchy |
| Lists | Confirm list items exist |
| Metadata | Check columns and values |
| Permissions | Test user access |
| Owners | Confirm site owners |
| Members | Confirm group access |
| Visitors | Verify read permissions |
| Search | Test SharePoint search |
| Navigation | Check menus and links |
| Sharing | Test sharing functions |
| Workflows | Verify business processes |
| Apps | Confirm custom solutions |
| Upload | Test new uploads |
| Download | Test downloads |
| Editing | Test document editing |
Native Microsoft Cross-Tenant Migration vs Third-Party SharePoint Migration Tools
Organizations planning a SharePoint tenant-to-tenant migration often evaluate two approaches:
- Microsoft’s native Cross-tenant SharePoint Migration capability
- Third-party SharePoint migration tools
The right choice depends on the migration requirements, environment complexity, compliance needs, and the level of control administrators need.
There is no single migration method that fits every organization.
Comparison: Microsoft Native Migration vs Third-Party Tools
| Capability | Microsoft Native Cross-Tenant SharePoint Migration | Third-Party SharePoint Migration Tools |
| Microsoft-supported approach | Yes | Depends on vendor |
| SharePoint Online tenant-to-tenant migration | Supported for eligible scenarios | Often supported by vendors |
| SharePoint site migration | Supported | Usually supported |
| Document migration | Supported | Usually supported |
| Metadata migration | Supported according to supported scenarios | Often supported |
| Permission migration | Supported with identity preparation | Usually supported with mapping features |
| Identity mapping | Required | Often provides additional mapping controls |
| Incremental migration options | Depends on Microsoft capability | Depends on vendor |
| Migration filtering | Limited compared with some third-party tools | Often available |
| Detailed reporting | Microsoft migration reports | Vendor-specific reporting options |
| Scheduling | Microsoft-supported scheduling options | Depends on product |
| Migration dashboard | Microsoft administration tools | Often included |
| Multiple migration scenarios | Focused on supported tenant-to-tenant scenarios | May support broader scenarios |
| SharePoint Server migrations | Not the purpose of cross-tenant migration | Some tools support hybrid scenarios |
| Granular migration control | Limited | Often more configurable |
When Should You Consider a Third-Party SharePoint Migration Tool?
A third-party SharePoint migration tool may be considered when organizations need additional migration capabilities beyond the native Microsoft approach.
Common scenarios include:
1. Complex Migration Projects
Large organizations may have:
- Hundreds of SharePoint sites
- Multiple departments
- Complex permission structures
- Multiple migration phases
A migration platform with centralized management may help administrators organize the project.
2. Advanced Filtering Requirements
Some projects require selective migration.
Examples:
Move:
- Only documents from specific departments
- Only recent files
- Only selected libraries
Exclude:
- Temporary files
- Old archives
- Unnecessary content
3. Detailed Reporting Requirements
Organizations may require reports showing:
- Migrated items
- Failed items
- Skipped items
- Migration status
- Permission results
4. Mixed Microsoft Environments
Some organizations may need to move content between:
- SharePoint Online environments
- Different SharePoint versions
- Hybrid environments
The appropriate tool depends on the specific scenario.
5. Reduced PowerShell Dependency
Some administrators prefer graphical interfaces instead of managing migration tasks entirely through PowerShell.
Shoviv SharePoint Migration Tool as an Alternative
Shoviv SharePoint Migration Tool is one example of a third-party migration solution that organizations may evaluate for SharePoint migration projects.
Vendor documentation describes capabilities such as SharePoint-to-SharePoint migration scenarios, migration of SharePoint content, permission handling, filtering options, and migration reporting.
Organizations should verify the latest product documentation before selecting any migration software because vendor features can change.
Vendor Resources:-
Possible Use Cases for Shoviv SharePoint Migration Tool
Depending on the supported version and configuration, organizations may use migration software like Shoviv for scenarios involving:
- SharePoint site migration
- Document library migration
- File and folder migration
- Metadata preservation
- Permission mapping
- Migration monitoring
- Migration reporting
How to Migrate SharePoint Site from One Tenant to Another Using Shoviv
The exact interface can change between product versions, so administrators should confirm current steps with Shoviv documentation.
A typical migration workflow follows these stages.
Step 1: Install and Open Shoviv SharePoint Migration Tool
Install the application on a supported Windows machine.
Before starting:
Check:
- System requirements
- Required permissions
- Network access
- Microsoft 365 authentication requirements
Step 2: Add Source SharePoint Tenant
The first environment is the source tenant.
Administrators provide authentication details to connect the original SharePoint environment.
Source information may include:
- Tenant URL
- Administrator credentials
- Authentication method
Example:
https://oldtenant.sharepoint.com
Step 3: Add Target SharePoint Tenant
Next, configure the destination tenant.
Example:
https://newtenant.sharepoint.com
The migration tool uses this connection as the destination location.
Step 4: Select Source SharePoint Site
Choose the SharePoint content that needs to move.
Possible selections may include:
- Sites
- Subsites where supported
- Libraries
- Lists
- Folders
- Files
Step 5: Select Target Location
Choose where the migrated content should be placed.
Before migration, verify:
- Target site exists
- Storage is available
- Permissions are prepared
- Naming conflicts are resolved
Step 6: Configure Mapping Options
Migration projects often require mapping between source and destination identities.
Review:
- Users
- Groups
- Permissions
- Owners
Example:
oldcompany.com user
↓
newcompany.com user
Step 7: Configure Migration Settings
Depending on the supported features, administrators may configure:
- Content selection
- Filters
- Migration options
- Reporting options
Step 8: Start Migration
After configuration:
- Review settings
- Start migration
- Monitor progress
Step 9: Review Migration Reports
After completion, check:
- Successfully migrated items
- Failed items
- Warnings
- Permission issues
Step 10: Validate Migrated SharePoint Content
Perform the same validation process used for any SharePoint migration:
Check:
- Files
- Libraries
- Metadata
- Permissions
- User access
- Business workflows
Why Organizations May Evaluate Shoviv for SharePoint Migration
Organizations may consider third-party tools when they need additional migration management features.
Potential advantages may include:
Migration Management
A dedicated migration interface can help administrators manage migration jobs.
Data Organization
Migration projects often need control over:
- Sites
- Libraries
- Folders
- Files
Permission Planning
Permission mapping capabilities can help during tenant transition projects.
Reporting
Migration reports help administrators review:
- Completed tasks
- Errors
- Warnings
Important:
A third-party tool should always be evaluated against:
- Migration requirements
- Security policies
- Compliance needs
- Vendor documentation
- Testing results
SharePoint Tenant-to-Tenant Migration Best Practices
Following best practices reduces migration risks.
1. Create a Complete Source Inventory
Document:
- Sites
- Owners
- Storage
- Permissions
- Applications
- Workflows
2. Identify Business-Critical Sites
Not every SharePoint site has the same priority.
Classify sites:
High priority:
- Finance
- HR
- Legal
- Operations
Medium priority:
- Department collaboration sites
Low priority:
- Archived content
3. Review Permissions Before Migration
Document:
- Owners
- Members
- Visitors
- Unique permissions
- External users
4. Prepare User Mapping
Create a clear identity mapping plan.
Example:
| Source User | Target User |
| [email protected] | [email protected] |
5. Review Microsoft 365 Groups
Identify:
- Group-connected sites
- Teams relationships
- Ownership
6. Check External Sharing
Review:
- Guest users
- Shared documents
- External access policies
7. Review Workflows
Document:
- Power Automate flows
- Approvals
- Automated processes
8. Check Custom Applications
Review:
- SharePoint Framework solutions
- Third-party apps
- Custom forms
9. Clean Up Unnecessary Data
Migration is a good opportunity to remove:
- Duplicate files
- Old archives
- Unused sites
10. Check Long File Paths
Review:
- Deep folders
- Long file names
- Unsupported characters
11. Perform a Pilot Migration
Before production:
Move a small sample.
Test:
- Files
- Permissions
- User access
- Workflows
12. Communicate With Users
Inform users about:
- Migration schedule
- New URLs
- Access changes
- Expected downtime
13. Create a Rollback Plan
Document:
- Recovery options
- Previous URLs
- Migration decisions
- Support contacts
14. Validate After Migration
Check:
- Content
- Permissions
- Search
- Navigation
15. Maintain Migration Documentation
Keep records of:
- Migration dates
- Source sites
- Target sites
- Issues
- Resolutions
SharePoint Migration Checklist
Before Migration
☐ Inventory all SharePoint sites
☐ Identify site owners
☐ Review permissions
☐ Review external users
☐ Check Microsoft 365 Groups
☐ Review Teams-connected sites
☐ Check workflows
☐ Check Power Automate flows
☐ Review custom applications
☐ Check storage requirements
☐ Review file paths
☐ Prepare identity mapping
☐ Test pilot migration
During Migration
☐ Confirm source tenant readiness
☐ Confirm target tenant readiness
☐ Verify trust configuration
☐ Start migration batches
☐ Monitor migration status
☐ Review errors
☐ Document migration progress
☐ Communicate status updates
After Migration
☐ Verify files
☐ Verify libraries
☐ Verify lists
☐ Check metadata
☐ Test permissions
☐ Confirm owners
☐ Test user access
☐ Verify search
☐ Check navigation
☐ Test sharing
☐ Review workflows
☐ Update documentation
☐ Inform users
Frequently Asked Questions:-
1. Can I migrate a SharePoint site from one tenant to another?
Yes. Microsoft provides a native Cross-tenant SharePoint Migration capability for supported Microsoft 365 scenarios. Third-party migration tools may also support additional migration scenarios.
2. Can I migrate SharePoint Online between two Microsoft 365 tenants?
Yes, SharePoint Online tenant-to-tenant migration is possible using Microsoft’s supported migration capability when requirements are met.
3. Can SharePoint Migration Tool (SPMT) migrate SharePoint Online tenant-to-tenant?
No. Microsoft SharePoint Migration Tool is not designed for direct SharePoint Online tenant-to-tenant migration.
4. Does Microsoft provide native SharePoint tenant migration?
Yes. Microsoft provides Cross-tenant SharePoint Migration for eligible tenants.
5. Can I merge two SharePoint sites during migration?
Generally, tenant migration moves content between environments. It is not the same as merging two existing SharePoint sites.
6. What happens to SharePoint permissions during migration?
Permissions require identity mapping between source and target users and groups.
7. Are SharePoint workflows migrated automatically?
Workflow behavior depends on the workflow technology and migration scenario. Some workflows may require recreation or updating.
8. Are Teams migrated with SharePoint sites?
A Teams-connected SharePoint site contains Teams file storage, but Teams conversations, settings, and apps require separate migration planning.
9. How long does SharePoint tenant migration take?
Duration depends on:
- Data size
- Number of files
- Permissions
- Versions
- Site complexity
- Migration approach
10. Can I migrate SharePoint metadata?
Metadata migration depends on the supported migration method and configuration. Metadata should always be validated after migration.
11. What happens to external users?
External users require review because guest identities and sharing permissions may need adjustment.
12. Can I migrate multiple SharePoint sites?
Yes, organizations commonly migrate multiple sites using planned migration batches.
13. Should I use Microsoft migration or a third-party tool?
The correct choice depends on:
- Migration requirements
- Supported scenarios
- Required controls
- Reporting needs
- Environment complexity
14. What should I check after migration?
Check:
- Files
- Permissions
- Metadata
- Search
- Links
- User access
- Business processes
15. What happens if migration fails?
Review migration logs, identify failed items, correct the issue, and rerun supported migration operations where applicable.
Sources and References
Microsoft Documentation
- Microsoft Learn — Cross-tenant SharePoint migration overview
https://learn.microsoft.com/en-us/microsoft-365/migration/cross-tenant-sharepoint-migration - Microsoft Learn — Cross-tenant SharePoint migration steps
https://learn.microsoft.com/en-us/microsoft-365/migration/cross-tenant-sharepoint-migration-step1 - Microsoft Learn — SharePoint Migration Tool FAQ
https://learn.microsoft.com/en-us/sharepointmigration/spmt-faqs - Microsoft Learn — How SharePoint Migration Tool works
https://learn.microsoft.com/en-us/sharepointmigration/how-the-sharepoint-migration-tool-works
