Make the Decision to Upgrade to MS Exchange 2010

Rock the enterprise email boat with care.


Your Challenge

  • Email vendors release significant platform upgrades more often than organizations need to upgrade, creating pressure to upgrade twice as frequently as upgrades are really warranted.
  • In addition to new features, significant changes to infrastructure and new deployment options often accompany new releases, complicating the upgrade decision.
  • This solution set will help organizations understand new features, new infrastructure requirements, and changes in delivery methods to assess upgrading.

Our Advice

Critical Insight

  • Email platforms require significant infrastructure investments. ROI is rarely achieved in the typical vendor product lifecycle of three years. Being one version "behind" for a few years is not a bad thing.
  • New features alone don't warrant an upgrade each time a new email platform version is released. Instead, factors like discontinued support and lack of integration with other applications/systems should be key upgrade considerations.
  • Emerging alternative delivery options, such as software as a service (SaaS), are game changers in the email market and can be key upgrade factors.

Impact and Result

  • Understand the new features in Exchange 2010 and how these may improve operational efficiency and lower operational costs.
  • Identify opportunities for leapfrogging to Exchange 2010 from Exchange 2003, passing over Exchange 2007, to ensure longevity of the upgrade decision and maximize ROI.
  • Select the appropriate and cost effective delivery option by comparing the different TCOs of the available delivery options, over the expected lifetime of the platform.

Get the Complete Storyboard

See how all the steps you need to take come together, with tools and advice to help with each task on your list.

Download Now

Get to Action

  1. Get the whole picture

    Determine when an upgrade is needed.

  2. Assess the features and functions found in newer versions

    Decide if they are appropriate for the organization at this time.

  3. Identify the infrastructure requirements of newer versions

    Gauge the additional costs of upgrading, beyond just software licensing.

  4. Choose a delivery method

    Compare the TCO of available deployment options, such as on-premise, on-demand/SaaS and traditional hosting, and select the most cost-effective solution.

  5. Evaluate the upgrade paths

    Choose the optimal upgrade path for the organization.

Guided Implementation Icon Talk to an Analyst

Our analyst calls are focused on helping our members use the research we produce, and our experts will guide you to successful project completion.

  • Book an Analyst Call on this topic. You can start as early as tomorrow morning. Our analysts will explain the process in your first call.
  • Get advice from a subject matter expert. Each call will focus on explaining the material and helping you to plan your project, interpret and analyze the results of each project step, and setting the direction for your next project step.

Schedule Your First Call


GET HELP Contact Us
×
VL Methodology