Go-Live & Hypercare
Going live on a new ERP is one of the most critical moments of any implementation. We treat it with the seriousness it deserves — detailed planning, a structured cutover, and a dedicated support window right after.
Pre-Go-Live Checklist
Before we set a go-live date, every item below must be complete and signed off by both teams.
| ✅ Configuration | |
|---|---|
| ☐ | All modules configured and UAT sign-off received |
| ☐ | Custom developments tested and accepted |
| ☐ | Integrations tested end-to-end |
| ☐ | User accounts created with correct roles and permissions |
| ☐ | Email notifications and workflows verified |
| 📦 Data Migration | |
| ☐ | Opening balances entered and verified (Finance) |
| ☐ | Item masters, customer/supplier masters migrated |
| ☐ | Employee data and salary structures migrated |
| ☐ | Historical data loaded (if in scope) |
| ☐ | Data sign-off received from your team |
| 🖥️ Infrastructure | |
| ☐ | Production server configured (if self-hosted) |
| ☐ | SSL certificate installed |
| ☐ | Backup automation verified |
| ☐ | DNS cutover plan confirmed |
| 🎓 Training | |
| ☐ | All user groups trained |
| ☐ | Manuals distributed |
| ☐ | Internal ERPNext admin identified and trained |
Go-Live Approach
We recommend going live on a Monday or Tuesday, avoiding month-end and financial year-end periods. This gives the team maximum runway to resolve any issues before the weekend.
Cutover Plan
| Timeline | Activity | Owner |
|---|---|---|
| T − 3 days | Code and configuration freeze | Hybrowlabs |
| T − 3 days | Final data migration run on production | Hybrowlabs + Client |
| T − 1 day | Pre-launch sync — walkthrough of go-live day plan | Both |
| Go-live day | System handed over to users | Hybrowlabs + Client |
| Go-live day | Hybrowlabs team on active standby (full day) | Hybrowlabs |
| T + 1 week | First post-go-live review meeting | Both |
During Go-Live
On go-live day the Hybrowlabs team is on a live bridge (Google Meet / WhatsApp) throughout business hours.
| Issue Type | Resolution Target |
|---|---|
| 🔴 Critical (system blocked) | Within 2 hours |
| 🟠 High priority | Within 1 business day |
| 🟡 Configuration tweak | Same day where possible |
Hypercare Window — 4 Weeks Post Go-Live
The Hypercare phase begins the moment you go live and runs for 4 weeks. This is our structured commitment that the same team who built your system stays by your side through early adoption.
During Hypercare:
- ✅ Same engineers and consultants remain assigned — no handoff to a generic support team
- ✅ Any issue within agreed scope fixed at no additional cost
- ✅ Priority over all other Hybrowlabs projects
- ✅ Weekly review calls to track open items and user feedback
- ✅ WhatsApp / Helpdesk channel — 4-business-hour response SLA
- ✅ Controlled hotfix deployments — tested before applying to production
Go-live is not the finish line. It's the starting line of your ERPNext journey.
Post-Hypercare
After Hypercare, you transition to our Annual Maintenance Contract (AMC).
- Issues clearly within original scope → still addressed at no charge
- Enhancements, new modules, integrations → covered under AMC or retainer
- A case study documenting the implementation journey is prepared (with your approval) and shared for review before publishing
See Ongoing Support & AMC for full details on what happens next.
