What is the best method to upgrade exchange 2003 to exch 2013?

Posted on 2015-01-21
Last Modified: 2015-01-22
I know there is no direct migration path frpm exch 2003 to exch 2013 but I was wondering if there is any good docs out there for the procedure for migrating from exch 2003 to exch 2013?
Do they have to migrate to ech 2010 first and then after all that work is done then go back and migrate to exch 2013?
Question by:vmich
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 35

Assisted Solution

by:Seth Simmons
Seth Simmons earned 250 total points
ID: 40562913
yes you need to migrate to either 2007 or 2010 first then to 2013
the 2003 server needs to be completely gone before installing 2013 since setup will halt if it detects a 2003 server present

other option is to migrate to pst files, remove exchange 2003, install 2013, create new mailboxes and import everything
involves downtime and not really practical for that reason

Author Comment

ID: 40562919
So I guess exch 2013 cant even be in the same forest then so I would have to create another forest and then build exch 2013 there and then use a third party tool to migrate from exch 2003 to 2013 correct?
Unless I build an exch 2010 server in the same forest and then migrate to it and then build the exch 2013 in the same forest.
Any idea on any good third party migration software for this?
LVL 34

Accepted Solution

it_saige earned 250 total points
ID: 40562943
It would be best (as Seth indicated) to migrate to Exchange 2007/2010 first (personally I would recommend Exchange 2010 over Exchange 2007).  Once this is completed then the migration to Exchange 2013 is extremely easy.  It should be noted, that while Exchange 2013 cannot coexist with Exchange 2003, it does coexist with Exchange 2007 and Exchange 2010.

As for the reason to my recommendation.  There are benefits to migrating from Exchange 2010 to Exchange 2013 over Exchange 2007 to Exchange 2013.

First, there is no need for a legacy record as all connections are proxied to the Exchange 2010 server from the Exchange 2013 server.

Second, there is the ability to perform an online move/migration of mailboxes from Exchange 2010 to Exchange 2013.

Free Backup Tool for VMware and Hyper-V

Restore full virtual machine or individual guest files from 19 common file systems directly from the backup file. Schedule VM backups with PowerShell scripts. Set desired time, lean back and let the script to notify you via email upon completion.  

LVL 35

Expert Comment

by:Seth Simmons
ID: 40562945
CodeTwo has a product but, of course, would require a new forest.

you could do a 2010 SP3 install with no product key (as a trial) to get through the migration

Expert Comment

by:Doug Williams
ID: 40563656
Unless you have the ability to build a new forest, all 2003 Exchange servers have to have all their objects (Including the system, test, and arbitration mailboxes) migrated to exchange 2007 or 2010. Then all 2003 servers must be GRACEFULLY removed from the organization (AD) so you must follow the full uninstall and decommissioning of those servers especially the last Exchange 2003 server.

To minimize the disruption, and not cause performance issues, make sure you have an appropriate number of Exchange 2010 servers to receive all of the mailboxes, public folders and all the other Exchange Objects of your organization.  I.e., don't plan on moving 3000 objects from four Exch 2003 servers onto one Exchange 2010 server.  The performance hit could be unacceptable. You need to design a 2010 organization that will be functional for the interim time.  This will be much easier on you and the company budget, if you can do this with VMs.  I concur that if you fully plan out both steps (2003-> 2010, and 2010-> 2013) you can get away with an unlicensed install of 2010 (functional for 90 days) then migration to the licensed destination of Exchange 2013. I would combine the advice you have here into one well planned two step procedure.

Remember however that you WILL have down time for the users as they are migrated from 2003 to 2010, as there is no online mailbox-move ability from 2003 -> 2010.  You will need to carefully plan the migrations for your users during non-business hours or you will have some very unhappy users and bosses.

Expert Comment

by:Minecraft_ Enderman
ID: 40563786
You must first upgrade the Exchange 2003 organization to either an Exchange 2007 or Exchange 2010 organization, and then you can upgrade the Exchange 2007 or Exchange 2010 organization to Exchange 2013. We recommend that you upgrade your organization from Exchange 2003 to Exchange 2010, and then upgrade from Exchange 2010 to Exchange 2013.
To help simplify your deployment, whether you’re moving your organization to the cloud or upgrading your on-premises organization, we created the Exchange Server Deployment Assistants (ExDeploy) to help guide you through the upgrade process. For more information about the ExDeploy tools, see Microsoft Exchange Server Deployment Assistant.

Author Closing Comment

ID: 40564059
upgrade to 2010 first..

Featured Post

Get HTML5 Certified

Want to be a web developer? You'll need to know HTML. Prepare for HTML5 certification by enrolling in July's Course of the Month! It's free for Premium Members, Team Accounts, and Qualified Experts.

Question has a verified solution.

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

Unified and professional email signatures help maintain a consistent company brand image to the outside world. This article shows how to create an email signature in Exchange Server 2010 using a transport rule and how to overcome native limitations …
A couple of months ago we ran into an issue that necessitated re-creating our Edge Subscriptions. However, when we attempted to execute the command: New-EdgeSubscription -filename C:\NewEdgeSub_01.xml we received an error indicating that the LDAP se…
The basic steps you have just learned will be implemented in this video. The basic steps are shown to configure an Exchange DAG in a live working Exchange Server Environment and manage the same (Exchange Server 2010 Software is used in a Windows Ser…
To add imagery to an HTML email signature, you have two options available to you. You can either add a logo/image by embedding it directly into the signature or hosting it externally and linking to it. The vast majority of email clients display l…
Suggested Courses

623 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