Migrating from Hosted Exchange 2007 to Hosted Exchange 2010 SP1
implement.com has recently completed a project for Microsoft to develop guidance on how to migrate from Hosted Exchange 2007 (and HMC) to Hosted Exchange 2010 SP1. The guidance can be downloaded from this blog:
This guidance provides planning content along with detailed step by step instructions and scripts to complete the migration. It is a complex migration, made much more so by the requirement to create a new Active Directory Forest when deploying Hosted Exchange 2010 SP1. I won't go into too many details here, as the guide also includes a gap analysis that highlights the many planning considerations for deploying this latest release.
One major item to keep in mind is that this release of Exchange 2010 SP1 includes native support for multi-tenancy, and there is no longer a separate solution from Microsoft to support hosting. Previously, Microsoft released the Hosted Messaging and Collaboration Solution (HMC) to provide support for hosting on Exchange 2007, including a provisioning automation engine called Microsoft Provisioning System (MPS). With HMC and MPS gone, service providers that relied on these tools and guidance need to look to Exchange 2010 SP1 Hosting native multi-tenancy capabilities and the powershell interface for provisioning.
There are still numerous gaps beyond what is native in the product and what it will take to deploy a hosted service. It is the responsibility of the service provider to fill these gaps. Systems Integrators like implement.com and ISVs that produce the control panel and automation solutions can help the service provider to fill these gaps. For the last couple of years, as Microsoft has been planning for this release, implement.com has also been preparing for this transition. The graphic below highlights this "solution gap" as we call it and we first created this graphic and started sharing with clients in the fall of 2008. "Wave 14" refers to the released or soon to be released suite of products that include Exchange 2010, SharePoint 2010, CRM 2011, and Lync Server 2010.
The gap includes basic provisioning functionality such as plans and resource management across a suite of products, billing, service orchestration (the nuts and bolts of creating the objects related to a plan that might include multiple services).
Another important item is that the new multi-tenant model delivered by Hosted Exchange 2010 SP1 does a nice job of providing isolation of tenants in Active Directory and we have performed the preliminary testing and guidance for SharePoint 2010 and Office Communications Server 2007 R2 to leverage the Exchange 2010 SP1 tenant model. I actually look at this not as the new Exchange 2010 tenant model, but really, the new Microsoft multi-tenant model for service providers that can be leveraged by all products. We are doing our best to get this feedback to Microsoft to make sure products like Lync leverage this model as well.
implement.com Corporation is very prepared to work with service providers and their ISVs to migrate from Hosted Exchange 2007 to Hosted Exchange 2010 and we have packaged up an initial phase of a typical project into a planning workshop.
Service Package for Migrating from Hosted Exchange 2007 to Hosted Exchange 2010