Migrating from Exchange Server 2003 to Exchange Server 2010: A Small Organization Perspective

Learn from real-world experience

In this article, you'll learn how to migrate your Exchange Server 2003 infrastructure (both  your front-end and back-end servers) to Exchange Server 2010. I'll focus on the requirements of smaller organizations, because the needs of larger organizations typically just scale up from there. I was lucky enough that one of my partner companies, Clark Systems Support, allowed me to do their migration, and I based this article on my experience there. Exchange Deployment ...

Buy This Project Plan Now!

This content is part of the Exchange Server 2010 Migration Project Plan.

Purchase this project plan to receive:

  • Step-by-step guidance for managing your project, start to finish
  • Tested advice for preparing for and completing your project
  • Insights to help you avoid common pitfalls and traps

Already registered? here

Discuss this Article 7

Anonymous
on May 25, 2010
Since our organization is only running an Exchange 2003 SP2 server and no Exchange 2007 servers I assume it's ok NOT to install the KB937031 Hotfix?
JEmlay
on Nov 1, 2010
Two things.

1. After following your guide my 2003 server stopped sending email out. In addition, any email sent to my 2003 machine where a user was on the new 2010 machine, didn't get their emails. Everyone got stuck in the queue. After an hour of reading the MS website I found a page that told me to run:

New-RoutingGroupConnector -Name "Interop RGC" -SourceTransportServers "Ex2010Hub1.contoso.com" -TargetTransportServers "Ex2003BH1.contoso.com" -Cost 10 -Bidirectional $true -PublicFolderReferralsEnabled $true

Right after, all unsent mail got sent. I have a single Exchange 2003 setup and am moving to a single 2010 setup. Something in your guide is missing. There is NO routing between the two servers from following your guide.

2. Set-OWAVirtualDirectory Clark2008\OWA* ` - that means nothing to me. What is Clark2008? What are we looking to put in there ourselves? Either way I dropped it. I see no reason to run the legacy stuff at all. Until the new server is fully functional, we simply have two mail servers addressable from the outside. No big deal.

All in all, thanks for the guide! Aside from that one hiccup, it got the job done. Two hours of downed email...blah, they can deal with it! :)
muraty
on Sep 24, 2010
Michael, these two sentences maybe misleding: "Exchange must be in Native mode. You can't have any Exchange 2000 servers..."
When you read this you think that because you cannot have Exchange 2000, the Exchange org must be switched to Native mode. It is not. The native mode requirement says that you just cannot have Exchange 5.5 servers before 2010 installation. Getting rid of the Exchange 2000 servers is a separate requirement and has nothing to do with the Native Mode requirement.
bentg
on May 25, 2010
Since our organization is only running an Exchange 2003 SP2 server and no Exchange 2007 servers I assume it's ok NOT to install the KB937031 Hotfix?

Please or Register to post comments.

Exchange Server 2010 Project Plan

<<< Back to the Project Plan


Planning


A First Look at Echange 2010

Exchange 2010 SP1: More Than a Simple Upgrade

Exchange Server Deployment Options

Preparing to Deploy Exchange 2010

Advancements in Exchange 2010 and Communications Server "14"

Planning for Exchange Server 2010 Personal Archives

Load Testing with Exchange 2010

Exchange 2010: Can You Have Too Much RAM?

Session 1: Bigger Mailboxes, Fewer Disks, Less Money

Migrating


Migrating from Exchange Server 2003 to Exchange Server 2010: A Small Organization Perspective

Going Virtual with Exchange 2010

Exchange Server's Client Access: An Introduction

Exchange Server's Client Access: Deploying Your Servers

Session 2: Virtualization The Straight Scoop

Exchange Server's Client Access: Load-Balancing Your Servers

Exchange Server’s Client Access: Securing Your Servers

Moving Mailboxes the Exchange 2010 Way

Exchange Server 2010 SP1 Mailbox Import and Export

Working with the Features of Exchange 2010


Mastering Exchange Server 2010’s Exchange Control Panel

Exchange 2010: High Availability with DAGs

Deploying Database Availability Groups in Exchange Server 2010

What’s New In Exchange 2010 & Remote PowerShell

Exchange Server’s Client Access: Server Administration

Exchange Server 2010 Role Based Access Control

Auditing Administrators’ Actions with Exchange 2010

Database Maintenance in Exchange Server 2010 SP1

Information Rights Management in Exchange 2010

Exchange 2010 High Availability

Walkthrough of Exchange 2010 DAG Creation

Multi-Mailbox Search in Exchange Server 2010

Exchange 2010 MRM: Implementing New Retention Policies

Exchange 2010 MRM: How to Modify and Reduce Help Desk Calls About Retention Policies

Manipulating Mailbox Contents in Exchange 2010

More Exchange 2010 SP1 Mailbox Cmdlets

Prevent Problems with Exchange Server 2010's MailTips

OWA Customization in Exchange 2010

Exchange Server 2010: A New Mobile Frontier

Unified Messaging in Exchange 2010

Session 3: Exchange Management Shell