Frequently Asked Questions

Most mid-market implementations land between $18K and $160K, depending on user count, modules, customization, and the cleanliness of your migration data. We publish full ranges on the pricing page. License fees are separate and paid directly to Odoo S.A. — there's no markup from us.

Fixed-fee against a signed SOW for implementation work. Change orders go through a written estimate before any extra work starts. For ongoing support, we publish a monthly subscription with documented response times.

Odoo license fees (paid to Odoo S.A.), third-party integration fees (Avalara, Stripe, Shopify), hosting (if not in the package), and end-user training beyond train-the-trainer. We list every excluded item in the SOW so there are no surprises.

Yes — typically 30% on signature, 40% at the mid-project milestone, and 30% at go-live. For larger Enterprise packages we can structure monthly billing across the engagement.

Starter packages go live in 6–10 weeks. Growth packages take 10–16 weeks. Enterprise multi-entity rollouts run 16–24 weeks or more. The biggest swing factor is data migration cleanliness, not module count.

Sometimes. A focused 3-module rollout (Sales, CRM, Inventory) with clean data and no customization can land in 4–6 weeks. We're transparent about which scope cuts genuinely save time versus which just defer work to phase two.

21 days for a single-entity Sales + CRM rollout with five users and clean Salesforce data. That's an edge case — the median is 12 weeks across all engagements.

Discovery weeks 1–2 are workshops to confirm modules, data sources, and integrations. Configuration weeks 3–8 happen in parallel: we configure standard Odoo while you prepare data exports. UAT weeks 9–10 are full end-to-end testing with your team. Cutover and hypercare follow.

Plan on 8–12 hours per week from a single business owner during discovery and UAT. Power users (1 per module) need 4–6 hours per week during configuration. Less involvement than that and the project drifts.

Yes. We staff one senior consultant + one functional analyst per engagement, with a technical architect on call for customizations. No outsourcing, no team swaps mid-project.

Small changes within the original scope are absorbed. Material scope changes go through a written change-order with an updated estimate and timeline. We've never billed retroactively for unscoped work.

Odoo.sh is the safe default for ≤50 users with light customization. Our managed AWS/GCP cloud fits 25–250 users or anyone needing custom domains, VPN, or specific compliance regions. Self-hosting fits regulated industries with in-house DevOps maturity. We're deployment-agnostic.

Your choice. AWS us-east-1, us-west-2, ca-central-1, and eu-west-3 are the most common picks. We deploy to the region closest to your primary user base or the one your compliance team requires.

Yes. We've moved customers from Odoo.sh to managed cloud and vice versa with zero downtime using the standard Odoo backup format. Plan on 1–2 weeks for the migration window.

Sales, CRM, Inventory, Accounting, and Purchase make up about 70% of phase-one scopes. Manufacturing, Project, HR, Helpdesk, and eCommerce typically come in phase two. We help prioritize based on your operational bottlenecks, not Odoo's app catalog order.

Selectively. We audit each OCA module for the target Odoo version, code quality, maintenance velocity, and upgrade path before adopting it. Our audit checklist is on the security page. About 30% of recent engagements use 1–3 OCA modules.

Functionally, yes — Odoo's CRM, ERP, and accounting modules cover the same surface. Whether it's the right call depends on your team's change tolerance, custom Salesforce flows, and reporting needs. We run a free 30-minute discovery to assess fit honestly.

Six-phase framework — extract, profile, map, transform, dry-run, cutover. We dry-run the migration at least twice in a sandbox before production cutover. The framework is documented in detail on our resources page.

We allocate a data-cleaning sprint during the project. Typical cleanup includes deduping partners, normalizing tax codes, fixing currency rounding, and rationalizing chart-of-accounts. Two weeks of cleanup typically saves four weeks of post-go-live debugging.

Yes — we've migrated from 30+ source systems. Anything with a CSV export and a published schema is migratable. Custom legacy systems take longer but are doable; we'll quote the data work separately if it's significant.

Bug fixes, security patches, Odoo S.A. coordination, user-question response, and minor configuration changes. Our full SLA — response times, escalation paths, holiday hours — is published on the technical support policy page. No hidden fine print.

P1 (production down) is 1 hour during business hours, 4 hours outside. P2 (major impact) is 4 business hours. P3 (minor) is 1 business day. P4 (request) is 3 business days. All measured against the policy page, not best-effort.

Yes, and we'll help. Several customers have transitioned to in-house support after 12–18 months with us. We document the environment, run knowledge-transfer sessions, and stay on retainer for escalations during the transition.

No. Implementation is project-based against a signed SOW. Support contracts are month-to-month with a 30-day notice to cancel — no minimum term, no auto-renewal traps. We earn the contract every month.

You do. All custom code is delivered with full source, repository access, and documentation. The work-product belongs to your business, not to Octura. We're a partner, not a vendor lock.

We'll help with the transition. Standard handover includes environment documentation, repository access transfer, recent backups, and an introductory call with the incoming partner. About 95% of our customers don't leave — but those who do are not penalized.