mithileshtata
Member
Moving Microsoft O365 data between tenants using the Aryson Tenant to Tenant Migration Tool is a streamlined process compared to manual PowerShell migrations. Here is the condensed guide for performing the export and migration.
1. Prerequisites & Setup
Before launching the tool, ensure the following are ready:- Global Admin Credentials: You need admin access for both the Source and Destination tenants.
- Azure App Registration: You must register an application in the Azure Portal (Microsoft Entra ID) to generate a Client ID and Tenant ID for both sides.
- Impersonation Rights: Ensure the admin account has the necessary permissions to access all user mailboxes.
2. Migration Steps
Phase 1: Source Connection
- Launch the Aryson Microsoft 365 Tenant to Tenant Migration Tool.
- Select Office 365 as the source and click Login.
- Enter the Source Global Admin credentials and the Application ID/Tenant ID.
- The tool will fetch and display all mailboxes, groups, and sites. Select the items you wish to migrate.
Phase 2: Destination Connection
- Click Next and choose Office 365 as the destination.
- Enter the Destination Global Admin credentials and the corresponding App registration details.
- The tool will establish a secure connection to the new tenant.
Phase 3: Mapping & Filtering
- Mailbox Mapping: Map the source mailboxes to the destination mailboxes (e.g., user@source.com → user@destination.com). You can do this manually or via a CSV file.
- Select Categories: Choose specific data to export: Mail, Calendar, Contacts, OneDrive, or Teams.
- Apply Filters: Use the Date Range filter to migrate only recent data or use the Task Filter to exclude specific folders (like Trash or Spam).
Phase 4: Execution
- Click the Convert or Migrate button.
- Monitor the live progress bar for each mailbox.
- Once finished, download the Log Report to verify that all items were successfully exported to the new tenant.
3. Critical Post-Migration Tips
- DNS Records: Update your MX, SPF, and DKIM records to point to the new tenant to ensure mail flow continues.
- Outlook Profiles: Users will need to create new Outlook profiles as the backend server ID has changed.
- License Check: Ensure destination users have active O365 licenses assigned before the data arrives, or the migration may fail.