Moving Exchange 2003 mailboxes to Exchange 2007 or Exchange 2010 in a completely different domain

Posted on 2011-09-30
Medium Priority
Last Modified: 2012-05-12
Our company, let’s call us CompanyA, has been purchased by another company, CompanyB.  These companies are not in the same geographical area and we are not on the same domain or network – 2 completely separate entities still.  

CompanyA is running Exchange 2003 SP2 on Windows Server 2003 Standard.  CompanyB is going to upgrade from Exchange 2007 to Exchange 2010 before the end of 2011.

CompanyB wants to migrate our mailboxes, distribution lists, and mail-enabled public folders to their Exchange server, but are not sure if they want to do this before or after the upgrade.  

Our domain is called companya.com and their domain is called companyb.com.  After the migration, we will retain companya.com as our primary email address, but also will begin using companyb.com.  

Is there a "simple" way to perform this task?  I’ve researched online and found ideas with Exmerge, which doesn’t sound like it will work between the two different versions of Exchange, and read a little about cross-forest migration, which sounds really “involved”.
I’ve got some other ideas of my own, but wanted to see what the Exchange experts have to say.  

I realize that there are DNS records to take into account, but at this point, I’m more interested in the actual Exchange mailboxes getting moved to the new server and platform.  

Thank you.
Question by:SolCow
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
LVL 10

Accepted Solution

ThorinO earned 2000 total points
ID: 36894803
How many mailboxes are going to be migrated? If not a lot I would manually create them on 2007/2010, export to a PST on the 2003 side using exmerge and import on the 2007/2010 side using the import-mailbox command. You could do this as well with a lot of mailboxes.

The other option like you said would be to do a cross forest trust and migrate. If you are not on the same network you would need to setup a VPN.
LVL 27

Expert Comment

ID: 36894851
In your case migrating to 2007 or 2010 really does not do big difference. Using cross-forest migration you must create trusts between the two AD domains. Using exmerge you simply export the contents of mailboxes to pst files  and then import them to mailboxes created on new server. Exchange 2007 SP1+ uses Import-mailbox, Exchange 2010 Sp1 uses New-MailboxImportRequest cmdlet. On exchange 2010 sp1 you dont need to have installed outlook.

You will have a little more work with migration contents of public folders. Maybe the best option is moving contents to mailbox, then to pst, then to mailbox on new server and back to PF...
Anyway you will need to enable PF on exchange 2007/2010 if you want to use older outlook clients.

At the end it really depends on the number of mailboxes you have to move. With big number of mailboxes you will have a lot of work migrating them thru psts.

Having multiple email domain names is no problem at all.
LVL 12

Expert Comment

by:Deepu Chowdary
ID: 36895423
There are several ways to move the mailbox… like
--> Moving the mailbox through EMC
--> Moving the mailbox through powershell and
--> Moving the mailbox by mode script.

Actually it depends upon the scenario which options needs to be select.
--> If we want to move little number of users mailbox we can go with exchange management console.
--> If we are moving the users mailbox one by one we can go with powershell
--> If we want to move the mailboxes in a bulk then we can go with Powershell scripts.

Whenever we are moving the mailbox lots of thing needs to be considered like BadItemLimit, PreserveMailboxSizeLimit, IgnoreRuleLimitErrors, MaxThread etc.

Go through this link


Author Comment

ID: 36903750
Thank you for the feedback.  These suggestions were along the lines I was thinking - export to PST, create mailbox on new server, and import to new mailbox via VPN.  

Featured Post

Fill in the form and get your FREE NFR key NOW!

Veeam® is happy to provide a FREE NFR server license to certified engineers, trainers, and bloggers.  It allows for the non‑production use of Veeam Agent for Microsoft Windows. This license is valid for five workstations and two servers.

Question has a verified solution.

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

This article will help to fix the below error for MS Exchange server 2010 I. Out Of office not working II. Certificate error "name on the security certificate is invalid or does not match the name of the site" III. Make Internal URLs and External…
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.
In this video we show how to create an Accepted Domain 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 >> Ac…
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…

649 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