migrating from exchange 2003 to exchange 2013

We currently have the following servers 2003, 2008,2012
we have 2 DC's. domain functional level  at windows server 2003

What we want to do is migrate our exchange server 2003 to exchange server 2013

We would like to know the best possible solutions to get this done

Requesting if steps can be provided briefly with links
Member_2_6474242Senior Systems AdministratorAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

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.

Brian BEE Topic Advisor, Independant Technology ProfessionalCommented:
Since Exchange 2003 and 2013 can't exist in the same domain, you may have to take some in between steps.

Depending on the number of mailboxes, you might be able to dump everything out to PST and then import into 2013. There are tools that can do that as well such as: https://www.codetwo.com/blog/migrating-exchange-2003-straight-to-exchange-2013/

Do you already have a 2013 license, or will you be buying one now? Since FYI 2016 is what you be buying now and then downgrading the license.
AmitIT ArchitectCommented:
Best possible is to move to office 365. if you want to stick on-premises, hire an IT Architect for Exchange, that can help you to perform the migration. Or Microsoft also can help you out. If you want to do it yourself and you have migration experience, you can start with Exchange deployment tool and understand the migration requirement.

In your case, best option to migrate to Exchange 2010 first and then directly to 2016. Skip 2013 altogether. Exchange 2016 is much more simplified and improved compared to 2013. Remember 2019 also coming soon.
Tom CieslikIT EngineerCommented:
Like mine colleges before me said It is NOT POSSIBLE migrate 2003 to 2013 in same forest, because Exchange 2003 and 2013 can't co-exist in one forest.
So if you have a lot of mailboxes and don't want to export all of them to PST file, install new Exchange and import PST to mailboxes you have 2 choices:

1. Backup Exchange using some software with granular recovery option like Symantec Backup Exec, demote your old Exchange, remove from domain, clean Forest from all informations about Exchange, Install new 2012 server with Exchange 2013, create all mailboxes manually and recover all emails from backup to new Exchange.

2. Create new Forest with new DC, join all users to new domain, Install new Exchange 2013 and then transfer all mailboxes using Cross-Forest-Migration

If you have no choice, you can deploy Exchnage 2010 on Windows server 2008, Migrate mailboxes, from 2003, then remove 2003 from domain and Mgrate again to 2013 but this will be very time consuming job.
Big Business Goals? Which KPIs Will Help You

The most successful MSPs rely on metrics – known as key performance indicators (KPIs) – for making informed decisions that help their businesses thrive, rather than just survive. This eBook provides an overview of the most important KPIs used by top MSPs.

The best and most convenient approach to you and to your users is to add Exchange 2010 into the environment, (would mean some AD domain and forest upgrade) migrate the users' mailboxes over and remove Exchange 2003. Once there, migrate over to 2016.
You will also need to upgrade your users' Outlook to the version that would allow to connect to the Exchange server which is in use at the time.
You would require a proper SSL certificate, name planning and much much more ...
Ajit SinghCommented:
The direct migration is not supported, even you can not able to install exchange 2013 or 2016 on a exchange 2003 environment. I would suggest to install one Exchange 2010 (with latest SP) and migrate from 2003 to 2010 at first step.: https://blogs.technet.microsoft.com/mconeill/2013/04/03/migration-from-exchange-2003-to-2013-a-no-go/

General Steps:

-Install Exchange 2010 into your Exchange 2003 organization.
-Configure Exchange 2010 and Exchange 2003 coexistence.
-Migrate Exchange 2003 mailboxes, public folders, and other components to Exchange 2010.
-Decommission and remove all Exchange 2003 servers.
-Install Exchange 2013/2016 into your Exchange 2010 organization.
-Configure Exchange 2013 and Exchange 2010 coexistence.
-Migrate Exchange 2010 mailboxes, public folders, and other components to Exchange 2013.
-Decommission and remove all Exchange 2010 servers.

Consider Exchange Server Deployment Assistance a web based application just you have to select what kind of deployment you were interested and then its provide you step-wise instructions to get this job done: https://technet.microsoft.com/en-us/office/dn756393.aspx

Hope this helps!

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
Sandeep KumarAssociate ConsultantCommented:
You can't do migrations directly from Exchange Server 2003 to 2013 because coexistence is not supported by Microsoft. But you can do so by using Kernel Migrator for Exchange software. It can perform Exchange direct migrations in both cross or intra-forest type. Visit https://www.nucleustechnologies.com/exchange-migration/ to know more about its features and support.
CodeTwo SoftwareSoftware DeveloperCommented:

@Brian B. thank you for mentioning our software.

CodeTwo Exchange Migration tool is a fully featured application that allows you to directly migrate the mailboxes' content from the old environment (Exchange 2003) to the new one (Exchange 2013/2016). No double-hop migration required. We have also an alternative version that handles migration to the Office 365.

There is no downtime for both of the environments so you can perform the process during normal working hours. The mailboxes can be automatically created with preserving chosen old AD attributes. What is more, all old EX addresses are converted (optionally) to SMTP equivalents, so if you are staying with same domain, you will be able to reply on migrated emails out of the box.

The process is handled by MAPI protocol (as the only alternative for old Exchange) and by EWS regarding the target environment. You can create multiple migration jobs so the program allows you to handle the migration topic as you want.

And of course the software comes with free support during your trial. You can test the software for free.


Member_2_6474242Senior Systems AdministratorAuthor Commented:
Thanks to all
Tom CieslikIT EngineerCommented:
My suggestion was exactly same as Ajit so I'm surprised why you did not split points between us. That's why assisted solution is for.
AmitIT ArchitectCommented:

i posted the objections. lets wait for the moderator.
Member_2_6474242Senior Systems AdministratorAuthor Commented:
the reason why i accepted that solution is because it is well explained.
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.