I’m excited to announce the release of the Exchange Server 2003 to 2010 Migration Guide.

Based on established best practices and lessons learned from migrating thousands of Exchange mailboxes, this guide will walk you through the entire process all the way from planning the project to removing the last Exchange 2003 server from your environment.

In the Exchange Server 2003 to 2010 Migration Guide you get:

  • The 200+ page PDF with detailed, step by step instructions that walk you through the entire process of migrating to Exchange Server 2010
  • A planning worksheet to record the important information you need from your existing environment for a successful migration project
  • A testing worksheet so you know that your new Exchange 2010 servers are working properly before you move any mailboxes
  • BONUS: Guide to Exchange Server 2010 Backup and Restore, to help you make sure your new Exchange 2010 servers are protected by backups
  • BONUS: How to Install an Exchange 2010 Client Access Server Array, to demonstrate how to configure a high availability pair of Client Access Servers
  • BONUS: How to Install an Exchange 2010 Database Availability Group, to deploy one of the most useful and exciting high availability features of Exchange Server 2010

One of the challenges of writing this guide was covering as much of the migration process as possible so that it is relevant to all of the unique Exchange Server environments out there in the real world, without making it too complex to read or impossible to actually finish writing it.

I solved this problem by including a detailed planning phase in the guide that leads you through the process of discovering all of the most important details of your environment that have an impact on the migration.

I also surveyed over 1000 readers of this website to find out the most common concerns about migrating to Exchange Server 2010, so that I could be sure that the migration guide covered those topics.

Click here now to get the Exchange Server 2003 to 2010 Migration Guide.

About the Author

Paul Cunningham

Paul is a former Microsoft MVP for Office Apps and Services. He works as a consultant, writer, and trainer specializing in Office 365 and Exchange Server. Paul no longer writes for Practical365.com.


  1. Rajil

    the click here link does not work. Where can I get the complete guide please.

      1. Jay Windsor

        I tried clicking on this link, and it takes one to a page with a “Download Now” button. When I click that button, it go to a “Microsoft Code Samples” page. I really would like to purchase the complete 200+ page How-to if still possible?

  2. Henry

    Thanks for a great Guide,

    However doesn’t fully cover my scenario with regards SSL certificates, our internal domain is for example : abc.com and the external domain is abc.co.il

    We purchased a WildCard certificate for abc.co.il and configured all of the virtual directories as:


    I have create a new internal DNS zone for the ABC.co.il domain (Split DNS)

    Internally everything is working fine including the Autodiscover, but from externally the autodiscover dosent work and i tried everything, do u have any ideas?


  3. junior

    Thanks for your swift response.

    We have decided to go with the SAN certificate.

    Currently we are using owa.domain.com in exchange 2003 and same for internal and mobile devices. When we move we want to use mail.domain2.com.

    my understanding is when i create the new certificate request i need to add the new domain name (mail.domain2.com) for external and autodiscover. For legacy i need to use domain.com (legacy.domain.com) and then export the certificate to the front-end Exchange 2003. is this correct?

    Also will the above cause issues with mobile devices initially, since they are configured to use owa.domain.com? When we start moving users to EX2010 the mobiles will be changed to the new domain name.

    1. Avatar photo
      Paul Cunningham

      Mobile devices should be fine as long as the new certificate still has the FQDN that mobile devices are connecting to (eg owa.domain.com). If not then they will likely start showing certificate and connection errors.

  4. Junior

    Hi Paul,

    I have purchased your Exchange 2003 to 2010 Migration Guide and it is an excellent guide, everything is simplified. However doesn’t fully cover my scenario with regards SSL certificates.

    We have TWO wild card certificates;

    owa.domain.co.uk – used by 2003
    owa.domain1.com – We want to use this for Exchange 2010

    Can we avoid purchasing the SAN certificate and use the wildcard instead? If so how can i use the above? do i need to install both certificates on the CAS/Hub Server?


    1. Avatar photo
      Paul Cunningham

      Wildcards will work.

      In your case it sounds like you want to change to a new domain/URL for OWA and other services as part of the migration. That is fine. The guide describes how to migrate *keeping* the same domain/URL for everything, so you’ll just need to substitute your desired configuration into any of those related steps.

      The CAS can only have one SSL cert bound to IIS. You should use the one you intend to be used for Exchange 2010 access.

Leave a Reply