Frequently Asked Questions

Most mid-market implementations fall somewhere between $18K and $160K, and where you land depends on user count, module mix, customization, and how clean your migration data actually is. Full ranges are on the pricing page. License fees are separate, paid straight to Odoo S.A. with no markup added by us.

Implementation work is fixed-fee against a signed SOW. Any change order gets a written estimate before extra work begins, and ongoing support runs on a monthly subscription with documented response times.

A few things sit outside the quote: Odoo license fees (paid to Odoo S.A.), third-party integration fees such as Avalara, Stripe, or Shopify, hosting if it's not part of the package, and end-user training beyond train-the-trainer. Every excluded item is listed in the SOW, so nothing shows up as a surprise later.

Yes. The typical split is 30% at signature, 40% at the mid-project milestone, and 30% at go-live, and for larger Enterprise packages we can arrange monthly billing across the engagement instead.

Foundation 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 plus CRM rollout with five users and already-clean Salesforce data. That's very much the exception though; the median across all our engagements is 12 weeks.

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. Every engagement is staffed with one senior consultant and one functional analyst, plus a technical architect on call for customization work. There's no outsourcing and no team swaps partway through.

Minor changes that fit within the original scope get absorbed at no extra cost. Anything more substantial goes through a written change order with an updated estimate and timeline, and we've never once billed retroactively for work that was never scoped in the first place.

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.

It's entirely your choice. AWS us-east-1, us-west-2, ca-central-1, and eu-west-3 come up most often, and we'll deploy to whichever region sits closest to your primary user base, or whichever 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 account for roughly 70% of phase-one scopes, while Manufacturing, Project, HR, Helpdesk, and eCommerce usually land in phase two. Priority gets decided by your actual operational bottlenecks, not by the order Odoo's app catalog happens to list things.

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 much the same ground. Whether that's actually the right move depends on your team's tolerance for change, any custom Salesforce flows in play, and your reporting needs. We run a free 30-minute discovery call to give you an honest read on fit.

We follow a six-phase framework: extract, profile, map, transform, dry-run, and cutover, running the dry-run at least twice in a sandbox before touching production. The full framework is documented on our resources page.

A data-cleaning sprint gets built into the project. That usually means deduping partners, normalizing tax codes, fixing currency rounding, and rationalizing the chart of accounts, and two weeks spent on that cleanup typically saves four weeks of debugging after go-live.

Yes, we've handled migrations from more than 30 different source systems. If it can export CSV and has a published schema, it's migratable. Custom legacy systems take more time but they're still doable, and we'll quote that data work separately when it's substantial.

The monthly contract covers bug fixes, security patches, coordination with Odoo S.A., answering user questions, and minor configuration changes. Response times, escalation paths, and holiday hours are all spelled out on the technical support policy page, with nothing buried in fine print.

P1, production down, gets a response within 1 hour during business hours and 4 hours outside them. P2, major impact, is 4 business hours; P3, minor issues, is 1 business day; and P4, general requests, is 3 business days. Every one of those is measured against the policy page, not treated as 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 runs project-based against a signed SOW, and support contracts are month-to-month, with 30 days' notice to cancel, no minimum term, and no auto-renewal traps. Every month, we have to earn that contract again.

You do, entirely. All custom code comes with full source, repository access, and documentation, and the work product belongs to your business, not to Octura. We see ourselves as a partner, not a vendor lock-in.

We'll help make that transition smooth. A standard handover includes environment documentation, transferred repository access, recent backups, and an introductory call with whoever's coming in. About 95% of our customers stick around, but the ones who don't are never penalized for leaving.