Avatar of Anthony H.
Anthony H.
Flag for United States of America asked on

Migrating Exchange

I have an exchange 2003 box in Texas. I bought a new server running Windows 2008 with Exchange 2013 std, located in a Colo in Irvine CA.

I want to migrate from 2003 to 2013 (Exchange).  I'm looking for high level ideas on the BEST way to do this. Migrating up to 500 email accounts.

any ideas?

The old 2003 server is at an office in Texas.  The new server is in a colo.
Put them on the cloud temporarily?
setup a VPN between locations and migrate?
Upgrade from 2003 to 2010 first , then 2013?
What about Active Directory?
Why not leave Exchange is Texas and setup HTTPS? (question to myself - no need to address).
ExchangeWindows Server 2003Active Directory

Avatar of undefined
Last Comment
Anthony H.

8/22/2022 - Mon
Sandesh Dubey

If you planning for MS exchange 2013 deployment then upgrade path will be Exch2003 to Exch2007/2010 and then to Exch2013.The exchange supportability matrix link for your reference:http://technet.microsoft.com/en-us/library/ff728623(v=exchg.141).aspx.You can setup vpn connectivity and perform migration.


I don't think that till now the migration from exchange server 2003 to exchange server 2013 is there. Moreover it is highly recommended that first you should migrate from exchange server 2003 to 2007/2010 and then to 2013.

For migration from exchange server 2003 to 2013, you can refer to two methods below:



Moreover there are many third party tools as well which can do such operations quickly. You can ask the Experts Exchange community for this.
Simon Butler (Sembee)

View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
Ask your own question & get feedback from real experts
Find out why thousands trust the EE community with their toughest problems.
Anthony H.

sembee2: For option 1, are you assuming there is a VPN between the two sites? if not, how would exchange work without AD?
All of life is about relationships, and EE has made a viirtual community a real community. It lifts everyone's boat
William Peck
Simon Butler (Sembee)

Yes, there is a presumption that you have a VPN. You would also need to have a domain controller in the second location - no AD no Exchange. Running Exchange with a remote domain controller isn't a good idea.

Anthony H.

so I found out there is an MPLS between the sites.  the server in the colo  is not in the same subnet.  here is what I got so far based from your comments.

there is ONE server in texas.
there is ONE server in the colo in IRVINE CA.

I need to put the server in the COLO on the same subnet as the server in Texas.
I then need to put another AD server in the colo
I can then begin the migration but point the exchange to the AD IN THE COLO manually through exchange console?

How can I do the migration with no downtime?
Simon Butler (Sembee)

As long as you configure the two locations with separate subnets and configure Sites and Services correctly in Exchange, there will be no need to manually configure the domain controllers in Exchange. The Exchange server will use the closest domain controller.

As for a migration with no downtime - build an Exchange 2010 server, migrate all data to that (only downtime is on individual mailboxes while they are being moved). Remove the Exchange 2003 server. Build the Exchange 2013 servers and then move the mailboxes to that. Again the only downtime is at the end of the move mailbox phase.

Try out a week of full access for free.
Find out why thousands trust the EE community with their toughest problems.
Anthony H.

Simon: can you private message me? am I allowed to give you my email address on here?
Simon Butler (Sembee)

It is against the rules of the site to do things off site.

Anthony H.

I have not made any progress on this. it's on hold.
Your help has saved me hundreds of hours of internet surfing.