Go-live & adoption
Go-live & adoption
From blueprint to production — with a phased approach that minimises risk and maximises adoption. Data migration, pilot, training, cutover and hypercare as one agreed runbook.
Updated May 18, 2026
Chapter 5 — Go-live & adoption
Configuration is technically nailed down. Now Gfacility has to get through something far more unpredictable: people. A flawless configuration and a failed adoption look the same after three months: an empty system and missed expectations. This chapter makes sure the real difference gets made.
Go-live is not a button. It is a period: weeks before the switch (data migration, pilot, training), the switch itself (cutover), and the first weeks after (hypercare). Each of those phases has its own risks and its own success criteria. This chapter gives you the runbook.
What do you deliver?
Migration plan with data cleanup
Which data moves, which gets cleaned up, which goes to archive.
Pilot results and go/no-go report
What worked, what broke, which decisions block broader use.
Training plan and change approach
A learning path per audience, with attendance and certification requirements.
Cutover runbook
Minute-by-minute script of the switch, with role assignment and roll-back button.
Hypercare plan
What support during the first 4-6 weeks after go-live, with escalation path.
Evidence for closure
Adoption figures, SLA measurements and lessons learned for the handover.
The five phases
5.1 Data migration & cleanup
Which history moves along, what do you dump, what do you archive — and how do you validate that everything is correct?
5.2 Pilot & feedback loop
Let a small group actually work with it, feed back quickly, and decide go/no-go with numbers.
5.3 Training & change management
A learning path per audience — plus a communication plan that sells the change before the system does.
5.4 Cutover runbook
The actual switch: minute by minute, with role assignment, freeze window and roll-back button.
5.5 Hypercare period
The first four-to-six weeks after the switch, with extra support, fast bugfix loop and clear exit criterion.
Recommended timeline
What happens when?
- −8wData migration script ready, first dry run on acceptance environment.
- −6wPilot group starts with real workflow in a production-like environment.
- −4wTraining rolls out: train-the-trainer first, broad audience from −3w.
- −2wPilot evaluation + go/no-go — final blockers now, not the night before.
- −1wFreeze window on source systems, communication blitz, hypercare team on standby.
- D0Cutover — usually on a weekend or holiday period. Follow the runbook, improvise nothing.
- +4-6wHypercare — elevated support, daily triage. Only then handover to steady-state support.