ERP Go-Live Checklist: 50-Point Launch Readiness Guide

Key Takeaways

• A go-live readiness gate at T-minus 7 days is your final decision point: go or postpone
• Data validation (financial reconciliation, record counts, integrity checks) must pass before cutover begins
• Go-live day should be planned for a Friday evening or weekend to minimize business disruption
• Designate a "war room" with key stakeholders for the first 48 hours
• Have a documented rollback plan that can be executed within 4 hours if critical failures occur
• Post-go-live support for 90 days is essential — most issues surface in the first 2 weeks
• Celebrate go-live day — successful launches deserve recognition

---

Phase 1: Pre-Go-Live (T-minus 30 to T-minus 1 Day)

Data Validation (Items 1–12)

• 1. Final data migration complete. All master and transactional data has been imported into the production ERP environment.

• 2. Record count verification. Total records per entity match between source system and ERP. Acceptable variance: 0 for master data, <0.1% for transactional data.

• 3. Financial reconciliation complete. Trial balance in the new ERP matches the source system as of the migration cutoff date. Tolerance: $0.00 for balance sheet accounts, $1.00 for P&L accounts.

• 4. Accounts receivable aging matches. Aged AR report in the new ERP matches the source system. All customer balances verified.

• 5. Accounts payable aging matches. Aged AP report in the new ERP matches the source system. All vendor balances verified.

• 6. Bank account balances match. Opening balances for all bank accounts reconcile with actual bank statements.

• 7. Inventory levels verified. Physical inventory count (or most recent cycle count) matches ERP inventory on-hand quantities for critical items.

• 8. Open orders are actionable. Every imported open sales order and purchase order can be processed (fulfilled, received, invoiced) in the new ERP without errors.

• 9. Data integrity checks passed. No orphan records (transactions referencing non-existent master data), no duplicate master records, no invalid field values.

• 10. Historical data accessible. Closed transactions and archived data are available for reference (either in the new ERP or in an accessible archive).

• 11. Number sequences configured. Invoice numbers, order numbers, payment references, and other sequences start at the correct values (no gaps, no conflicts with historical numbers).

• 12. Multi-currency rates current. Exchange rates are updated for the go-live date. Automatic rate feed configured and tested.

System Testing (Items 13–22)

• 13. End-to-end workflow testing complete. Every critical business process has been tested from start to finish in the production environment (not staging).

• 14. Integration testing passed. All third-party integrations (payment gateways, shipping carriers, eCommerce platforms, bank feeds, EDI) are tested with production credentials.

• 15. Email notifications verified. Order confirmations, invoice emails, payment receipts, and internal notifications send correctly with proper formatting and sender addresses.

• 16. Report generation verified. All critical reports (P&L, balance sheet, aged AR/AP, inventory valuation, sales summary) generate correctly with accurate data.

• 17. Print templates verified. Invoices, delivery slips, purchase orders, and labels print correctly on the hardware that will be used in production.

• 18. User access and permissions tested. Each user role has been verified: correct menu access, correct record visibility, correct edit/create/delete permissions. At least one user per role has logged in and confirmed.

• 19. Performance testing passed. System response times are acceptable under expected concurrent user load. Page load under 3 seconds, report generation under 30 seconds for standard reports.

• 20. Backup and recovery tested. A full database backup has been created and a test restore has been performed successfully. Backup schedule is configured and verified.

• 21. Disaster recovery plan documented. If the production server fails, what is the recovery procedure? Documented with step-by-step instructions, contact information, and estimated recovery time.

• 22. Security audit completed. Default passwords changed, SSL certificates valid, firewall rules configured, admin access restricted to authorized personnel only.

Training and Readiness (Items 23–30)

• 23. All users have completed role-based training. Training attendance records confirm 100% participation for go-live-critical roles. Users who missed sessions have received catch-up training.

• 24. Train-the-trainers are prepared. Internal trainers have delivered at least one practice session and have all support materials.

• 25. Quick reference cards distributed. Printed quick reference guides for the top 5 tasks per role are at every workstation.

• 26. Sandbox environment available. Training sandbox remains accessible for users who need additional practice in the first weeks after go-live.

• 27. Support contact information distributed. Every user knows: who to contact for help (Tier 1 internal trainer, Tier 2 IT, Tier 3 vendor), how to contact them (phone, chat, email, ticketing system), and expected response times.

• 28. Go-live communication sent to all staff. Company-wide email from executive sponsor confirming the go-live date, what to expect, where to find help, and encouragement.

• 29. External stakeholder notification. Customers, vendors, and partners have been notified of any changes that affect them (new invoice format, new payment portal, new order process).

• 30. Executive go/no-go decision documented. Formal sign-off from the project sponsor, project manager, and department heads that the system is ready for go-live. If any critical items are outstanding, the go-live is postponed.

---

Phase 2: Go-Live Day (T-Day)

Cutover Procedures (Items 31–38)

• 31. Source system frozen. No new transactions are entered in the old system after the cutover point. All users are logged out. Clear communication sent: "Stop using [old system] as of [time]."

• 32. Final data delta migrated. Any transactions entered in the source system between the initial migration and the cutover freeze are now imported into the new ERP. This "delta" migration must be fast — ideally under 2 hours.

• 33. Delta reconciliation complete. Post-delta migration, re-verify financial totals, open order counts, and inventory levels. Everything must match.

• 34. DNS and domain changes completed (if applicable). Customer-facing portals, API endpoints, and eCommerce URLs point to the new system. SSL certificates verified.

• 35. Integrations activated. Payment gateways, shipping connectors, bank feeds, eCommerce sync, EDI, and any other integrations switched from test to production mode.

• 36. Automated jobs activated. Scheduled tasks (bank feed sync, exchange rate update, email reminders, report generation, backup jobs) are enabled and verified.

• 37. Go-live announcement sent. "The new system is now live. Please log in at [URL]. If you need help, contact [support info]."

• 38. First transaction processed successfully. A real production transaction (a sales order or a purchase order) is processed end-to-end by a business user to confirm the system is operational. This is the symbolic "first order" moment.

Monitoring and Support (Items 39–44)

• 39. War room established. A dedicated physical or virtual room where the project team, IT support, and vendor consultants are available for the first 48 hours. Equipped with: dashboards showing system health, a running log of reported issues, and direct communication channels.

• 40. Issue logging and prioritization active. Every reported issue is logged in a tracking system with:

  • P1 (Critical): System down, data loss, cannot process orders — fix within 1 hour
  • P2 (High): Major feature broken, significant workaround required — fix within 4 hours
  • P3 (Medium): Minor feature issue, easy workaround available — fix within 24 hours
  • P4 (Low): Cosmetic issue, enhancement request — fix within 1 week

• 41. System health monitoring active. Server CPU, memory, disk usage, database connections, and application error rates are being monitored in real time. Alerts configured for threshold breaches.

• 42. Rollback criteria defined and communicated. The specific conditions under which the go-live is reversed and the old system is reinstated are documented and agreed by leadership. Typical triggers:

  • Cannot process financial transactions for more than 4 hours
  • Data integrity issue affecting more than 1% of records
  • System downtime exceeding 2 hours with no resolution path

• 43. Floor support deployed. Support staff (internal trainers, IT, vendor consultants) are physically present in each department for the first 2 business days to assist users in real time.

• 44. End-of-day checkpoint. At the end of go-live day, the project team reviews: transactions processed, issues logged, issues resolved, outstanding P1/P2 items, and a go/no-go decision for Day 2 normal operations.

---

Phase 3: Post-Go-Live (T+1 Day to T+90 Days)

Week 1: Stabilization (Items 45–48)

• 45. Daily stand-up meetings. 15-minute meeting every morning for the first 2 weeks: what issues came up yesterday, what is the plan for today, what is blocked. Attendees: project manager, department leads, IT support lead.

• 46. First week-end close (if applicable). For businesses that do weekly financial reconciliation, the first week-end close in the new system is a critical milestone. Finance team should allocate extra time and have support available.

• 47. User feedback survey deployed. Short survey (5 questions, 2 minutes) sent to all users after the first week:

  1. How confident are you using the new system? (1–5)
  2. What task is most difficult for you?
  3. What task is easier than in the old system?
  4. Have you needed help this week? Was it available?
  5. What one thing would you change about the new system?

• 48. Quick-win enhancements deployed. Based on Week 1 feedback, deploy 3–5 quick improvements that demonstrate responsiveness. Examples: dashboard customization, shortcut addition, default value change, report format adjustment.

Month 1–3: Optimization (Items 49–50)

• 49. First month-end close. The most important milestone after go-live. Plan for this to take 2–3x longer than your eventual target. Key activities:

  • Bank reconciliation for all accounts
  • Accounts receivable and payable aging review
  • Revenue recognition verification
  • Expense accruals and prepayments
  • Intercompany eliminations (if multi-company)
  • P&L and balance sheet generation
  • Comparison with previous month (from old system) for consistency check

• 50. 90-day post-go-live review. Formal assessment of the implementation:

---

Go-Live Timing: When to Launch

Best Times to Go-Live

Avoid:

• Month-end or quarter-end (finance team is already stretched)
• Major sales events or promotions (e-commerce and retail)
• Holiday periods (reduced support availability)
• The last week of the fiscal year (absolute worst timing)

Go-Live Weekend Schedule

---

Rollback Plan Template

A rollback plan is insurance you hope never to use. But not having one when you need it is catastrophic.

Rollback Decision Authority

Who can authorize rollback: Project Sponsor (CEO/CFO) — and only after consultation with Project Manager and IT Lead.

Rollback Trigger Criteria

Rollback Procedure

1. Announce: Notify all users to stop entering data in the new system immediately
2. Backup: Create a full backup of the new ERP database (preserves any data entered post-go-live)
3. Restore: Reactivate the source system from the pre-go-live backup
4. Delta recovery: Any transactions entered in the new ERP during the go-live period must be manually re-entered in the source system
5. Integrations: Revert all integration connections to the source system
6. DNS: Revert any domain/URL changes
7. Communicate: Send all-staff email confirming the rollback and providing timeline for next attempt
8. Debrief: Within 48 hours, conduct a detailed analysis of what went wrong and what must change before the next attempt

Estimated Rollback Time: 2–4 hours

---

Communication Templates

Pre-Go-Live Announcement (T-minus 7 Days)

Subject: ERP Go-Live: [Date] — What You Need to Know

Body: Dear Team, after [X] months of preparation, our new ERP system goes live on [date]. Here is what to expect: [brief summary of changes]. Training materials are available at [link]. If you have questions, contact your department trainer or [support email]. This is an exciting milestone for our company, and your preparation and positive attitude are what will make it a success. — [Executive Sponsor Name]

Go-Live Day Announcement

Subject: The New System Is Live — Welcome to [ERP Name]

Body: Good morning, Team. Our new ERP system is now live. Please log in at [URL] using your credentials. Quick reference cards are at your workstation. If you need help, your first contact is [department trainer name]. For technical issues, contact IT at [phone/email]. We have extra support on-site today and tomorrow. Thank you for your hard work in making this happen. — [Executive Sponsor]

Post-Go-Live Check-In (T+3 Days)

Subject: ERP Go-Live Update: Day 3

Body: Team, here is a quick update on how things are going: [X] transactions processed, [Y] issues reported and [Z] resolved. The most common question has been [topic] — here is a quick guide: [link]. Your feedback is valuable — please share any suggestions at [feedback form link]. Thank you for your patience and professionalism this week.

---

Frequently Asked Questions

What is the most common reason for go-live failure?

Insufficient data validation. When financial reconciliation has not been completed rigorously before cutover, the first week of production operation reveals discrepancies that undermine trust in the new system. Always reconcile to the penny before go-live — it is the single most important checklist item.

Should we do a big-bang go-live or phased go-live?

It depends on your organization. Big-bang (all modules, all departments at once) is faster but higher risk. Phased (one module or department at a time) is lower risk but creates longer parallel running and integration complexity. For organizations with strong project management and thorough testing, big-bang works well. For organizations with limited change management capacity, phased is safer.

How long should parallel running last?

Minimum 30 days for small businesses, 60–90 days for enterprises. The goal is to complete at least one full month-end close in the new system before decommissioning the old one. Parallel running should be active (both systems in use) for the first 30 days and passive (old system read-only for reference) for the remaining period.

What if we discover critical issues on go-live day?

Follow the issue prioritization system (P1–P4). P1 issues get immediate attention with all available resources. P2 issues get addressed within the business day. P3 and P4 issues are logged for resolution in the first week. If P1 issues cannot be resolved within the rollback threshold (typically 2–4 hours), execute the rollback plan. It is better to delay go-live by a week than to operate a broken system.

Who should be in the war room on go-live day?

Project manager, IT lead, vendor/implementation consultant, database administrator, one representative from each major department (finance, sales, operations), and an executive sponsor (available by phone if not on-site). The war room should operate for the first 48 hours, then transition to normal support channels.

How do we celebrate go-live?

Celebrate visibly. A successful go-live is a significant organizational achievement. Ideas: company-wide email from the CEO, team lunch, go-live cake, recognition of key contributors, and small tokens of appreciation for the project team. Celebration reinforces that the transition is positive and builds momentum for the stabilization phase.

Can ECOSIRE support our ERP go-live?

Yes. ECOSIRE's implementation services include full go-live support: cutover planning, war room staffing, hypercare support for 90 days, and first month-end close guidance. We have supported hundreds of Odoo go-lives across manufacturing, distribution, services, and retail. Contact us to plan your successful launch.

---

Launch with Confidence

A successful go-live is not about everything going perfectly — it is about having the preparation, the team, and the processes to handle whatever comes up. This 50-point checklist gives you the framework. Your team provides the execution.

ECOSIRE's Odoo implementation team has refined this go-live process across hundreds of deployments. From cutover planning through 90-day stabilization, we provide the expertise and support that turns go-live day from a source of anxiety into a milestone worth celebrating.

Plan your go-live with ECOSIRE and launch your ERP with confidence.