Migrating Exchange 2003 straight to Exchange 2013

Migrate Exchange 2003 straight to Exchange 2013

Moving from Exchange 2003 to Exchange 2013 – bottom line

For system administrators time is essential, especially when migrating Exchange. Moving data fast, properly and smoothly is a dream. Double hop migration can turn that dream into a nightmare, whereas exporting/importing PST files across forests doesn’t work in large companies. Therefore, it is always worthwhile to check for alternatives just like the CodeTwo migration tools.

Learn more about CodeTwo Exchange Migration

Want to migrate to Office 365? Try CodeTwo Office 365 Migration.


Recommended articles

How to effectively schedule a meeting with Scheduling Poll (formerly FindTime) in Outlook?
January 29, 2025

How to effectively schedule a meeting with Scheduling Poll (formerly FindTime) in Outlook?

Tired of back-and-forth emails when scheduling meetings? Scheduling Poll for the rescue!
How to delay sending an email in Outlook
January 23, 2025

How to delay sending an email in Outlook

Outlook lets you delay sending an email. See exactly how it works and how to do it.
What are customer satisfaction surveys?
September 24, 2024

What are customer satisfaction surveys?

Email surveys can be a great tool for gathering customer feedback. Check out 6 most effective email survey examples.

Comments

    • If I understand you correctly, you want to migrate Exchange 2003 to 2013 to a different forest but without changing your domain?
      I’m afraid this scenario won’t work. When migrating Exchange 2003 to 2013/2016, I can recommend CodeTwo Exchange Migration in cross-forest, cross-domain scenario.

  1. avatar
    DavidC_Surrey says:

    I really don’t see the point of this. It is no different from migrating to 2010 and then on to 2016 because your software does not allow 2003 to 2016 in one hop on the same domain. Someone needs to produce software that will take an offline backup of 200x and allow you to uninstall your 200x, install 2016 and then restore the mailboxes from the offline backup or better still the .EDB file copied from the original server. Why has nobody done this? It would save so much time and money.

    • avatar
      Kamil Glaser says:

      Hi David,
      Our migration software has helped many companies save time and resources in many different scenarios, especially in cross-domain migration. Thanks to CodeTwo Exchange Migration, they were able to perform a quick and secure data migration without double hopping and with zero downtime for users. Nonetheless, thank you for your opinion, our developers will take it into account while working on the new versions of the program.
      Apart from that, you can use CodeTwo Backup to create an offline backup of your mailboxes and then restore them, just like you specified in your comment.

  2. Dear codetwo team,

    thanks, appreciable tool.

    can you please tell me the pre-requisites for migration of ex 2k3 to 2k13.

    thanks
    Akim

  3. Hi

    I was able to transfer mailboxes successfully using your product but can you tell me how to setup outlook after migration? Im getting this error when i tried to add the account with the new domain name “The set of folders cannot be Opened. You must connect to Microsoft Exchange with the current profile before you can synchronize your folders with your Outlook data file (.ost)”

  4. avatar
    Adam the 32-bit Aardvark says:

    Hi Andrew,

    If you need to keep your existing local domain, the steps you mentioned seem to be correct.

    CodeTwo Exchange Migration could help you with the Exchange 2003 to 2016 cross-forest move. Service availability would not be affected, because our product only copies data to the target server. The only time users may “feel” the migration is when you switch your MX records to the new server.

    Hope this helps,
    Adam

  5. Hi,

    looks like a very interesting product.

    We are looking to migrate our Exchange server from 2003 to 2016. I m aware they both cannot coexist on the same domain.

    Would i therefore have to create a new domain for the exchange server, remove old server from current domain, then add new exchange server to domain?

    If so, i’m guessing that users will not be able to send/receive email untill this has been completed?

  6. hi dear friends,
    first i am sorry about my bad english.
    i will migrate my exchange 2007 server to 2013 exchange
    and after migration all users will have this message:
    your mail boxes moved to 2013 exchange or something like,
    how can i make this process?which tool i have to use
    thanks

  7. Used your product to migrate from Exchange 2003 to Exchange 2013. Had a few issues but am generally satisfied with the data move. However, the destination server reports the mailbox versions as being Exchange 2003, not Exchange 2013. Therefore, Role Assignments are not possible, which causes a number of problems. Now that the old server is gone, what can be done to “promote” or upgrade the mailbox versions?

  8. Hi Tomasz!

    My forest is forest.com, and my exchange 2003 server is located in domain1.forest.com. Can I install exchange 2013 at the root level, forest.com? Or do I need to create a new root level, forest2.com and then install exchange 2013?

    Thanks.

  9. Hi All

    I’m currently in a process to migrate WS 2003 to 2012, from AD, Files, Exchange and user redirections. Is there anything very important to know about except what has been mentioned above?
    or a website can help a me through the process?

  10. avatar
    Tomasz Majocha says:

    HI,

    @Don J – it is really hard to tell as the migration process relies on many factors, such as quality of your Internet connection (in the case of a migration to a different network), your local router throttling, source and target server throttling, performance of the computers involved etc. Our program does not affect the speed you already have at disposal in your environment.

    @Francesco Pellegrini – I am not entirely sure what do you mean by asking about customers that are not using Microsoft Exchange. Most probably, just as you pointed out, they have their own paths of migration and upgrading their non-Exchange environments. The article covers MS Exchange migration.

  11. avatar
    Francesco Pellegrini says:

    What happens to those customers who decided to stay away from Microsoft Exchange?
    Upgrading a Lotus Domino R5 server to IBM Domino 9 takes 15 minutes.
    Launch installer, click, click, click… done.
    Restart server and tell users to connect.
    Just my two cents abut the meaning of “value” for customers and not for vendors…
    Cheers

  12. Microsoft offers coexistence with Exchange 2013 SP1. Check it out. Still no direct path from 2003 to 2013. You must still stage it with 2010 or use 3rd party tool.

  13. avatar
    Tomasz Majocha says:

    Hi Andrea!

    Microsoft does not support coexistence scenario between Exchange 2013 and Exchange 2003 (and older) unfortunately.
    When migrating the process requires creating a new, separate domain on Exchange 2013.

  14. avatar
    Andrea Rigoni says:

    Hello,
    I’m very interested to your product “CodeTwo Exchange Migration.” to migrate from Exchange 2003 to Exchange 2013 directly, without intermediate steps.
    I have a question for you: How should I do when I receive this error message from Exchange 2013 setup:
    “One or more servers in the existing organization are running Exchange Server 2000 or Exchange Server 2003.Installation can’t proceed until all Exchange 2000/2003 servers are removed”?

    Waiting for your reply.
    Best Regards.
    Ps.:I have more than 200 mailboxes.

Leave a Reply

Your email address will not be published.

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>

*

CodeTwo sp. z o.o. sp. k. is a controller of your personal data.
See our Privacy Policy to learn more.