Improve company productivity with a Business Account.Sign Up

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 520
  • Last Modified:

Migration from Exchange 2003 to 2010 without coexistence?

Is it possible to migrate a single Exchange 2003 server to Exchange 2010 without using coexistence?

I would like to export user mailboxes and public folders to PST files and import them to the new Exchange 2010 afterwards. Do I miss something important or is it possible to migrate a small Exchange server that way without problems or missing data?

I did not setup the Exchange 2003 system. Are there any options/features where some additional data or unusual preferences could be stored?

Is it better to use Outlook or Exmerge to create the PST files? I am thinking about problems with code pages using Exmerge. Will this be a problem if I use Outlook instead?
  • 2
  • 2
  • 2
  • +1
1 Solution
MAS (MVE)Technical Department HeadCommented:
Exchange 2003 usually runs on 32-bit hardware whereas Exchange 2007 / 2010 requires 64bit hardware.

If your current server is 32bit you will have to buy a new hardware. Then upgrade using the link below.

Or if your current hardware is 64bit and you do not want to buy new hardware
1.Export your mailboxes to PST using Exmerge
2.Export your Public Folders to PST from your outlook
3.Install exchange 2010 using the below URL

MAS (MVE)Technical Department HeadCommented:
Please check this if you want to uninstall/remove exchange2003 from your networt
Malli BoppeCommented:
Any real reason why you want go about creating PST files, instead of going through the co-existance path.

With your Approach.
1.) Creating PST files and import them would lot longer then  moving hte maailboxes.
2.) When building new exchange 2010 server in the same domain it would recognise that you have 2003 server and wouldn't let you gohead.
3.)Moving PB would be lot more difficult
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

exexcAuthor Commented:
I'm planning to rebuild the whole network (including DC / Active Directory) because

a) It was not configured by me and has some design decisions I don't like (for example a very poor OU-structure, inconsistent role based access controls, 3rd party POP-connector instead of SMTP)

b) There are a lot of DNS/Replication and other errors in the event log and it will be faster/cleaner to start from scratch, than fixing all those problems

c) It's a small and very simple network (no policies, no complicated security structure, only 15 users)

So there won't be any problems with the active directory or leftovers from the old Exchange system.

What is PB?
Well with ExMerge  or a third party tool you can export to disk for transport and then import via 2010. with that said consider the following;

1. ExMerge only supports the ANSI PST Format which has a 2GB limit
2. ExMerge will not warn you if a PST goes over 2GB, it will just corrupt the PST and you won’t know it until you try to open it :-(

NOTE: ANSI PST's actually start to degrade at about 1.8GB so I would not go over that limit in order to ensure the data is recoverable

3.Here is an article on how to script the creation of overflow PST's if you reach the 2GB limit

4. Alternatively, you can look at 3rd party tools that can open any offline database so that you can export to Unicode PST format which has a 20GB limit.  Just put a search into Google for something like “Export or Recover Mailboxes from an Exchange Offline EDB or Live Production Exchange Server” and you will find several options. 

5. Keep in mind that their have been some issues with moving data from older exchange servers into Exchange 2010 has had some issues with importing legacy ANSI data and when that happens the CAS service restarts and all users are disconnected.  There is allot out there on this but check out  and

5.a best way to attempt to overcome this is to ensure the 2010 side is patched to the hilt before you start, i.e. SP1 RU5

5. Either way bear in mind that since you will not be using the official MS mailbox move process, replies to the imported messaging items may fail and modifications to old calendar items may not work right because the X500 addresses from the original Exchange server will not be assigned to the mailboxes in the new Exchange server. Here are some details about that problem here: 

** and you can use the LegacyExchangeDN tool 

** Basically, you need the legacyExchangeDN from the old Exchange install to be added to the new recipients as an X500 format ProxyAddress entry. It's not too bad to do, once you know what to do.

exexcAuthor Commented:
Happy to assist and thanks for the points
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

  • 2
  • 2
  • 2
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now