Configuring BitTitan For a on Premise to Hosted Exchange Migration

I have used Bittitan now on a couple of occasions and I have to say that it is my preferred method of doing large-scale Exchange migrations. if On-Premise to On-Premise  or On Premise to a Hosted Exchange Platform

If you’ve not seen BitTitan before – Check out one of their case studies below

 

 

this post is more of an Aide-Memoire for my self more than anything after trial and error as to what to do and what order to do them in

The full Guide for a Hosted Exchange – Hosted Exchange guide can be found by BT here

https://help.bittitan.com/hc/en-us/articles/115008107207-Hosted-Exchange-to-Hosted-Exchange-Migration-Guide

 

However, the bits I have taken below are a combination of my own learnings and the above guide

 

Prepare the Source Environment

  • We need to create a Domain Administrator on the customer server
  • This user will need to be given Full Access rights to all mailboxes on that server, we can do this with the following PowerShell command

 

Get-Mailbox -ResultSize Unlimited | Add-MailboxPermission -AccessRights FullAccess -User MigrationWiz

 

Prepare the Destination Environment – Hosted Exchange

  • Create a user in the Customer OU if it is a multi tenanted domain
  • Execute the following PowerShell to give the user full access to the Mailboxes in the new system but just contained within the customers OU

 

Get-Mailbox -OrganizationalUnit “COMPANY.co.uk/Hosted Clients/CUSTOMER” -ResultSize Unlimited | Add-MailboxPermission -AccessRights FullAccess -User [email protected]

 

For the above you will need to run powershell as an Administrator on both the source and destination server and we have delegated permissions to our user called “Migratin Wiz” 

 

MigrationWiz Steps

Now that we have the Source nd destination environment in a place where they are good to go we need to do the following

  • Create a new customer if applicable
  • Create a new project, adding source and destination Exchange Servers
  • Purchase Licenses if required
  • Add Source and Destination mailboxes

 

The Migration Itself

 

now that we have the Migration all set up we need to do the following

  • Verify credentials
  • Trial Migration
  • Pre-Stage Migration
  • Retry errors
  • Full Migration (Delta Sync)

An important point to note during the migration is what I learned was the mail is not just sync’d from Server A – B .. It is cached in a MS Azure data center so it necessary to cap the project as to how man simultaneous mailboxes they can do at once

 

Once complete it is best to delete the “Migration Wiz’ user


Leave a Reply

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