Solved

Exchange 2007 to Exchange 2013  Mailbox Migration Best Practices?

Posted on 2014-03-19
3
664 Views
Last Modified: 2014-03-31
I have, in the recent past, migrated several clients to MS Office 365 Hosted Exchange Services from various versions of MS Exchange Server including Exchange 2003.  I like the ability to pre-populate the online user mailboxes by moving the mailbox data but not moving the actual mailboxes before making a final DNS cutover to the new site.

Is it possible to do something similar when moving from local legacy Exchange Server to a new local Exchange Server 2013?  

If not, are there easy ways to move large mailboxes without inconveniencing the owners of those mailboxes?  

Finally, when migrating from SBS2003 to SBS2008 (or SBS2011) Microsoft automatically set up bridgeheads and connectors that allowed all mail to flow from the legacy server until the final cutover was made.  To accomplish this task in Exchange 2013 should I simply setup a second public IP address for the new server and make sure that there is mail flow through the firewall and email gateway service provider before I move any mailboxes?

I realize that I've asked three separate, but hopefully closely related, questions.  If someone can provide an easy "best practices" approach to my answer I'll be grateful.

Thanks,

J
0
Comment
Question by:Qualitycomputer
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
3 Comments
 
LVL 19

Accepted Solution

by:
R--R earned 500 total points
ID: 39940007
First you cannot populate the mailboxes here as the mailboxes are available on legacy server. As this is a exchange 2007 I would recommend to move the mailboxes during weekend because once the mailbox started moving you will not be able to access the mailbox.

The second IP is not required as the email flow will be fine. Once the mailboxes are move you can redirect the traffic to the new server on firewall.
0
 

Author Comment

by:Qualitycomputer
ID: 39941301
My thought on the second IP address is that I could move a few mailboxes at a time and have mail flow from both servers rather than needing to move all the mailboxes at once and then cutting over the firewall settings.

Thanks for your input on this.
0

Featured Post

Is Your AD Toolbox Looking More Like a Toybox?

Managing Active Directory can get complicated.  Often, the native tools for managing AD are just not up to the task.  The largest Active Directory installations in the world have relied on one tool to manage their day-to-day administration tasks: Hyena. Start your trial today.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

How to resolve IMCEAEX NDRs in Exchange or Exchange Online related to invalid X500 addresses.
A couple of months ago we ran into an issue that necessitated re-creating our Edge Subscriptions. However, when we attempted to execute the command: New-EdgeSubscription -filename C:\NewEdgeSub_01.xml we received an error indicating that the LDAP se…
In this Micro Video tutorial you will learn the basics about Database Availability Groups and How to configure one using a live Exchange Server Environment. The video tutorial explains the basics of the Exchange server Database Availability grou…
This video demonstrates how to sync Microsoft Exchange Public Folders with smartphones using CodeTwo Exchange Sync and Exchange ActiveSync. To learn more about CodeTwo Exchange Sync and download the free trial, go to: http://www.codetwo.com/excha…
Suggested Courses

634 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question