BitTitan Office 365 to Office 365 Migration – While Keeping the Same Domain Name

Office 365 to Office 365 migrations with the same domain name has a different order, such as a migration from Office 365 to Office 365 with a different domain name. The reason for this is that Microsoft only allows a tenant name at a time. For these reasons, additional steps are required.

Example environment:
– Active Directory(DHCP, DNS) Microsoft Azure
– Active Directory(DHCP, DNS) on-premises Hyper-V
– ADConnect on-premses Hyper-V
– Exchange Online

1: Add new users in new Active Directory
Create the users in the new Active Directory. Advice: For this change use a PowerShell script.

2: Add new domain suffix in on-premises Active Directory
Add the new alternative UPN suffix in Active Directory and Trusts.

3. Export the rights on the current environment
Use the Get-MailboxPermissions Powershell script.

4. Change UPN to the new UPN suffix for all users
Import-Module ActiveDirectory
$oldSuffix = “contoso.local”
$newSuffix = “contoso1.nl”
$ou = “DC=Contoso,DC=Users,DC=TEST”
$server = “AD01”
Get-ADUser -SearchBase $ou -filter * | ForEach-Object {
$newUpn = $_.UserPrincipalName.Replace($oldSuffix,$newSuffix)
$_ | Set-ADUser -server $server -UserPrincipalName $newUpn
}

5. Configuration AD Connect
Confugure AD Connect with the new tenant.

6. Domain from federated to Managed
If you use ADFS on the old tenant, end before changing smtp addresses on the old tenant. Configure to domain to Managed.

7. Change all SMTP addresses to @oldtenant.onmicosoft.com
In the old tenant change all SMTP addresses to @oldtenant.onmicosoft.com. This is important for removing the domain name in the old tenant.

Convert-MsolDomainToStandard -DomainName olddomain.nl -PasswordFile C:\Temp\PW.txt
To check: Get-MsolDomain

8. Change all SMTP addresses to @newtenant.onmicrosoft.com
In the new tenant change all SMTP addresses to @newtenant.onmicosoft.com. This is important to add the domain name in the new tenant. If you not changing the smpt address, you will have issues with the smpt addresses.

9. Domain from federated to Managed
If you use ADFS, configure the domain to federated.

Connect-MsolService –Credential $cred
Set-MsolADFSContext –Computer ADFS01.domain.NL
Convert-MsolDomainToFederated –DomainName domain.nl
Successfully updated ‘domain‘ domain
Get-MsolFederationProperty –DomainName domain_name.com

10. Deleted domain from old tenant
Before you deleted the domain from the old tenant, check to domain name is not using by mailboxes, shared mailboxes or groups. Deleted now the domain from Admin Center in Office 365 portal – Installation – Domain.

11. Change the TXT record
Change the TXT record on your DNS public Admin center to the new tenant name. Important is the TTL on 5 minutes.

12. Add domain to new tenant name
Add the same domain name in the new tenant Office 365 Admin portal.

13. Configure AD Connect
Configure AD Connect with new tenant name.

14. Migrate the users with BitTitan
Create a BitTitan account and the connectors to both Office 365 tenants on Manage BitTitan

You have several options to add users:

I’ll show with a quid add:
You need a source mailbox and destination mailbox.

You can also start a trial migration for testing or a pre-stage migration. An pre-stage migration is the same sync before completing a batch in Office 365 Exchange Admin portal.

Migration is completed for the test user from Tenant A to Tenant B.

More information about BitTitan:
What items are not migrated with MigrationWiz?
What items are migrated with MigrationWiz?
What are the descriptions of the different migration types?

Leave a Reply

Your email address will not be published. Required fields are marked *