Migrating Microsoft 365 services (Email, Teams, SharePoint) from a GoDaddy-tenant to a new Systron CSP tenant Print

Migrating Microsoft 365 services (Email, Teams, SharePoint) from a GoDaddy-tenant to a new SYSTRON Micronix CSP tenant involves a Tenant-to-Tenant (T2T) migration. Because GoDaddy acts as a reseller with "federated" control, this process requires breaking that federation, moving the data, and updating DNS records.There is no direct "push" button to move GoDaddy M365 to a regular tenant; it is a full tenant-to-tenant migration.

The most effective method for a comprehensive migration (Mail, Teams, SharePoint) is to use a third-party tool like BitTitan MigrationWiz.

Phase 1: Planning and Pre-Migration

1. Engage SYSTRON Micronix: Inform your new CSP provider to prepare the new, empty M365 tenant.
2. Purchase Licenses: Purchase the required M365 licenses in the new SYSTRON tenant.
3. Inventory Data: List all users, shared mailboxes, SharePoint sites, and Teams data in the GoDaddy tenant.
4. Create a New Domain: To facilitate the migration, it is best practice to have a temporary domain or use the <available-name-related-to-domain>.onmicrosoft.com domain for mapping.

Phase 2: Preparing the GoDaddy Source Tenant

1. Contact GoDaddy Support: Contact a "GoDaddy Guide" to submit a "Move my Microsoft 365 email away from GoDaddy" ticket.
2. Get Temporary Credentials: GoDaddy will provide a temporary password for the admin account, allowing you to sign into the Microsoft tenant directly.
3. Prepare Migration Tool: Set up BitTitan MigrationWiz (or a similar tool) to connect to the source (GoDaddy) and destination (SYSTRON) tenants.
4. Remove GoDaddy Federation (If Necessary): If GoDaddy does not defederate automatically, use PowerShell to convert your domain from "Federated" to "Managed".

Phase 3: Data Migration (Mail, Teams, SharePoint)

1. Mailbox Migration: Use the tool to migrate mailboxes, contacts, and calendar items.
2. SharePoint & OneDrive Migration: Use the migration tool to move documents, permissions, and structure to the new tenant.
3. Teams Migration: Use the tool to migrate Teams chat history, channel messages, and file structures.
4. Delta Sync: Run final delta passes to sync new data created during the migration process.

Phase 4: Cutover and Post-Migration

1. Update DNS Records: Update MX, SPF, and TXT records in DNS to point to the new SYSTRON/Microsoft tenant.
2. Remove Domain from GoDaddy: Remove your custom domain from the GoDaddy M365 organization so it can be added to the new tenant.
3. Finalize User Setup: Re-assign licenses and set up user profiles in the new tenant.
4. Test: Verify mail flow, SharePoint access, and Teams functionality.
5. Cancel Old Services: Cancel the M365 subscription in GoDaddy to avoid continued billing.

Key Considerations

• Do not delete mailboxes in GoDaddy before the migration is complete.
• Do not purchase new licenses in the new tenant until you are ready, or it will create a separate, wrong tenant.
• GoDaddy will no longer support your M365 services once the move is complete.
• Active Plans: Your GoDaddy plans must be active and not expire within 5 business days of the request.
• MFA Access: Ensure you have access to Multi-Factor Authentication (MFA) methods for all admin accounts.
• DNS Management: You will need to update MX, SPF, and CNAME records during the final cutover.
• No Direct Migration: There is no direct "push" button to move GoDaddy M365 to a regular tenant; it is a full tenant-to-tenant migration.
• Password Changes: Users will lose their single sign-on (SSO) with GoDaddy and will need new passwords to sign in at portal.office.com.
• Email Add-ons: Third-party add-ons like Proofpoint (Advanced Email Security) or Barracuda (Archiving) are deleted during this move.
• Timing: The process can take several hours to days to complete, primarily dependent on data volume, DNS propagation and coordination with GoDaddy support.