Exchange 2010 to 2016 cutover migration

Liquidfox

Liquidfox

Liquidfox

Soldato
Joined
26 Sep 2007
Posts
4,141
Location
Newcastle
Now we all know how easy it is to migrate Exchange mailboxes to Exchange Online. You create the migration endpoint, give a few permissions, click a few buttons and voila. You're syncing. Can this be done to another Exchange service? Ie our multi-tenanted Exchange platform we've got in our datacentre? It would appear that this lovely feature is a Exchange Online only thing, I expect in an effort to push people to their Exchange Online service.

As far as I can see the only option to do a move like this would be a cross-forest migration which isn't possible in this scenario as the source network is running SBS. Anyone else have any suggestions apart from doing it the old fashioned way?
 
Last edited:
Normally, yes, that's exactly what we'd do. What we're doing here though is only migrating Exchange. Their SBS will stay live for the time being whilst we bring a new 2016 DC online and migrate AD onto that. The destination Exchange servers are external to the source, on a completely separate domain that is not going to be joined. Think of the destination as being 365 (ie it's multi-tenanted), but it's not hosted by Microsoft. It's hosted by us. It seems that in all their wisdom MS have left out the brilliantly useful migration features and kept them for only their Online platform instead.

It looks like I'm going to have to do pretty much what I did for a 2007 migration. Spin up a VM on our side, VPN to the source network, install Exchange management tools and export the mailboxes onto a share local to our destination servers and then run an import. There's leased lines at each end so it'll be easier to just export over a VPN than it would be to do a seed copy and then sync the changes.
 
You must log in or register to reply here.
Back
Top Bottom