T2 Tech Group's proven methodology helps organizations migrate applications during a data center relocation. The strategy uses a best-practices approach to efficiently coordinate the following phases of a move: the perquisite stage, mock migration, failover testing, implementation and go-live, and project closeout. Using this approach to coordinate an application migration allows teams to efficiently build a solid application strategy; validate the strategy through testing; and go-live with minimal business interruption, a minimized project cost, and an optimal result.
Application migration process presentation by t2 tech group
1. A Five-step Methodology for
Application Migration
A BEST-PRACTICES APPROACH TO MIGRATING
APPLICATIONS TO AN ADVANCED COMPUTING
PLATFORM
2.
3. Initial Migration Assessment
1. Conduct server inventory and
application mapping
2. Define applications groups
3. Determine migration scheduling
and effort assessment
4. Category Server Application Environment OS Location RAM CPU
Server mnrmpapp1 Risk Monitor Pro Live Win2008 R2 Ent (32 bit) Main Building 8 4
Server mnrmpapp2 Risk Monitor Pro Live Win2008 R2 Ent (32 bit) Main Building 8 4
Server mnrmpsql1 Risk Monitor Pro Live Win2012 R2 Ent (64 bit) Main Building 16 4
Server mnrmpsql2 Risk Monitor Pro Live Win2012 R2 Ent (64 bit) DRBuilding 16 4
Server mnrmpapp1t Risk Monitor Pro Nonprod Win2008 R2 Ent (32 bit) Main Building 8 2
Server mnrmpsql1t Risk Monitor Pro Nonprod Win2012 R2 Ent (64 bit) Main Building 8 2
Appliance mnvrop1 vRealize Live SUSEEnterprise Linux Main Building 8 4
Server mnpxpsv1 Pyxis Supply Live Win2012 R2 Ent (64 bit) Main Building 8 4
Server mnpxpsv2 Pyxis Supply Live Win2012 R2 Ent (64 bit) Main Building 8 4
Server mnpxpsv1t Pyxis Supply Nonprod Win2012 R2 Ent (64 bit) Main Building 4 2
Server mnpxpsv2t Pyxis Supply Nonprod Win2012 R2 Ent (64 bit) Main Building 4 2
Server mndoseweb1 Intellidose Live Win2008 R2 Ent (64 bit) Main Building 4 2
Server mndoseweb1t Intellidose Nonprod Win2008 R2 Ent (64 bit) Main Building 4 2
Server mndosesql1 Intellidose Live Win2008 R2 Ent (64 bit) Main Building 16 4
Server mndosesql2 Intellidose Live Win2008 R2 Ent (64 bit) DRBuilding 16 4
Server mnfetaibus1 FetaLink Live RedHat 7 Main Building 8 4
Server mnfetaibus2 FetaLink Live RedHat 7 Main Building 8 4
Server mnfetaibus1t FetaLink Nonprod RedHat 7 Main Building 4 2
Server mnmuseapp1 GEMuse Live Win2012 R2 Ent (64 bit) Main Building 8 4
Server mnmuseapp2 GEMuse Live Win2012 R2 Ent (64 bit) Main Building 8 4
Server mnmuseapp3 GEMuse Live Win2012 R2 Ent (64 bit) Main Building 8 4
Server mnmusesql1 GEMuse Live Win2012 R2 Ent (64 bit) Main Building 16 4
Server mnmusesql2 GEMuse Live Win2012 R2 Ent (64 bit) DRBuilding 16 4
Server mnmdctapp1 Medicity Live Win2003 R2 Ent (64 bit) Main Building 8 4
Server mnmdctapp2 Medicity Live Win2003 R2 Ent (64 bit) Main Building 8 4
Server mnmdctint1 Medicity Live Win2003 R2 Ent (64 bit) Main Building 8 4
Server mnmdctint2 Medicity Live Win2003 R2 Ent (64 bit) Main Building 8 4
Server mnmdctsql1 Medicity Live Win2008 R2 Ent (64 bit) Main Building 16 4
Server mnmdctsql2 Medicity Live Win2008 R2 Ent (64 bit) DRBulding 16 4
Server mnisirapp01 iSirona Live Win2008 R2 Ent (64 bit) Main Building 8 4
Server mnisirapp01t iSirona Nonprod Win2012 R2 Ent (64 bit) Main Building 4 2
Server Inventory & Application Mapping
Complete server
inventory
Complete application
discovery
Conduct infrastructure
interviews to determine
associated application
data
Map server to
application
5. Define Applications Groups
• Application function/purpose
• Cost analysis
• User base
• Clinical/non-clinical
• Application support team
• Integration complexity/dependencies
Sequence Application Name Application Function / Purpose Clinical / Non Clinical Tier User Count Current OS Application Lead Infrastructure Lead
Group 1 ClickStudio Password Storing Non-Clinical Low 50 2012 Andy Anderson Alex Patel
Group 1 GEMUSE(EKG) Cardiology EMR Clinical Medium 1739 2008 Terrell Davin Amy Carroll
Group 1 Risk Monitor Pro Risk management Clinical Medium 5000 2008 Jason Thomas Brad Schneider
Group 1 Source One Email Archiving Non-Clinical Low 100 2008 Jake Jones Janet Bennett
Group 2 Intellidose Ambulatory Oncology Clinical Medium 40 2008 Matthew Easley Kerry Johnson
Group 2 Pyxis Pharmacy / Medication Dispensing Clinical Critical 3870 2003/ 2008 Kristtina Tomlinson Ron Rogers
Group 2 iSirona DeviceConX Device Integration Clinical Critical 600 2008 Hector Warner Ryan Nguyen
Group 2 PulseCheck, Ibex Emergency Department EMR Clinical Critical 2500 2003/ 2008 Antje Smith Jasson Garrett
9. Discovery Document
• Create standard
documentation for each
application
Application and infrastructure
leads
User base
Criticality
Authentication
Back-up strategy
Application interdependencies
Interface requirements
Current and future server
information
Required database features
Application delivery method
10. Architecture Diagram
• Identify new IP’s
• Identify all servers by
naming standards
• Identify port communication
for network design
• Identify core service
dependencies
11. Application Migration Process Flow
• Document sequence of
steps
• Document party(s)
responsible
• Document steps to be
performed
12. Secure External Resources (If Required)
• Estimate and secure
required labor/vendor
assistance
• Vendor resource
assistance
• Create and validate
migration SOW with
vendor
• Negotiate quote
• Issue PO request and
tracking
• Perform best practices for
vendor management
13.
14. Application:
Name/ Role:
Test Patient:
Duration to Result Validation Expected Result/ Duration
30 secs Launch Intellidose via Citrix Application login screen loads
10 secs
Enter admin/ clinical staff/ provider username &
password
Username & password input accepted in their respective fields
10 secs Click login
Intellidose accepts valid username & password and loads
patient search page
10 secs Working patient list
Working patient list automatically displays on left of patient
search after successful login
10 secs
Cosigner's queue
Cosigner's queue automatically displays below working patient
list after successful login
30 secs
Search current patient (on Allscripts
schedule/ current appointment) by Last/ First Name, Current patient displays and is selectable
10 secs Select/ double-click patient Opens patient chart and patient displays in working patient list
10 secs Validate patient demographics Patient demographics, under general tab, should mirror EHR
5 min Validate allergies/ medication
Patient's allergies and current, inactive and med Hx to display
under allergies/ medication tab
1 min Validate active problems Patient's active problems from EHRto display under problem
1 min Validate social history Patient's social history from EHRto display under social history
1 min Validate family history Patient's family history from EHRto display under family history
1 min
Validate past medical history
Patient's past medical history from EHRto display under past
med history tab
1 min Validate diagnosis Patient's Dx from EHRto display under Dx 1 tab
5 mins Validate lab results from EHR Patient's lab results from EHRto display under tests tab
2 min Validate vital signs Patient's vitals correctly listed under Metrics tab
10 mins Provider writes an order/ plan & signs off on it
Pre-built and customized treatment plans can be applied to
patients Tx plan
Document nurse's visit Nurse follows provider, documents visit (nurse's note)
Validate document transfer to EHR
Chemo order and nurse's note successfully populate in EHR
(.PDF format) under Hem/ Onc chart section. Correctly labeled
as Instrinsiq Chemo Orders and Instrinsiq Nurses Notes
30 min Modify existing treatment plan Treatment plans editable
5 min
Run sample report
Ability to run drug utilization, tumor registry, practice statistics,
patient status and operational reports
1 min Verify printing: record summary Printers displayed from Citrix session and documents print
Intellidose
Jim Baker; Clinical Analyst
Int Test1
Mock Migration
1.Create application
migration playbook
2.Replicate server and
storage
3.Test application using test
scripts
4.Test load balancing and
high availability, if requiredID Task Name Resource Location Duration
Planned Start
Time Notes Complete
Backed
Out
Actual
Start Time
Actual
Finish
Actual
Duration Start Delta
Duration
Delta
Pre-test steps 2.40 hours
Failover Start Time 10:00
0 Go / No Go Discussion All 5 10:00
1 Stop services, email, HL7, alert, auto report Vendor 1 Current Application Server 5 10:05
2 Stop app pool (IIS) Vendor 1 Current Application Server 5 10:10
3 Backup app folder Vendor 1 Current Application Server 5 10:15
4 Backup SQL DB Vendor 1 Current Prod SQL Server 5 10:20
5P Take DB offline Vendor 1 Current Prod SQL Server 5 10:25
5T Restore SQL DB Vendor 1 New Prod SQL Server 5 10:30
6 Configure IIS Vendor 1 New Application Server 5 10:35
7 Install current RMP4.30 Vendor 1 New Application Server 5 10:40
8 Merge INI/ CSSfiles with backup copy Vendor 1 New Application Server 5 10:45
9 Upgrade to RMP4.30.2.602 Vendor 1 New Application Server 5 10:50
10 Perform integration testing Vendor 1 New Application Server 5 10:55
11 Install the client application on Windows Infra Lead App Delivery 5 11:00
12 Site manager perform functional testing App Lead New Application Server 5 11:05
13 Update intranet for all site links Infra Lead App Delivery 5 11:10
End 12:40
NewCo Application Migration Playbook
15. Create Application Migration Playbook
• Create step-by-step migration document
• Assign estimated duration to each step
• Obtain team signoff
ID Task Name Resource Location Duration
Planned Start
Time Notes Complete
Backed
Out
Actual
Start Time
Actual
Finish
Actual
Duration Start Delta
Duration
Delta
Pre-test steps 2.40 hours
Failover Start Time 10:00
0 Go / No Go Discussion All 5 10:00
1 Stop services, email, HL7, alert, auto report Vendor 1 Current Application Server 5 10:05
2 Stop app pool (IIS) Vendor 1 Current Application Server 5 10:10
3 Backup app folder Vendor 1 Current Application Server 5 10:15
4 Backup SQL DB Vendor 1 Current Prod SQL Server 5 10:20
5P Take DB offline Vendor 1 Current Prod SQL Server 5 10:25
5T Restore SQL DB Vendor 1 New Prod SQL Server 5 10:30
6 Configure IIS Vendor 1 New Application Server 5 10:35
7 Install current RMP4.30 Vendor 1 New Application Server 5 10:40
8 Merge INI/ CSSfiles with backup copy Vendor 1 New Application Server 5 10:45
9 Upgrade to RMP4.30.2.602 Vendor 1 New Application Server 5 10:50
10 Perform integration testing Vendor 1 New Application Server 5 10:55
11 Install the client application on Windows Infra Lead App Delivery 5 11:00
12 Site manager perform functional testing App Lead New Application Server 5 11:05
13 Update intranet for all site links Infra Lead App Delivery 5 11:10
End 12:40
NewCo Application Migration Playbook
16. Server & Storage Replication Process
Acquire and utilize P2V and/or V2V solution for
server replication
Migrate data using file/block copies where
necessary
Validate servers/storage replication was
successful
Upgrade virtual hardware drivers where
necessary
Create appropriate network communications in
the destination
Assign VMs to proper port group
Power on test copies of VMs
Assign new IP addresses and hostnames where
necessary
Perform server integrity testing (DNS, AD,
network communications, etc.)
Configure agents, if necessary (backup, SCCM,
antivirus, etc.)
17. Application:
Name/ Role:
Test Patient:
Duration to Result Validation Expected Result/ Duration
30 secs Launch Intellidose via Citrix Application login screen loads
10 secs
Enter admin/ clinical staff/ provider username
& password
Username & password input accepted in their
respective fields
10 secs Click login
Intellidose accepts valid username & password and
loads patient search page
10 secs Working patient list
Working patient list automatically displays on left of
patient search after successful login
10 secs
Cosigner's queue
Cosigner's queue automatically displays below working
patient list after successful login
30 secs
Search current patient (on Allscripts
schedule/ current appointment) by Last/ First Current patient displays and is selectable
10 secs Select/ double-click patient Opens patient chart and patient displays in working
10 secs Validate patient demographics Patient demographics, under general tab, should mirror
5 min Validate allergies/ medication
Patient's allergies and current, inactive and med Hx to
display under allergies/ medication tab
1 min Validate active problems Patient's active problems from EHRto display under
1 min Validate social history Patient's social history from EHRto display under
1 min Validate family history Patient's family history from EHRto display under
1 min
Validate past medical history
Patient's past medical history from EHRto display
under past med history tab
1 min Validate diagnosis Patient's Dx from EHRto display under Dx 1 tab
5 mins Validate lab results from EHR Patient's lab results from EHRto display under tests
2 min Validate vital signs Patient's vitals correctly listed under Metrics tab
10 mins Provider writes an order/ plan & signs off on it
Pre-built and customized treatment plans can be
applied to patients Tx plan
Document nurse's visit Nurse follows provider, documents visit (nurse's note)
Validate document transfer to EHR
Chemo order and nurse's note successfully populate in
EHR(.PDFformat) under Hem/ Onc chart section.
Correctly labeled as Instrinsiq Chemo Orders and
30 min Modify existing treatment plan Treatment plans editable
5 min
Run sample report
Ability to run drug utilization, tumor registry, practice
statistics, patient status and operational reports
1 min Verify printing: record summary Printers displayed from Citrix session and documents
Intellidose
Jim Baker; Clinical Analyst
Int Test1
Test Application Using Test Scripts
• Review and updated test
script(s)
• Schedule testing resources
and provide user access
• Perform application test
using test script(s)
• Create issue log and
resolve all outstanding
issues
18. Test Load Balancing & High Availability
• Test each application
based on architecture
necessities
• Verify functionality of
load balancing
• Verify high availability
• Create affinity rules for
the VMs
21. Test Failover/Failback
• Document failover process
with failover architecture
• Create a process flow
diagram
• Create a step-by-step
runbook/playbook with
failover durations
• Perform test failover and
failback
22. Test Restore from Backup
• Setup backup solution for
all application servers
• Verify backups created at
necessary intervals
• Restore data from backups
• Validate restored data
RESTOREBACKUP
25. Schedule & Communicate Application
Downtime
• Identify application cutover
window with application
owners and user community
• Determine appropriate
communication channel for
cutover announcement
• Determine and secure go-
live resources
• Send out scheduled
communications
26. Cutover Application to New Data Center
Follow Mock Migration Process
• Utilize tested migration playbook
• Stop application at old platform
• Ensure replication is complete
• Start application at new platform
• Use and validate application
using test script(s)
• Reroute user traffic to new
platform
• Communicate uptime
• Document and track issues
29. Decommission Process
Verify checklist of servers to decommission
Initiate change control to decommission all servers
Remove servers from backup software/schedule
Remove servers from antivirus software
Remove A records from DNS server
Remove alerts from server monitoring solution
For physical servers – pull network cables, unrack
servers, and destroy data on disks
For virtual servers – delete VMs from the
management server
Delete LUNS/NFS/CIFS shares associated with server
Update all application documentation, if necessary
Cancel existing vendor obligations/contracts, if
necessary
Revise budget and deliver report of completion
30. Closeout
• Complete performance and cost
measures
• Ensure any new contracts are
set and budgeted for upcoming
financial year
• Verify inventory has been
updated
• Update cost changes
• Add operations monitoring and
management system
33. Project Plan
• Tracks timeline and
deliverables for
application migration
project
• Provides an overview of
epics, stories and key
milestones
• Tracks key
dependences
35. Migration Dashboard
• Lists every
application being
migrated
• Dashboard
updates
• Green –
complete
• Yellow – in
progress
• Migration
dashboard feeds
Velocity chart
36. Velocity Chart
• Depicts progress of project in a burn-up velocity based on
migration dashboard
• Velocity tracks
• Current scope
• Completed scope
• Baseline scope
• Current forecast
• Baseline forecast