5 Odoo Go-Live Mistakes That Still Cost Teams Weekends (2026 Checklist)

Why Odoo go-live still breaks weekends

Odoo go-live is not a button click. It is a cutover: data, users, integrations, and expectations all move at once. When something fails, the symptom is often vague — “the shop is slow,” “invoices look wrong,” “email does not send.”

The root cause is usually one of five predictable mistakes below. Fix these before you announce the launch date.

1. Backups exist, but restores were never tested

Most teams configure automated PostgreSQL backups and assume they are safe. A backup file that never restored is not a backup — it is hope.

What goes wrong: corrupted dumps, wrong retention, backups taken while Odoo workers are mid-transaction, or restores that take hours because nobody practiced.

Fix before go-live:

• Restore to a clean staging server at least once
• Time the restore (know your RTO in minutes, not guesses)
• Document who can run the restore and where credentials live
• Keep one off-site copy separate from the production VM

If you only do one thing from this list, do this one.

2. Staging is not a copy of production reality

A staging database with demo data and three test users will not reveal production problems. Staging should mirror volume and integrations, not just schema.

What goes wrong: payment providers work in test mode only, cron jobs disabled on staging, missing custom modules, or different Odoo version/build.

Fix before go-live:

• Refresh staging from a recent production anonymized dump when possible
• Enable the same modules and cron schedule (scaled down if needed)
• Run one full sales → invoice → delivery → payment path on staging
• Test PDFs and email templates with real-looking records

3. User permissions are copied, not designed

Importing users from spreadsheets without a role model creates security debt on day one. Finance sees warehouse costs. Sales edits accounting. Support resets admin passwords.

What goes wrong: over-permissive groups, shared logins, or “we will fix ACLs later.”

Fix before go-live:

• Map roles: sales, warehouse, accounting, website, admin
• Use groups of least privilege; add rights incrementally when someone blocked
• Disable shared accounts; enforce individual logins
• Audit Settings → Users the day before cutover

4. Outbound email is untested under load

Odoo sends mail for invoices, delivery orders, password resets, and ecommerce confirmations. SMTP misconfiguration shows up after customers complain.

What goes wrong: SPF/DKIM missing, relay limits on shared hosting, cron mail queue backlog, or templates referencing wrong company details.

Fix before go-live:

• Send test mail from each critical template (invoice, sale order, delivery, portal invite)
• Verify SPF, DKIM, and DMARC on the sending domain
• Watch the mail queue during a staging load test
• Set a real reply-to and support address customers can reach

5. Cutover plan is a date, not a runbook

“We go live Friday” is not a plan. A runbook lists order of operations, owners, rollback triggers, and communication.

What goes wrong: DNS switched before data freeze, modules updated during business hours, no rollback path, stakeholders surprised by read-only mode.

Fix before go-live:

• Write a one-page runbook: freeze, backup, deploy, smoke tests, DNS, announce
• Define rollback: when you revert DNS vs when you restore DB
• Schedule cutover in a low-traffic window with two people present
• Keep a public status line for internal teams (“shop read-only until 14:00”)

Quick pre-flight checklist

Use this the day before go-live:

1. Restore test passed this week
2. Staging walkthrough completed (sale → invoice → pay → ship)
3. Roles reviewed; no shared admin except break-glass
4. Test emails received in Gmail/Outlook, not spam
5. Runbook shared with client + engineer on call

Full checklist (PDF)

This post is the short version. For backups, monitoring, upgrades, and day-two operations, get the Odoo Survival Guide (PDF, instant download):

Odoo Survival Guide on Gumroad

Built for Odoo teams shipping on 17, 18, and 19 — no subscription, keep the PDF forever.

Hexalian builds production Odoo modules and engineering guides. Browse modules at hexalian.com/store.