Still celebrating National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17

x
?
Solved

Exchange 2007 to Exchange 2013  Mailbox Migration Best Practices?

Posted on 2014-03-19
3
Medium Priority
?
668 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 2000 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

Get free NFR key for Veeam Availability Suite 9.5

Veeam is happy to provide a free NFR license (1 year, 2 sockets) to all certified IT Pros. The license allows for the non-production use of Veeam Availability Suite v9.5 in your home lab, without any feature limitations. It works for both VMware and Hyper-V environments

Question has a verified solution.

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

The core idea of this article is to make you acquainted with the best way in which you can export Exchange mailbox to PST format.
The main intent of this article is to make you aware of ‘Exchange fail to mount’ error, its effects, causes, and solution.
To show how to create a transport rule in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Mail Flow >> Rules tab.:  To cr…
The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager
Suggested Courses

670 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