none
Is it possible to migrate from exchange 2003 directly to 2010?

Answers

  • Yes, a migration from both Exchange 2003 and Exchange 2007 to Exchange 2010 will be supported.  As shown in the article Transitioning to Exchange 2010, you can see that Excahnge 2003 is supported.

    "You can only transition to Exchange 2010 from the following existing messaging systems:
    • Exchange 2007 messaging system
    • Combined Exchange 2003 and Exchange 2007 messaging system

    This means that if you are upgrading from an Exchange 2003 or Exchange 2007 organization, you can choose to either transition the organization, or migrate to a new organization. In most cases, you will want to retain the Exchange data from the existing organization, and so you should choose to transition to Exchange 2010.

    If you are upgrading from any messaging system besides Exchange 2003 or Exchange 2000, your only option is to migrate to Exchange 2007."


    Gary A. Cooper | Senior Systems Architect | MCA:Exchange2003 | MCM:Exchange2003/2007 | Horizons Consulting, Inc. | Wk +1.618.498.6744
    Wednesday, April 15, 2009 3:52 PM
  • Yes, it is possible and supported to migrate from Exchange 2003 to 2010 or keep in coexistence during transition.

    Coexisting with Exchange 2010

    Amit Tank | MVP - Exchange | MCITP:EMA MCSA:M | http://ExchangeShare.WordPress.com
    Wednesday, April 15, 2009 3:56 PM

All replies

  • Yes, a migration from both Exchange 2003 and Exchange 2007 to Exchange 2010 will be supported.  As shown in the article Transitioning to Exchange 2010, you can see that Excahnge 2003 is supported.

    "You can only transition to Exchange 2010 from the following existing messaging systems:
    • Exchange 2007 messaging system
    • Combined Exchange 2003 and Exchange 2007 messaging system

    This means that if you are upgrading from an Exchange 2003 or Exchange 2007 organization, you can choose to either transition the organization, or migrate to a new organization. In most cases, you will want to retain the Exchange data from the existing organization, and so you should choose to transition to Exchange 2010.

    If you are upgrading from any messaging system besides Exchange 2003 or Exchange 2000, your only option is to migrate to Exchange 2007."


    Gary A. Cooper | Senior Systems Architect | MCA:Exchange2003 | MCM:Exchange2003/2007 | Horizons Consulting, Inc. | Wk +1.618.498.6744
    Wednesday, April 15, 2009 3:52 PM
  • Thanks for your answer.
    Wednesday, April 15, 2009 3:54 PM
  • Yes, it is possible and supported to migrate from Exchange 2003 to 2010 or keep in coexistence during transition.

    Coexisting with Exchange 2010

    Amit Tank | MVP - Exchange | MCITP:EMA MCSA:M | http://ExchangeShare.WordPress.com
    Wednesday, April 15, 2009 3:56 PM
  • You can also move mailboxes back to 2003 from 2010 if you need to for some unforseen reason. This is great if during coexistence something comes up and you have to back off temporarily.

    Exchange 2003 does not support the "online" mailbox move like 2007 --> 2010 does.
    Wednesday, April 15, 2009 4:08 PM
  • hi,

    and addtion,

    migration and transition is supported from exchange 2003/2007 but in-place upgrade is not supported.

    can not coexist with Exchange 5.5 and Exchange Server 2000.

    regards,
    Exchange - MVP | www.cozumpark.com | www.mumincicek.com
    Saturday, April 25, 2009 2:01 PM
  • hi,

    and addtion,

    migration and transition is supported from exchange 2003/2007 but in-place upgrade is not supported.

    can not coexist with Exchange 5.5 and Exchange Server 2000.

    regards,
    Exchange - MVP | www.cozumpark.com | www.mumincicek.com
    hi Mumin
    At least u must have Exchange 2003 Sp2 or Exchange 2007 Sp2.But Exchange 2007 Sp2 doesn't available for public yet.


    Regards

    Chinthaka | If you think my thread is helpful, Please vote.
    Saturday, April 25, 2009 2:08 PM
  • Hi,

    I have migrated our Serves from Exchange 2003 to Exchange 2010. All mailboxes are now running on Exchange 2010 and Exchange 2003 is not needed.

    I can't find any information to "remove the Exchange 2003 after migrating to Exchange 2010". What are the steps or any link?

    Thanks,

    Sher
    Saturday, January 30, 2010 9:26 AM
  • While I am not aware of an updated article, I do not believe anything has changed since 2007. This page was updated 9/9/2009 for Exchange 2007 SP2.

    http://technet.microsoft.com/en-us/library/bb288905(EXCHG.80).aspx
    Brian Day, Overall Exchange & AD Geek
    MCSA 2000/2003, CCNA
    MCTS: Microsoft Enterprise Server 2010, Configuration
    MCITP: Enterprise Messaging Administrator 2010
    LMNOP
    Saturday, January 30, 2010 4:50 PM
  • I cannot verify this as being the accurate answer but I do know that in a transition from Exchange 2003 to 2007 you would go through the Exchange 2003 uninstall to remove the Exchange 2003 from email service.  Start-up the Exchange 2003 install CD and remove the application.  I assume that this would also apply to the Exchange 2010 transition too.
    Tuesday, April 06, 2010 2:04 PM
  • BTW, I can't find a reference now, but it may be worth mentioning that if you are leapfrogging 2007, you may still want to run the 2007 AD prepare tools, so that if, after installing 2010, you have some need to install Exchange 2007, you can.  Otherwise, you will not be able to.  I am trying to find where I got that, but I cannot.  Anyone please feel free to verify that.
    Friday, June 04, 2010 8:47 PM
  • Hi,

    I have migrated our Serves from Exchange 2003 to Exchange 2010. All mailboxes are now running on Exchange 2010 and Exchange 2003 is not needed.

    I can't find any information to "remove the Exchange 2003 after migrating to Exchange 2010". What are the steps or any link?

    Thanks,

    Sher


    Hi,

    I am planning to migrate our server from Exchange 2003 to Exchange 2010. But i dont know whats is the initial steps need to do?,could you please help me to impliment the migration.

    Thanks,

    Rashid.N

    Wednesday, August 04, 2010 12:42 PM
  • hi,

    if you need it (I know, long time ago :) ) - http://milindn.files.wordpress.com/2010/01/rapid-transition-guide-from-exchange-2003-to-exchange-2010.pdf

     

    awesome guide, for transitioning from 2003 to 2010 and, as they said above, the only way for migration...

    Tuesday, September 07, 2010 12:36 PM
  • Hi Guys,

     

    currently we have 4 Exchange Servers with 4 Domains in the same Forest.

    We have 3 Exchange Server 2003 Ent, 1 Exchange Server 2000.

    Now, we are planning to separate the 4 domains into 4 different forest each has its own DNS and AD.

    Company ACompany BCompany C and Company D

    currently Company A is our parent domain

     

    We will first separate B [currently on Windows 2003 / Exchange 2003 Ent]

    to Windows Server 2008 with Exchange 2010.

    Will ADMT help me on this scenario?

    - move "specific" users from A to B

    - move "specific" computers from A to B

     

    Hope to hear from you soon.. thanks a bunch

    Wednesday, January 26, 2011 5:12 AM
  • This is GOLD right here Tim. Thanks!
    Jason, MCP Comptool Solutions LLC
    Wednesday, September 07, 2011 8:02 PM
  • I know it's an old question but I wrote this a while back and it might help anyone else who stumbles in :)

     
     
    Friday, January 06, 2012 11:27 AM
  • What if you need to revert back to Exchange 2003 once migrated to 2010?  Some clients always want to have a backout plan, just in case.  My guess is that this would not be highly recommended and am hoping that, in fact, industry best practices would dictate that it is not recommended.  Is that the case?  Is there a link or somewhere I could find a full list (or list) of the errors we would expect to encounter if we did have to migrate back to Exchange 2003 from Exchange 2010?  Any and all help would be appreciated.
    Thursday, March 15, 2012 1:37 AM
  • What if you need to revert back to Exchange 2003 once migrated to 2010?  Some clients always want to have a backout plan, just in case.  My guess is that this would not be highly recommended and am hoping that, in fact, industry best practices would dictate that it is not recommended.  Is that the case?  Is there a link or somewhere I could find a full list (or list) of the errors we would expect to encounter if we did have to migrate back to Exchange 2003 from Exchange 2010?  Any and all help would be appreciated.
    I had the same question so I tested it out. I migrated a user to 2010 and migrated back to 2003 with success. Now I'm sure somewhere out there people have had issues, but it suprisingly migrated flowlessly. It is not recommended to migrate back to 2003 but in my case, it did work.

    Jason, MCP Comptool Solutions LLC

    Thursday, March 15, 2012 1:01 PM
  • Thanks, Jason!  That's comforting to some extent.  Was there somewhere where you pre-identified issues that may come up?

    Cheers,

    Josh

    Thursday, March 15, 2012 1:44 PM
  • I know this post is a little bit out of date, but I thought it might be useful for someone who's rearching the topic. A simple and rather cheap migration tool has been recently launched. Supports direct migrations from Exchange 2003 to 2010 and 2013. More info: http://www.codetwo.com/exchange-migration

    Friday, June 14, 2013 8:20 AM
  • The sequence for a migration from Exchange 2003 to Exchange 2010 is as follows:

    1. Bring the Exchange organization to Exchange Native Mode.
    2. Upgrade all Exchange 2003 Servers to Exchange Server 2003 Service Pack 2.
    3. Bring the AD forest and domains to Windows Server 2003 Functional (or higher) levels.
    4. Upgrade at least one Global Catalog domain controller in each AD Site that will house Exchange Server to Windows Server 2003 SP2 or greater.
    5. Prepare a Windows Server 2008 (RTM or R2) x64 edition server for the first Exchange 2010 server.
    6. Install the AD LDIFDE tools on the new Exchange 2010 server (to upgrade the schema).
    7. Install any necessary prerequisites (WWW for CAS server role).
    8. Run setup on the Exchange 2010 server, upgrade the schema, and prepare the forest and domains. (Setup runs all in one step or separate at the command line.)
    9. Install CAS server role servers and configure per 2010 design. Validate functionality.
    10. Transfer OWA, ActiveSync, and Outlook Anywhere traffic to new CAS servers.
    11. Install Hub Transport role and configure per 2010 design.
    12. Transfer inbound and outbound mail traffic to the HT servers.
    13. Install Mailbox servers and configure Databases (DAG if needed).
    14. Create public folder replicas on Exchange 2010 servers using pfmigrate.wsf script, AddReplicatoPFRecursive.ps1,or Exchange 2010 Public Folder tool.
    15. Move mailboxes to Exchange Server 2010 using Move Mailbox Wizard or Powershell.
    16. Rehome the Offline Address Book (OAB) generation server to Exchange Server 2010.
    17. Rehome Public Folder Hierarchy on new Exchange Server 2010 Admin Group.
    18. Transfer all Public Folder Replicas to Exchange Server 2010 Public folder store(s).
    19. Delete Public and Private Information Stores from Exchange 2003 server(s).
    20. Delete Routing Group Connectors to Exchange Server 2003.
    21. Delete Recipient Update Service agreements using ADSIEdit.
    22. Uninstall all Exchange 2003 servers.
    Friday, June 14, 2013 8:45 AM