Moving/Migrating mailboxes from one Exchange 2007 server to a new Exchange 2010

Just trying to ascertain the best way to migrate mailboxes from an existing Exchange 2007 server to a brand new Exchange 2010 server.

The new platform is Windows Server 2011 Standard, the old platform is Server 2003.
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

SriHarsha KTechnical Services SpecialistCommented:
For Migration from Exchange 2007 to Exchange 2010,please follow this.

and to move mailboxes from Exchange 2007 to Exchange 2010,

Note- This is for LOCAL MOVE REQUEST (i.s moving mailboxes within the same forest)

UncleVirusAuthor Commented:
Thanks for your reply - These are going to be moving to a completely new domain, on a completely new server.

I've actually come across this URL while googling for a solution - I'm afraid it only covers migrating from one server to the same server. :-(

I could export all the emails locally on each machine as a PST, then import the mail back in. We're talking 6 users here so it's not exactly going to take a huge amount of time.

Are there any implications in doing this?
Seeing as your new server is a SBS 2011, you won't be able to join or create any forest trusts too. So that option goes out of the window.

If you export and import emails from one Exchange environment to another, you're gonna have problems when replying to old emails, which will populate AD information which has been embedded into old emails. So users will need to delete the TO and CC information and retype it in again.

See the following question which I advised on the same thing:

Also bear in mind that if you use Exmerge, PSTs will be capped at 2 GB and will get corrupted if exceeded. So make sure you export via Outlook.

Hope that helps answer your question with a heads up.

Determine the Perfect Price for Your IT Services

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden with our free interactive tool and use it to determine the right price for your IT services. Download your free eBook now!

Madan SharmaConsultantCommented:
Microsoft provides inbuilt wizard from SBS2003 to SBS2011

check this link:-
Madan SharmaConsultantCommented:
if you don't have SBS version of 2003 then I'll advise you install and configure your SBS2011 separately  and export mailboxes to pst from old server and upload them to new server.

this is because Microsoft only support SBS to SBS transiting but it you go for it and any issue comes up then Microsoft will not support you.
I may be wrong but my interpretation is as follows:

EXISTING SERVER: Server 2003 with Exchange 2007
NEW SERVER: SBS 2011 with Exchange 2010

Therefore migrations from other non SBS platform migrations are a no no. Unless you want to look at the swing method too, if so you need 'SBS 2011 Kit 1' from here:

UncleVirusAuthor Commented:
Hmm, I want to migrate JUST the emails, no active directory no nothing.

I think the only way to go with this is:

Dump the contents of a user's mailbox to a PST file, and then import this into their new mailbox using Outlook manually - ON THE PROVISO that the users *cannot* and *must not* reply to existing emails. (E.g move them to an 'ARCHIVED' folder under their mailbox, and leave them well alone.

I have a feeling this is the only solution..
What are you thoughts guys? Cheers!
Best way forward, remember to do PST export via Outlook if their mailboxes are over 2GB.  Don't forget public folders if you have any too.

Best of luck!
Madan SharmaConsultantCommented:
yes this will be good option for you and don't worry about  replying existing email that issue will not come up with this process.
UncleVirusAuthor Commented:
Nice and simple! - No public folders, and 6 mailboxes to move across. Shouldn't be too bad really! And okay, can you confirm that by exporting the PST's beforehand logged on as the user - They can reply to existing emails?
If you perform an exmerge or PST as the user, you will still have the reply problem as the AD information is embedded into the emails. Read my original post and the link inside that which explains the matter in a little more detail. It's just one of those things you have to live with.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
UncleVirusAuthor Commented:
No worries. I will forewarn the end-users of this issue. Thank you for your assistance! I will award points as necessary.
Your welcome, cheers.
UncleVirusAuthor Commented:
As above. Guidance points to manually exporting PST's due to the scale of the task (6 mailboxes, not too much work involved!)

Along with the warning that users will be unable to hit 'Reply' on old/archived/imported emails on the new system!
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.