Hi, I hope somebody can help me get this sorted out. We have a company with a domain called abc.local which is running exchange 2003. They have had lots of problems within there domain and the General Manager wants to create a brand new domain called zyx.local. She would also like to install a new exchange 2010 server in the xyz.local domain. So far I have setup the new domain in AD. I'm just installing exchange 2010 in the xyz.local domain. My question/concern here is how am i to get all the data (mailbox etc.) from the exchange 2003 server to the exchange 2010 server?

Hi, yes is scenario is supported refering to http://technet.microsoft.com/en-us/library/bb124008(EXCHG.140).aspx (Transitioning to Exchange 2010) If you need detailed information for the upgrade process please refer the Microsoft documentation: http://technet.microsoft.com/en-us/library/aa998604(EXCHG.140).aspx regards Thomas Paetzold visit my blog on: http://sus42.wordpress.com

Hi, to me it's not clear what you're exactly up to as long as some important questions are open: - you talk about a new domain xyz.local. Is it a new domain within the existing forest? Or a new domain in a new forest? - will users remain in the existing domain zyx.local or will they be migrated to xyz.local? - do you plan to create new Outlook profiles or is it necessary to retain existing profile contens? Regards, MarkusMCSE:Messaging

You can use the Move-Mailbox cmdlet to move mailboxes across forest, see TechNet Upgrading to Exchange 2007 & How to Move a Mailbox Across Forestsfor more details. But moving the mailbox data is only part of the migration process for most projects I work on. Most clients want mail flow to work before, during, and after the migration between both forest and also want to migrate distribution groups and contacts also. If you use ADMT it will only migrate some of the AD attributes for users and groups, the Exchange attributes are not migrated since they are unique to the forest the object exist in. So you will lose e-mail address, delivery restrictions, delegate info, and more. Therefore, you need to use other tools (3rd party or scripts) to migrate and convert the additional attributes to do a full fidelity migration. In addition, the Exchange tools do not migrate Public Folders, groups, or contacts. Doing a full fidelity cross forest migration is a complex process that takes many hours of planning, testing, and work to provide a smooth migration. I've done dozens of them and each one is a bit different and different issues come up in about everyone. If you need an expert migration consultant to assist your organization feel free to contact me directly.If this post helps to resolve your issue, please click the "Propose as Answer" If you find it helpful , mark it as helpful by clicking on "Vote as Helpful" button at the top of this message. By marking a post as Answered, or Helpful you help others find the answer faster. If you need an expert migration consultant to assist your organization feel free to contact me directly. Jason Sherry | Blog | Hire Me | Twitter: @JasonSherry Microsoft Infrastructure Architect, MCSE: M, MCTIP, Microsoft Exchange MVP