Transformation and migration

Activities:

• Establish and provide high-level project plan and schedule
• Conduct kick-off meeting
• Project set up in central repository
• Request available IT asset data

Deliverables:

• High-level project plan
• High-level project schedule
• Kick-off presentation
• Team onboarded
• Project set up in central repository

Activities:

• Review overall current state architecture 
• Capture, assess, and analyse embedded and dynamic SQL within the upstream and downstream applications for remediation.
• Review compute, storage, network designs and platforms for source and target.
• Capture, assess, and analyse the complexity of the database objects for the target databases

Deliverables:

• Migration effort and cost, risks timeline, and proposed implementation plan
• Final report summarising the captured data and analysis
• End-to-end migration roadmap 

Activities:

• Define required data inputs
• Perform data mapping and data normalisation 
• Review and import inventory asset data
• Provide data gap analysis report
• Conduct interviews and asset validation sessions

Deliverables:

• Assets normalised and mapped in our tooling
• Asset dependencies validated

Activities:

• Develop T-minus and T-plus draft runbooks
• Develop migration recipes per move method
• Identify any required governance & change management procedures
• Develop migration scripts to support the increase of migration throughput.
• Analyse target compute and storage requirements based on existing performance data and growth requirements

Deliverables:

• T-minus and T-plus runbooks available for viewing
• Cookbook, event recipe, and draft event runbook available for viewing
• Technical runbook(s) with engineer steps and specifications required to execute migrations
• Target compute and storage sizing requirements to support server and data workloads developed
• Low-level plan signoff

Runbooklogic:

• The base framework of a runbook is defined with the end customer.
• The meta data of an application or workload will determine which migration logic is used to create
  the runbooks.

• Multiple variations or activities can be dynamically created.

Sequence:

• Each task has predecessor and a successor tasks.
• Tasks only become available once the processor tasks are complete.

Task ownership:

• Each task is assigned to an individual, pre confirmed during the simulation events.
• Durations for each tasks are forecast.

Communications:

• To support the scaling of bulk migrations in a single event window, the migration consultants man a command centre.

Activities:

• Prepare for event execution
• Conduct dry-run event and task validation 
• Perform any required runbook adjustments and complete pre-migration event preparation
• Setup for virtual and data migration execution
• Event oversight
• Manage the command centre and support execution
• Conduct post migration event lessons learned session
• Perform any required runbook adjustments
• Migration workload execution
• Execute virtual and data migrations
• Provide post virtual and data migration support

Deliverables:

• Final event runbook
• Tools and scripts configured successful test from source to target conducted
• In scope servers successfully migrated
• Post migration event results document

Automation reduces time, effort and cost, whilst reducing manual errors, giving your business more time to focus on your primary objectives.

• Repetitive tasks can be completed faster whilst ensuring high quality results as each task is performed identically, without human error.