The document discusses the various phases of embarking on a data center migration/transformation program. It begins by outlining common business drivers for such a program, such as cost reductions, mergers/acquisitions, and regulatory requirements. It then emphasizes the complexity of the task and need to minimize business disruption. Key phases discussed include discovery, planning, design, and implementation. The discovery phase involves assessing the current environment. Planning develops high-level designs and roadmaps. Design creates detailed technical, process, and organizational blueprints. Implementation executes the migration plan. Technical approaches like lift-and-shift, re-platforming, and rebuilding are also summarized.

1. © Copyright 2014 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Embarking on your Data Centre
Migration/Transformation Program
Australian Cloud and Data Centre Strategy Summit 2016
Gus Sabatino – Hewlett Packard Enterprise

2. © Copyright 2014 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
What leads us to embark on such a complicated Journey?
So you have the strategic business case, now what?
• Real estate cost reductions, eliminate leased real estate
• Mergers, Acquisitions
• Consolidation opportunities
• Data Centre facilities themselves are an expensive commodity
• Time to Re-New
• Not meeting regulatory requirements
• IT needs to be scalable
• Move to utility based ‘pay-as-you-go’ services
• Reduce Network Complexity
• Releasing Trapped Compute

3. © Copyright 2014 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Embarking on your Data Centre Migration/Transformation Program
Don’t underestimate its complexity
The question is not
“How do I relocate the Network, Servers, Apps and Data?”
but instead…
“How do I relocate the business, keep it
operational and incident free during the
relocation?”
The critical success criterion will be to complete the change without anybody
in the business and the user community realizing it has happened.

4. © Copyright 2014 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
The Big Rules
Rule # 1- Be clear about the business objectives
These should flow from the Strategy and Business Case that got us here.
Make sure they are realisable (align to SMART principle).
Rule #2 - A Data Centre Migration programme is a joint programme between
the Business, IT, Customers, Clients and Partners. It simply can not be ‘delegated’.
Without full engagement the only guarantee is failure.
Rule #3 - People – Ensure that you onboard a team of data center experts
which have done Data Centre migrations before. Technical experience and the ability to
manage the interactions competently is absolutely fundamental.
Don’t just give it a go – If you feel you need help, get it!

5. © Copyright 2014 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
• The Business
• Real Estate
• Facilities Engineering
• Finance
• Security
• Operations
• Disaster Recovery
• Networks
• Capacity & Availability
• Applications Support
• Apps Users
• Server Technology Towers
• Storage Services
• Cloud Services
• Service Desk
• End Users
• Service Management
• Incident and Problem Management
Who should we engage? Stakeholders
Stakeholders
• You must clearly understand who your stakeholders are
– Engage every single one
– Make them part and integral to the program – this ensures success!
– Missing a stakeholder is like buying a bike without wheels
Stakeholders could be from …

6. © Copyright 2014 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Where should we start? The Core Team
Assembling the Core Team
• Appoint a Project Sponsor
– Ideally from the Business if not possible, from IT
• Members of the team
– Business representative
– Members of IT
•CIO, Head of Infrastructure, Head of Networks, Head of Apps
•Representative of the User Community
– Head of Facilities/Real Estate
– Procurement
– Finance
– Program Manager

7. © Copyright 2014 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Forming the ‘Elite’ Program Team – Success Starts here!
Building a team for success - Resources
Ensure that you onboard a team which have done it before.
– Be prepared to backfill current knowledgeable resources
• You will need:
– Program Manager
– End to end Architect
– Technical Transformation Leads
– A Program Delivery Champion,
•Organisation Engagement, Cultural Diversity
– Program Problem Manager
• Financials
– Account for Travel Costs
– Project overheads, typical 10-15%, additional management support and governance

8. © Copyright 2014 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Forming the ‘Elite’ Program Team
Building a team for success – Structure and Governance
– Dedicated Project Managers per packet of work
• Application, Network, Technology – Servers, Storage, Virtual/Cloud
– A Strong PMO
• Steering Committees
• Communication Plans
• Program and Status Reporting
– A Change Control Champion aligned to the PMO responsible for
• Business Change & Operational Change
• Process Change
• Don’t under estimate scope change / scope creep
– Engagement
• Engage with your Suppliers, Third Party Support Organisations, Vendors,
Partner, Clients and Customers early

9. © Copyright 2014 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
The ‘Kick Off’Starting the Journey -
Bringing the Team together – The ‘Kick Off’
• You must make the project real to the team and each team member
– Introduce the initiative, the objectives and benefits
– Introduce and obtain endorsement of the timeline
– Make the team integral to the program success
– Set the expectations
– Make the program one of the performance objectives, it will ensure
team members have an incentive. Reward performance
It will not be a success without them!
The Kick 0ff Goal,
Engagement, commitment and desire to succeed with a;
‘Gut Wrenching’, ‘Fire in the Belly’ and ‘Tenacity’ to be the best!

10. © Copyright 2014 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Data Centre Migration Programme - The Phases
Implement
Discovery Plan Design Implement Run
Gate 1
Approval
Gate 2
Approval
Gate 3
Approval
Top Down Discovery Execute Detailed
Migration Plan
Bottom up DiscoveryCMO Data Gathering

11. © Copyright 2014 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
The Phases in Detail - Discovery
Implement
Activities Deliverables Resources Others
•CMO Data Gathering
•Client Current State, Apps,
Assets, Users
•BA’s
•Technical Resources
•Discovery Workshops
•Inventory servers, storage,
applications, network,
contracts, financials
•PM’s
•Solution Architects
•Tools
•Site Discovery •CI Interdependencies •Methods
•Consolidation Strategy &
Roadmap
•Customers
•Users
•High level Business Case
•Plan Next Steps
The Discovery Phase sets the basis for success by determining your current state, your strategic objectives and
tactical consolidation / relocation roadmap.

12. © Copyright 2014 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
The Phases in Detail - Plan
Implement
Activities Deliverables Resources Others
•Top Down Discovery
•Site Assessments
•Detailed Inventory & SLA
Analysis
•PM’s
•BA’s
•Interviews
•Initial Scope Statement
•Statement of Requirements
•Draft Solution Blueprint
•Solution Architects
•Technical Resources
•Finance Support
•High Level Designs
•Organizational, IT Process &
Technical Designs
•Transition Strategy
•Methods
•Tools
•Investment Justifications
•Rapid Opportunity
Analysis
•Cost Model
•Statement of Work
•Approve and Plan Next Steps
The Plan phase includes the high level design, the consolidation and relocation roadmap, and the validation that
the design meets the specified requirements.
Gate 1
Approval

13. © Copyright 2014 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
The Phases in Detail - Design
Implement
Activities Deliverables Resources Others
•Bottom up Discovery
•Detailed Designs
•Detailed Technical,
Organisation and Process
Solution Blueprints
•(Temporary State
•(Future State)
•PM’s
•BA’s
•Solution Architects
•Technical Resources
•Third Parties
•Financial Models
•Cost Model
•HW/SW Bill of Materials
•Finance Support
•Implementation
Planning
•Detailed Migration Plan
•Deployment, Test and
Acceptance Plans
•DR and Strategic Test Plans
•Cutover and Transition Plans
•Methods
•Tools
•Approve and Plan Next Steps
The Design phase is where the technical solution including facilities, servers, applications, network as well as
potential organizational and process designs are created and documented
Gate 2
Approval

14. © Copyright 2014 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Data Centre Migration Programme - Technical Approaches
Migration Method Benefits Disadvantages
Lift and Shift • Technically the easiest
• No fallback plan if equipment does not travel well
• Need significant downtime
• Still need to transform at end of life
• Additional data Centre space required
Lift and Shift with
Swing Kit
• Can test before cutover
• Fall-back plan - less risk
• May need to rebuild applications/databases
• Equipment hire cost
• 2 stage process
• Still need to transform at end of life
Re-platform
(multiple flavours)
• Can test before cutover
• One stop process
• Fall-back plan - less risk
• Refreshed equipment and O/S - options available for Utility
or Cloud Services
• Can virtualise to reduce numbers of servers
• Can consider applications consolidation at same time
• Applications may need remediation if legacy
• May need to rebuild applications/databases
Rebuild
• This is where you just provide new kit in the target DC and
completely, from the ground up, rebuild the app.
• Used when moving work into the “cloud” and when
organisations want to re-platform or upgrade the
application to a new version.
• High risk as you are making 2 changes at the same time.
• Clear R&R between what we do and what the client
does.

15. © Copyright 2014 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
The Phases in Detail - Implement
Implement
Activities Deliverables Resources Others
•Execute Detailed
Migration Plan
•Detailed Technical,
organisational and IT
changes implemented
•PM’s
•BA’s
•Solution Architects
•Build and Test
•Build Target environment
•System and Acceptance
Testing
•Technical Resources
•Third Parties
•Customers
•Release to Production
•Production Handover
documentation, training, KB
•Cutover Legacy Systems and
Infrastructure, Processes,
and Organisation
•Plan for Risk Mitigation and
Contingency
•Cutover and Acceptance
•Users
•Methods
•Tools
The Implementation Phase includes the deployment and acceptance of technical solutions, IT organizational
changes and IT process changes.
Gate 3
Approval

16. © Copyright 2014 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
The Phases in Detail - RUN
Implement
Activities Deliverables Resources Others
•Transition to BAU
•Transition Operations
and Support
•Decommission Legacy
systems and
infrastructure
•PM’s
•BA’s
•Technical Resources
•Third Parties
•Customers
•Monitor
•Monitor Results
•Identify other
improvement
opportunities
•Users
•Tools
•Methods
•Documentation
The Run Phase includes the transition to on-going operations, and retirement of infrastructure and services that
have been replaced
Run

17. © Copyright 2014 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Data Centre Migration Planning - Risks
Risks
Lack of buy-in and Support from Business Units, Clients and Customers
Communication breakdown with Stakeholders – Resource constraints, conflict etc.
Resource availability – Resources not dedicated to the project or not available to recruit
Latency between Network, Sites , Applications and end user community – Performance Issues
Insufficient Data Discovery , incomplete inventory, mapping of CI’s and interdependencies
Availability of legacy equipment – When performing lift and shift, legacy equipment may no longer be available
Risk of shutting down equipment - can result if failed re-start of parts such as HDD’s, RAM, CPU’s
Obtaining consensus – Due to many DC Migration strategies and
Appropriate cutover - timeframe approach (progressive, big bang)

18. © Copyright 2014 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
To be continued…
You’ve started the Journey, now take the dive!

19. Thank you Gus Sabatino
gus.sabatino@hpe.com

20. © Copyright 2014 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
BACK UP SLIDES - NOTES

21. © Copyright 2014 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
BACK UP SLIDES - NOTES

22. © Copyright 2014 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
BACK UP SLIDES - NOTES

23. © Copyright 2014 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
BACK UP SLIDES - NOTES