Blog Post

Exchange Team Blog
1 MIN READ

Exchange 2007 reaches end of life on April 11th. What’s your plan to move?

The_Exchange_Team's avatar
The_Exchange_Team
Icon for Microsoft rankMicrosoft
Feb 27, 2017

On April 11, 2017, Exchange Server 2007 will reach End of Life. If you haven’t already begun your migration from Exchange 2007 to Office 365 or Exchange 2016, you need to start planning now. End of life means that Microsoft will no longer provide the following for Exchange 2007:

  • Free or paid assisted support (including custom support agreements)
  • Bug fixes for issues that are discovered and that may impact the stability and usability of the server
  • Security fixes for vulnerabilities that are discovered and that may make the server vulnerable to security breaches
  • Time zone updates
Your installation of Exchange 2007 will continue to run after this date. However, because of the changes listed above, we strongly recommend that you migrate from Exchange 2007 as soon as possible. To learn about your options for migrating from Exchange 2007 to Office 365 or a newer version of Exchange Server, check out Exchange 2007 End of Life Roadmap. If you have other Office 2007 servers or clients, such as SharePoint Server 2007, PerformancePoint Server 2007, Office Communications Server, Project Server 2007, or Office 2007 client applications, check out Resources to help you upgrade from Office 2007 servers and clients for information about their end of life dates and upgrade options.

Exchange Team

Updated Jul 01, 2019
Version 2.0
Exchange 2007
on premises
Planning and Architecture
  • Deleted's avatar
    Deleted
    Mar 10, 2017
    Luckily I've already managed to move from Exchange Server 2007 to 2013 a few months ago, but it was a big change for our small organisation (about 125 seats, single server). The web-based management interface takes time to learn. Procedures that used to work (e.g. powershell stuff) needed testing and tweaking. Lot of problems initially with disk space due to excessive logging; I've had to write a script to run daily as a scheduled task to clean out unwanted log files (that took a while to write, test and tune). The mail queue database also hogging disk space has needed occasional maintenance. Are we better off than before? Probably, but the cost to get from (A) to (B) was considerable.
    • Deleted's avatar
      Deleted
      Mar 10, 2017
      Have you got numbers on how much disk space you needed for the log and mail queue volumes going from 07 to 13?
  • Deleted's avatar
    Deleted
    Mar 28, 2017
    I plan to upgrade to Exchange Server 2010 because 2013 and 2016 has less features. In 2013 removed EMC and 2016 not run Edge filtering and antispam in Windows Server 2016. Also the user interface and experience in OWA on 2013 and 2016 version are terrible ugly and a nightmare experience. One color, or two, flat design, lack of constrast, big texts, big and a lot of blank spaces, terrible.

    All seems to be that Microsoft no longer want our customers to continue using Exchange Server, maybe in order to suscribe to Exchange Cloud Services, but never do that in my life.

  • Deleted's avatar
    Deleted
    Mar 29, 2017
    We recently upgraded from 2007 to 2013 but find various issues that cannot be done via the 2013 GUI. It appears these issues remain in Exchange 2016. Is there any place to submit feedback to the Exchange team?

    One of my big issues is the fact that we use groups when delegating permissions but for some unexplained reason the EAC does not allow you to delegate groups to an object for full access, send as, etc. We have to resort to Powershell to perform this one task. Why??