Why This Matters
Tenant-to-tenant migrations are becoming a regular part of Microsoft 365 administration—whether driven by mergers, divestitures, or consolidation efforts.
This guide focuses specifically on the setup phase of migrations. It avoids cutover strategy and instead walks through how to quickly and reliably configure tools to move data between environments.
Tools Covered
- Movebot — optimized for file and content migrations
- BitTitan MigrationWiz — optimized for mailbox and structured workload migrations
Core Setup Pattern
Regardless of tool, migrations follow a consistent pattern:
- Connect source and destination environments
- Scan or discover data
- Map users and resources
- Execute migration
Environment Preparation
- Global admin access in both tenants
- Target users created and licensed
- Exchange mailboxes provisioned
- OneDrive initialized (user sign-in or pre-provisioning)
- SharePoint sites created where required
- Modern authentication enabled
Movebot Setup (OneDrive & SharePoint)
Create Migration Project
Begin by creating a new migration project in the Movebot portal. The process is entirely SaaS-driven with no infrastructure required.
Connect Source & Destination
- Add Microsoft 365 as the source
- Add Microsoft 365 as the destination
- Authenticate using admin credentials
Run Discovery Scan
Perform a scan of the source environment to understand folder structures, file counts, and data volume. This step helps identify potential issues before migration begins.
Configure Mapping
- Map OneDrive users to destination users
- Map SharePoint sites to target locations
- Define folder targeting and overwrite/merge behavior
Permissions & Metadata
- Enable permissions migration
- Preserve metadata where applicable
- Validate file naming and compatibility constraints
Run Migration
Start the migration job and monitor progress through the dashboard. Track throughput, failures, and completion rates.
BitTitan MigrationWiz Setup (Mail, OneDrive, SharePoint)
Create Project
- Select Mailbox Migration for Exchange
- Select Document Migration for OneDrive and SharePoint
Configure Endpoints
- Define source tenant
- Define destination tenant
- Use OAuth authentication
Import & Map Users
- Import via CSV or autodiscovery
- Map source users to destination users
Validation
- Confirm mailbox access
- Confirm licensing
- Verify permissions
Pre-Stage Migration
Run an initial migration pass for historical data. This reduces load during final cutover and improves performance.
Final Migration
- Calendars
- Contacts
- Documents
- Permissions
Tool Positioning
- Mailboxes: BitTitan
- OneDrive: Movebot or BitTitan
- SharePoint: Movebot
- File Shares: Movebot
Practical Tips from the Field
Start Small
Always test with a limited pilot group before scaling. Validate data structure and access.
Focus on Permissions
The most common migration issues occur with SharePoint and OneDrive permissions. Validate thoroughly.
Review Reports
Always check migration logs, error reports, and completion summaries before closing a project.
Use Parallelism
Both tools support concurrent migrations, which significantly improves speed at scale.
Final Thoughts
Migration tooling does not need to be complex. Both Movebot and MigrationWiz follow a predictable and repeatable workflow.
When combined effectively, they provide a reliable and scalable approach to Microsoft 365 tenant migrations.
Documentation References
- Movebot Documentation — https://docs.movebot.io/
- BitTitan Help Center — https://help.bittitan.com/hc/en-us