Methodology
How we deliver an Odoo implementation
Seven phases, each with a named owner, a measurable exit criterion, and a fixed-price commitment. The methodology behind every TechUltra Odoo engagement.
Last reviewed:
Five principles behind the methodology
These are the rules we don't break, even under client pressure. Each one came from a past engagement where breaking it cost us.
-
Fixed price after discovery — never open-ended T&M
We don't bill time-and-materials for project work. Discovery is the one fixed-price exception. The implementation quote is a single number you can budget against. If we mis-scoped, that's our risk, not yours.
-
Standard first, customization second
We push back on customization requests where standard Odoo already does the job, even if it means changing your process slightly. Every customization is future maintenance — your future-self thanks us for the discipline now.
-
Data migration is its own workstream
Treating data migration as an afterthought is the single most common reason mid-market implementations slip. We run 3+ test migrations before go-live, with full reconciliation, on a parallel timeline to development.
-
Your team owns the system, we own the implementation
From week 1 your champions are configuring alongside us. By go-live they can run the system without us. Hypercare is a backstop, not a crutch.
-
Hypercare is where most partners go quiet — we don't
The first 4 weeks post go-live are when real users hit edge cases we didn't test. A named senior consultant is on-call. Daily standup the first week. SLA-backed defect resolution. This is non-negotiable.
The seven phases in detail
- 01
Discovery
- Duration
- 1 week (fixed-price, USD 2,500–4,000)
- Owner
- Senior consultant + your operational lead
Objective. Map your business processes, surface compliance and integration requirements, and produce a fixed-price implementation quote with confidence intervals.
Activities
- Process workshops (4–6 hours total, role-by-role)
- Existing systems audit — what stays, what gets replaced, what integrates
- Compliance review (GST, VAT, e-invoicing, statutory reports for your jurisdictions)
- Module fit assessment — which standard apps + what customization
- Data migration scope — sources, volumes, cleanup requirements
- Risk register — top 5 risks with mitigation plan
Deliverables
- Process map (current state + target state)
- Module + customization scope document
- Data migration plan
- Integration list with effort bands
- Fixed-price quote for full implementation
- Project plan with phases and milestones
Exit criteria
You have a written, signed-off scope and quote. We have enough to commit to a fixed price. Either side can walk away with no further obligation.
- 02
Setup & configuration
- Duration
- 2–6 weeks (depends on module count)
- Owner
- Functional consultant + technical lead
Objective. Install Odoo (managed or self-hosted), configure each module to match the target-state process map, and establish a baseline working system in a sandbox.
Activities
- Hosting provisioning (Odoo Online / Odoo.sh / self-hosted)
- Chart of accounts setup, tax configuration, fiscal year setup
- Master data structure (product categories, customer/vendor master, BOM templates)
- User accounts, access rights, multi-company structure if applicable
- Module-by-module configuration walkthrough with your team
- Country-specific localization (GST, VAT, ZATCA, e-invoicing format)
Deliverables
- Configured Odoo sandbox accessible to your team
- Configuration document (what was set up, why, where to change later)
- Localization confirmed working with test transactions
Exit criteria
Standard processes work end-to-end in sandbox with sample data, without customization. Anything that doesn't work standard is now on the customization backlog with effort estimates.
- 03
Customization & development
- Duration
- 2–8 weeks (parallel to data migration)
- Owner
- Senior Odoo developer + functional consultant
Objective. Build the custom modules, workflow automations, and reports that the standard system doesn't cover. Keep this list short — every customization is future maintenance.
Activities
- Custom module development (Python + OWL frontend)
- Studio-based no-code customization for forms and views
- Custom reports (Odoo report builder + QWeb templates)
- Workflow automations (Odoo automation rules + server actions)
- API extensions for external integrations
- Code review and unit tests for every custom module
Deliverables
- Custom modules deployed to sandbox, tested by your team
- Technical documentation (module purpose, key entry points, upgrade notes)
- Test cases covering each customization
Exit criteria
Every committed customization is working in sandbox and signed off by the relevant business owner. Anything we cut is documented with the reasoning.
- 04
Data migration
- Duration
- 1–4 weeks (parallel to customization)
- Owner
- Data migration specialist + your data owner
Objective. Move master data, historical transactions, and open balances from your existing system into Odoo cleanly. This phase makes or breaks go-live confidence.
Activities
- Source system export (QuickBooks / Tally / SAP / NetSuite / spreadsheets)
- Data cleansing (duplicates, malformed records, missing fields)
- Mapping (source field → Odoo field, with transformation rules)
- Test migrations into a staging Odoo instance (3+ iterations typical)
- Reconciliation reports (record counts + financial totals match source)
- Production cutover plan with cut-off date and freeze window
Deliverables
- Migrated sandbox/staging instance with full data
- Reconciliation report showing 100% match for financials, near-100% for transactional
- Cutover runbook for production migration
Exit criteria
Your data owner has signed off the staging migration. Financial reconciliation reports tie out. The cutover plan is rehearsed and timed.
- 05
Integrations
- Duration
- 1–6 weeks (parallel where possible)
- Owner
- Integration developer + your IT/ops lead
Objective. Connect Odoo to the systems that will continue running alongside it — payment gateways, banks, e-invoicing portals, EDI partners, CRM, marketing tools.
Activities
- Connector setup for native integrations (Shopify, Amazon, Stripe, Razorpay)
- Custom API integrations (banks, payment gateways, EDI, statutory portals)
- Webhook / message-queue setup where real-time sync is needed
- Authentication and credential management (OAuth, API keys, certificates)
- Integration test suite — runs on every change to catch regressions
- Monitoring and alerting (Odoo logs + external monitoring)
Deliverables
- Each integration working end-to-end in staging
- Integration runbook (what fails, how to diagnose, how to retry)
- Monitoring dashboards for production
Exit criteria
Every committed integration is sending and receiving real test data successfully. Failure modes are documented. Production credentials are provisioned but not active yet.
- 06
Training & UAT
- Duration
- 1–3 weeks
- Owner
- Training lead + your role-based champions
Objective. Train your team end-to-end and run formal User Acceptance Testing. UAT signoff is the gate before production go-live.
Activities
- Role-based training sessions (sales, ops, finance, HR — each gets relevant modules)
- Hands-on practice in a clone of the staging environment
- Quick-reference guides per role (1-page PDFs, not 80-page manuals)
- Formal UAT — your team runs scripted test cases covering every committed process
- Defect log + resolution cycle (target: zero P1, <5 P2 at signoff)
- Train-the-trainer for your internal champions who will support post go-live
Deliverables
- Training completion certificates per role
- Role-based quick-reference guides
- UAT signoff document with defect log
Exit criteria
UAT is signed off by every business owner. P1 defect count is zero. P2 defect count is below the agreed threshold (typically <5) with a fix plan for each.
- 07
Cutover & hypercare
- Duration
- 1 weekend + 4 weeks hypercare
- Owner
- Project manager + on-call senior consultant
Objective. Execute the production cutover and stabilize the system through the first 4 weeks of real use. Hypercare is the highest-touch period of the engagement.
Activities
- Cutover weekend — production data migration, integration go-live, user account activation
- Day-1 floor support — on-site or remote, every user has a named contact
- Daily standup for week 1, every-other-day for weeks 2–4
- Defect triage with SLA-backed fixes
- End-of-month financial close support (single biggest stress test)
- Post-go-live review at week 4: what worked, what to improve, support model going forward
Deliverables
- Production system live, all users transacting daily
- Stable financial close completed in Odoo
- Post-go-live report with metrics (transaction volume, defect count, training gaps)
- Ongoing support plan signed off
Exit criteria
First end-of-month financial close has been completed in Odoo. P1 defect count from go-live is zero. User adoption metrics (logins, transactions) are at expected levels. You're ready for ongoing support to take over from the project team.
Total timeline by deployment size
Three reference shapes. Yours will land within ±20% of the closest one once discovery is done.
| Deployment shape | Total duration | Phase breakdown |
|---|---|---|
| 10 users, 2 modules, no integrations | 4–6 weeks total | Discovery 1 wk → Setup 1 wk → Migration 1 wk → Training 1 wk → Cutover + hypercare 1 wk. |
| 50 users, 5 modules, 2 integrations | 10–14 weeks total | Discovery 1 wk → Setup 3 wks → Customization 3 wks (parallel: Migration 2 wks + Integrations 3 wks) → Training/UAT 2 wks → Cutover + hypercare 4 wks. |
| 250 users, 8 modules, 4 integrations, multi-entity | 16–20 weeks total | Discovery 2 wks → Setup 4 wks → Customization 6 wks (parallel: Migration 3 wks + Integrations 5 wks) → Training/UAT 3 wks → Cutover + hypercare 4 wks. Often phased rollout by entity. |
Frequently asked questions
-
How long does an Odoo implementation actually take?
Depends on scope. 10-person business with 1–3 modules: 4–8 weeks. 50-person mid-market with 4–6 modules and 1–2 integrations: 10–14 weeks. 250-person business with 6–10 modules, multi-entity, multiple integrations: 16–20 weeks. 1,000+ person enterprise: 24+ weeks, often phased by entity or geography. Numbers are end-to-end from contract signature to go-live, not just development.
-
Why do you insist on a paid discovery week?
Because skipping discovery is the #1 reason mid-market Odoo projects overrun by 40%+. One week of paid discovery (USD 2,500–4,000) saves typically 4–8 weeks of timeline slippage on a 14-week project. It also gives both sides a no-strings-attached exit point if the fit isn't there — far cheaper than discovering misalignment mid-build.
-
Can phases run in parallel?
Yes — customization, data migration, and integrations almost always run in parallel after the setup phase. Discovery and cutover are sequential by definition. The phase breakdowns we publish are calendar weeks (the elapsed time), not effort weeks (the consultant time).
-
What does "fixed price" actually mean — can it change?
The price for the agreed scope is fixed. If you add scope mid-project (new module, new integration, new requirement that wasn't in discovery), that's a change order with its own fixed price. We don't quietly bill against an open-ended budget. The change-order line is the place where customers feel most respected by our process.
-
Who from our team needs to be available, and how much?
An executive sponsor (10% time), an operational lead (50% time for the whole project), and one champion per major module (30% time during their module's setup and training phases). UAT phase needs broader involvement — typically 5–10 hours per end-user. Below this level of internal engagement, no Odoo implementation succeeds regardless of partner quality.
-
What happens if we hit a serious problem during the build?
Every project has a weekly steering call (you + our project manager + senior consultant) explicitly to surface risks. Any P1 issue triggers an immediate escalation call within 24 hours with our delivery lead. Material schedule slippage triggers a re-plan with you, not a unilateral slip. We publish a weekly status report with traffic-light indicators per workstream.
-
How is your process different from other Odoo partners?
Three differences. First, paid discovery week — most partners do scoping for free (and then over-promise to win the deal). Second, fixed price always — most partners default to T&M and the budget mysteriously inflates. Third, hypercare is a named phase with a named consultant for 4 weeks post go-live — most partners hand off to L1 support the day after go-live. The combination is the difference.
-
Do you offer any kind of post-implementation guarantee?
Defects discovered within 60 days of go-live that relate to functionality delivered as part of the implementation scope are fixed at no charge. Beyond 60 days, defects are covered by your ongoing support contract. New requirements that emerge post go-live are always change orders or part of an ongoing support engagement, not retroactive scope.