Migration Process (Office Communications Server 2007 Migration)

Lync Server 2010

Topic Last Modified: 2011-04-06

The recommended and supported migration procedure for Microsoft Lync Server 2010 is the side-by-side migration procedure. This section includes information about why you should use side-by-side migration, in addition to information about coexistence and an alternate migration method.

In nearly every migration, you should use the side-by-side migration path. In a side-by-side migration, you deploy a new server with Lync Server 2010 alongside a corresponding server that is running Office Communications Server 2007, and then you transfer operations to the new server. If it becomes necessary to roll back to Office Communications Server 2007, you have only to shift operations back to the original servers. Be aware that in this situation, any new meetings scheduled with upgraded clients will not work, and the clients would also need to be downgraded.

After you deploy Lync Server 2010 in parallel with Office Communications Server 2007, the topology represents a coexistence testing state of the two deployments. Before you migrate to Lync Server 2010, it is important to test both deployments and ensure that services are started, you can administer each site, and clients can communicate with current and legacy users. Prior to migrating all users in Phase 7: Move from Pilot Stack Deployment to Production (Office Communications Server 2007 Migration), you should understand the state of each deployment and ensure that each deployment is functional and working properly. Typically, this coexistence testing phase exists throughout the pilot testing of Lync Server 2010. Legacy users are moved to Lync Server 2010 for a period of time to ensure that application compatibility and features and functions are working properly. After pilot testing, users and applications are moved to the production version of Lync Server 2010, and the legacy pools and applications of Office Communications Server 2007 are retired.