GD Bloggers

This is the blog site for Microsoft Global Delivery Communities focused in sharing the technical knowledge about devices, apps and cloud.
Follow Us On Twitter! Subscribe To Our Blog! Contact Us

Part 3: Step-by-Step Exchange 2007 to 2013 Migration

Part 3: Step-by-Step Exchange 2007 to 2013 Migration

  • Comments 26
  • Likes

In part 1 we covered the deployments steps for Exchange 2013, in Part 2 of this series we covered Exchange 2013 configurations and testing, in this part we will start our migration. Make sure to start these configuration outside business hours, also plan a proper downtime to complete these steps and test them.

6.Move Client Access from Exchange 2007 to Exchange 2013

Virtual Directories

Open Exchange 2007 management shell and run the following commands.


Set-OwaVirtualDirectory -Identity "e12-01\OWA (Default Web Site)" -ExternalUrl



Set-OabVirtualDirectory -Identity "e12-01\OAB (Default Web Site)" -InternalUrl -ExternalUrl



Set-ActiveSyncVirtualDirectory –Identity “e12-01\Microsoft-Server-ActiveSync (Default Web Site)” –ExternalUrl $Null –InternalUrl


Web Services:

Set-WebServicesVirtualDirectory –Identity “e12-01\EWS (Default Web Site)” -InternalUrl –ExternalUrl


Unified Messaging:

Set-UMVirtualDirectory -Identity "UnifiedMessaging (Default Web Site)" –InternalUrl –ExternalUrl

Outlook Anywhere:

Set-OutlookAnywhere -Identity "E12-01\Rpc (Default WebSite)" -IISAuthenticationMethods Basic,Ntlm


TMG Rules:

Create/update your TMG publish rules

For Exchange 2007 update your publish rules to accept connections for Legacy name space:


Follow the steps in this link to publish Exchange 2013.

DNS Configurations:

Update your DNS records as follows

Internal DNS



Point to Exchange 2013 server

Point to Exchange 2013 server

New record points to Exchange 2007 Server

Public DNS



Point to TMG Listener

Point to TMG Listener

New record Point to TMG Listener


Apply all your test scenarios for both internal and External client types; once again you can use Microsoft Remote Connectivity Analyzer

7.Move Mailboxes:

Once you complete your tests successfully, its time to start moving mailboxes. you can do this using EAC or Shell.

New-MoveRequest -Identity '' -TargetDatabase "DB01"


You can create Batch moves as described in this link. Once you complete your mailboxes migration let us move to the final steps in this migration process (PF Migration and Exchange 2007 Decommissioning).

  • As per my Experience, you just need legacy for owa and EWS.

  • Great write up. I am already migrating users however the move request only does 2 mailboxes at a time. Do you have any ideas of how to increase this?

  • For Greg. There is a setting to adjust on target CAS server to increase moves.

  • Hi, great articles ! But what about receive connectors after decomissionning Exchange 2007 ? If you don"t recreate receive connectors from Exchange 2007, what's happening ?

  • HI, I tried to move the mailboxes across using the PowerShell and EMC and both ways I tried the move is just sitting on queued, I left it for a day and the same thing.. Queued with 0% progress.
    Any suggestions?

  • Hey, GZ, I was sitting here watching my attempt at moving a mailbox sit here on zero percent and then I saw this. Did you find out what was causing this, or find a resolution?
    Thanks in advance,

  • Never mind. . . I just did a get-moveRequestStatistics command and it says percent complete is up to 32. So maybe the command just isn't refreshing and one must run this get-moveRequestStatistics command every so often to check the progress? Oh well. Good luck... to me and you and everyone in this boat...

  • As I was migrating from Exchange 2007 to Exchange 213, I got an error, "Set-OwaVirtualDirectory: Object is read only because it was created by a future version of Exchange: 0.10 ( Current version supported is 0.1 (8.0.535.0)", from Exchange 2007 management shell when i run the command "Set-OwaVirtualDirectory -Identity "e12-01\OWA (Default Web Site)" -ExternalUrl"

    Please help. Thanks.

  • Thank you.

  • this is a nice Article.

  • Hi. question. im migrating from Exch 2007 to 2013, im mostly finished, I need to move near 2000 users and groups. I need to migrate firs one of the administrators account to test the process, mi question is. will he be able to access groups that are in the legacy environment once he will be moved to 2013? or need to move also the groups he has?


  • @ Nacho, what do you mean by accessing the group?

  • Thank you so much for this, you are a life saver! Very straight-to-the point tutorial. Conclusively, can I apply these same steps going from exchange 2013 to another exchange 2013 box? I'm trying to migrate 2007-->2013--->2013 (to be same name/ip as the 2007 box). My guess is yes.

  • @Son can you elaborate more what you are trying to achieve, and the approach you will take...

  • @Mohammad - I'd like to migrate from 2007 (hostname currently email) --> 2013(new hostname is emailnew) using your approach. I would then like to migrate the 2013(hostname emailnew) to 2013(hostname back to email with original ip address). Would this be the correct approach or is there something easier?

    Summation: Migration 2007-2013 keeping original name and IP (swing migration).

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment