The document outlines a client's project to migrate their tier 1 enterprise applications and infrastructure services from an existing data center to a new data center. It discusses the key tasks of determining what applications need to migrate, managing stakeholders and vendors, and creating tools to manage the migration. It then presents and analyzes four options for performing the migration - "forklift", "build new", "virtualize", and "serial number swap" - weighing the risks, impacts, costs, and resources required for each. It concludes by outlining the consultant's process for planning and executing the migration through a "playbook" approach.

1. DATA CENTER MIGRATION Jan 2009

2. Overview Project Scope We are assisting our client with the build out a new data center. As part of that effort all tier 1 enterprise applications and supporting infrastructure services will need to migrate to the new data center. Specified Task Move all tier 1 enterprise and infrastructure application to the new data center. Implied Tasks Determine the list of application for migration Stakeholder Management Vendor Management Create tools to manage and gather data Change Management Operational Improvements

3. Migration Options Forklift: Physically move servers from the old to the new location. (High Risk, Moderate Cost) Build New: Install newly purchased hardware in the new DC, install applications, migrate data over a WAN connection. As available, leverage planned new system implementation and hardware refresh projects to fund new equipment purchases. (Low Risk, High Cost)

4. Migration Options Virtualize: Convert physical servers to virtual, then move the virtual servers to the new location over a WAN connection. (Low Risk, Moderate Cost, Does not work for some systems) Serial Number Swap: Rent servers that exactly match the configuration of existing servers and place in the new DC. Install applications on rented equipment, migrate data over a WAN connection. Return original equipment to rental agency. Swap ownership and maintenance agreements between original and rented equipment. (Low Risk, Moderate Cost)

5. Migration Options Forklift Serial Number Swap Build New Virtualize Risk HIGH LOW LOW LOW Customer Impact MED LOW LOW LOW Cost LOW MED HIGH LOW Resources HIGH MED MED MED

6. Our Process - The Playbook Define Move Teams Application Profile Migration Process Flow Effort Estimates Server plan Data Plan Timeline

7. Knows and Knows Not If you know it and know you know it; it is fact document it, it may be a requirement. Establish the move approach and the risks associated for each system with the business owner. Clearly communicate the business case behind this project to all involved, especially skeptical business units. Make sure everyone understands why this has to be done.

8. Knows and Knows Not If you know it and don’t realize you know it; then it is fact or information by experience. Often seen as “a technical” project the business units are not directly involved or not involved early enough. Code Remediation- any hard-coded host names or IP addresses need to be changed in the code of the apps. Set a plan to assess the impact and to manage this risk.

9. Knows and Knows Not If you don’t know it and don’t know you don’t know it; ignorance is bliss and it’s in fate’s hand. The client will most likely NOT have all the operational procedures they will need in the new data center. Determining these processes should be a part of the scope. Just because the clients owns a tool or technology don’t assume the know how to use it. (i.e.. EMC replication, VMware etc.)

10. Knows and Knows Not If you don’t know it and know you don’t know it; you need to ask questions! Ensure that management sets this project high enough on the priority list that you have the attention and support of key resources, particularly tech support teams. Do not assume that the company knows what applications and servers it has. The inventory needs to be accurate to succeed.

11. Beware the FUD (Fear, Uncertainty, and Doubt) I don’t have the resources to move my application How is it going to be supported. Its working fine right now, why do we need to move.