New: Odoo and Dynamics 365 cost calculators.Estimate your costs

Odoo implementation: cost, time, and steps

As of October 2026, a new-customer 50-hour Odoo Success Pack is US$5,950. The guide covers steps, Standard at US$31.10 per user a month, and timelines.

OdooImplementation & Go-Live10 min readUpdated 28 sources

Key takeaways

  • Light User capabilities listed by Odoo include that person's own time off, expenses, appraisals, attendances, referrals, and planning, plus field service, inventory barcode operator, read-only Knowledge, payslips, POS, and the manufacturing shop floor.
  • Odoo's project leader role combines project manager, business analyst, and product knowledge so process-versus-product trade-offs have one owner.
  • Put the accounting cutover on a month or quarter boundary so opening balances have a clean date.
  • Odoo.sh worker, storage, and staging prices are not on the public pages used here. Confirm hosting on the order form and keep it as its own line.

What an Odoo implementation includes

An Odoo implementation is the work of making Odoo match the processes a company of 20 to 100 people already runs: which apps go live first, how records get in, who is trained, and how you cut over. Installing the software is the start of that work. Sales, inventory, accounting, manufacturing, and eCommerce can share one database, and you can phase apps instead of turning every department on in the same week.

Three decisions set the project before any workshop. The edition is Community or Enterprise. The subscription is One App Free, Standard, or Custom. The host is Odoo Online, Odoo.sh, or on-premise. Community is the LGPLv3 core. Enterprise is the licensed edition that adds functional support, upgrades, and hosting. Switching Community to Enterprise is documented, except for a source install.

As of October 2026 the US pricing page lists One App Free at US$0 for one app and unlimited users on Odoo Online. Standard is all apps on Odoo Online. Custom is all apps on Odoo Online, Odoo.sh, or on-premise, plus Studio, agentic AI, multi-company, and the external API. Odoo.sh hosting for custom developments is excluded from the subscription price.

A paying user has backend access to create, view, or edit documents, or is an employee record with no linked user. Portal users, such as customers and suppliers viewing invoices, are not paying users. Website visitors who place eCommerce orders are not paying users either. A Light User is listed at US$8.90 and is quoted through an Odoo advisor. Odoo defines a light user as an active user designated Light User, or an active HR employee record not linked to an active non-portal user.

  • Light User capabilities listed by Odoo include that person's own time off, expenses, appraisals, attendances, referrals, and planning, plus field service, inventory barcode operator, read-only Knowledge, payslips, POS, and the manufacturing shop floor.
  • The subscription includes hosting, maintenance, and unlimited email support Monday to Friday, 24 hours a day, in English, French, Spanish, or Dutch, plus free eLearning and upgrades.
  • The subscription excludes implementation and expert services, Odoo.sh hosting for custom developments, in-app credits (SMS, contact autocomplete, lead generation, AI bill and expense scan), and maintenance of custom code.
  • Odoo Online hosting is free, with unmetered storage up to 100 GB under the acceptable-use policy. Online uses intermediary SaaS versions that are not the releases used on Odoo.sh or on-premise. Minor Online versions ship every two to three months and are not eligible for extended support.

Odoo implementation methodology and steps

Odoo's implementation methodology says Odoo experts should challenge the work at critical steps. The same document frames gap analysis at about 10%, kick-off at about 5%, and implementation at about 80%. Configuration, import, test, and training together are the about 80% implementation block. It also says custom-development complexity grows with the square of the number of customizations, so the standing instruction is to keep custom code small.

People looking for an Odoo implementation PDF, cookbook, or methodology book can use two public agreements plus a written phase plan. The Enterprise Subscription Agreement, version 13, dated 24 September 2026, sets covered versions, support, and renewal math. The Partnership Agreement sets who may deliver Enterprise services. Success Pack contents sit on Odoo's packs page. This guide is the working method for a US or Canadian company. There is no separate book title to order.

A project plan that a finance lead can govern names the phase-one apps, the count of paying users and light users, the host, the import list, the training dates, the go-live month, and the hours that pay for the work. When scope changes, update that plan in writing before the hours are spent. Flectic sets the timeline for a first phase in the written scope, with a fixed price, before work starts. The delivery model is designed to deliver up to 3x faster cycle time. That is a design target, and it still depends on scope, data, and how fast your team decides.

  • Odoo's project leader role combines project manager, business analyst, and product knowledge so process-versus-product trade-offs have one owner.
  • The customer single point of contact needs authority to accept a standard workflow or to approve a customization. A messenger without that authority adds a cycle to every open point.
  • Official support tickets cover bugs and guidance on standard features and Covered Extra Modules. Development and customization questions need a separate services agreement. Bug-fix handling is to start within 2 business days.
  1. 1. Analysis and gap review

    Map the processes you will run in phase one, the systems that feed them, and the metric that tells you go-live worked. Name a customer single point of contact who can decide scope. Cut legacy habits that only feel mandatory. This slice is the small front of the plan, on the order of the 10% gap weight in Odoo's methodology.

  2. 2. Kick-off and solution design

    Lock the subscription (Standard or Custom), the host, and the fiscal localization before anyone posts accounting entries. Configure standard workflows first. Record gaps that need Studio or custom code as a separate list with an owner. Kick-off is the short alignment step, on the order of 5% in Odoo's weighting.

  3. 3. Configuration and any approved development

    Build in short cycles: configure, review with the process owner, adjust. Studio on the Custom plan covers fields and views when the gap is configuration. Put unavoidable Python in its own modules so an upgrade can be tested.

  4. 4. Import, test, and role-based training

    Import master data and open items after they are cleaned. Run at least one full test pass: order to delivery to invoice to payment. Train by role while configuration is still open, so the people who do the work can reject a setup that looks right in a demo and fails on a Tuesday.

  5. 5. Go-live and the weeks after

    Cut over on a date finance can reconcile, with signed tests, a named on-call list, and a written rollback rule. Keep that on-call list staffed for the first weeks. The second wave (another app, another site, another company) uses the same five steps on a smaller unknown.

How long does an Odoo implementation take?

How long an Odoo implementation takes depends on whose clock you use. Odoo states that 80% of projects within its estimator's scope go to production in 200 hours or less. That figure counts consultant hours. Calendar weeks run longer. At a 40-hour week, 200 hours is five weeks of one consultant. Your team still has to clean data, attend training, and sign off, so the calendar is longer than the hour count.

One Odoo partner, Cybrosys, publishes three bands: 1 to 2 weeks for a basic setup, 1 to 3 months for a mid-level multi-module project with migration and training, and more than 3 months for a complex multi-module, multi-entity rollout. Treat that as one vendor's schedule, useful as a scope signal. A US quote published by Bista has Duff Jones of Trearc, Inc. in Tennessee describing a project that stayed inside a 9-month span from ERP planning to go-live. The same page quotes Dennis McCarthy, a CFO in Detroit, saying the work stayed within budget and on plan, with no dollar figure. Use the 9 months as one company's reported span, not as a price.

A fast path is a single app, clean master data, and a small hour pack. A comprehensive path adds manufacturing, a second company, or custom code, and those are the items that push past a Success Pack into a longer partner project. Manufacturing routings, multi-company rules, and custom modules each add test cycles the hour estimator does not absorb for free.

  • Put the accounting cutover on a month or quarter boundary so opening balances have a clean date.
  • Add calendar time for test cycles and dirty data. The 200-hour figure does not include your staff's hours.
  • Phase by value. Finance and inventory can go live while manufacturing or eCommerce follows, using the same method on the next slice.
  • A buyer who wants the system live inside a month is describing a basic setup. That wish shows up in project stories. It fits a short pack and a narrow app list, and it does not fit a multi-entity manufacturer.
Odoo implementation duration signals as of October 2026
SignalDurationWhat it covers
Odoo Success Pack estimator200 hours or less for 80% of projects in that estimator's scopeOdoo's own production claim. Hours, not elapsed calendar time.
Cybrosys basic setup1 to 2 weeksA basic setup on that vendor's published band, with packages starting from US$999 and no itemized breakdown.
Cybrosys mid-level1 to 3 monthsMulti-module work with migration and training, as that vendor defines mid-level.
Cybrosys complexMore than 3 monthsMulti-module, multi-entity rollout, as that vendor defines complex.
Flectic Odoo projects8 to 28 weeks for industry packagesFixed-scope packages for five industries. Any other first phase gets its own timeline in the written proposal.
Trearc, Inc. (Tennessee), as quoted by Bista9 months from ERP planning to go-liveOne US company's reported span. No dollar amount is used from that page.

Odoo implementation cost in the US and Canada

Odoo implementation cost is two bills: the subscription, and the services. As of October 2026 the US pricing page shows Standard at US$31.10 and US$38.90 per user per month, and Custom at US$61.00 and US$76.20 per user per month. The page says the discount is valid for 12 months for the initial users ordered. It does not spell out a monthly-versus-annual toggle beyond that sentence, so budget both figures and confirm the renewal rate before you sign. No public Canadian dollar license price was on that page. Figures below stay in US dollars. Do not convert them.

Services have a published price when you buy Success Packs from Odoo. Returning-customer prices are Starter 4 hours US$580, Basic 25 hours US$3,600, Standard 50 hours US$7,000, Custom 100 hours US$12,500, and Pro 200 hours US$25,000. New customers get 15% off the first pack only: US$493, US$3,060, US$5,950, US$10,625, and US$21,250. Dividing pack price by hours is arithmetic, not a published day rate: the returning 50-hour pack is US$7,000 divided by 50, or US$140 an hour, and the new-customer 50-hour pack is US$5,950 divided by 50, or US$119 an hour.

Odoo says companies under 50 employees usually implement with Odoo using Success Packs, companies over 50 employees usually use a partner for local project management, and companies over 250 employees should contact Odoo directly. A full partner statement of work for a US or Canadian firm is quoted per project. This guide does not publish a market range for that work. Cybrosys, one partner, says packages start from US$999 for a basic setup. That floor is not itemized and is not a US rate card. The Success Pack estimator also displayed an example of EUR 4,500 before the 15% new-customer discount (EUR 3,825 after that 15%, which is arithmetic on the displayed example, not a named package).

Worked example, assumptions stated. Fifteen paying Standard users, no light users, Online hosting, the discount applied to those initial users for 12 months, and a new customer's first pack. Fifteen times US$31.10 is US$466.50 a month, or US$5,598 for those 12 months. Fifteen times the other shown Standard rate, US$38.90, is US$583.50 a month, or US$7,002 for a year. Add the new-customer 50-hour pack at US$5,950 and the first-year cash at the discounted license rate is US$11,548 before in-app credits, travel, custom code, and your staff's time. Swap in the 100-hour new-customer pack at US$10,625 and that first-year total is US$16,223. The 200-hour new-customer pack at US$21,250 makes it US$26,848.

Same headcount on Custom: 15 times US$61.00 is US$915 a month (US$10,980 for 12 months). Fifteen times US$76.20 is US$1,143 a month (US$13,716 for a year). Choose Custom when you need Studio, multi-company, the external API, agentic AI, or a host other than Online. Ten Light Users at the listed US$8.90 is US$89, arithmetic on the listed price. The advisor quote sets the billing term.

For license prices, Odoo.sh and Flectic's planning ranges by scope, see Odoo pricing.

Book a 30-minute call with Flectic after you have those two lines. The call counts paying users and light users and matches phase one to a Success Pack or a statement of work.

  • Odoo.sh worker, storage, and staging prices are not on the public pages used here. Confirm hosting on the order form and keep it as its own line.
  • On renewal, if prior-term charges (excluding the non-covered-version fee) are below the current list price, charges can increase by up to 7% per year of the previous term.
  • In-app credits for SMS, contact autocomplete, lead generation, and AI bill and expense scan sit outside the user price. So does maintenance of custom code.
Published Odoo license and Success Pack prices as of October 2026 (US pricing page, USD)
ItemPriceBasis
One App FreeUS$0One app, unlimited users, Odoo Online
Standard, discounted rate shownUS$31.10 per user per monthDiscount valid 12 months for the initial users ordered
Standard, other rate shownUS$38.90 per user per monthShown beside the discounted rate
Custom, discounted rate shownUS$61.00 per user per monthSame 12-month discount rule. Odoo.sh hosting is extra
Custom, other rate shownUS$76.20 per user per monthShown beside the discounted rate. Odoo.sh hosting is extra
Light UserUS$8.90Quoted through an Odoo advisor
Success Pack, new customer, first pack onlyUS$493 / US$3,060 / US$5,950 / US$10,625 / US$21,2504, 25, 50, 100, or 200 hours. 15% off the first pack only
Success Pack, returning customerUS$580 / US$3,600 / US$7,000 / US$12,500 / US$25,0004, 25, 50, 100, or 200 hours

What moves an Odoo implementation budget

Two companies with the same user count can buy very different hour packs. The license math above is the predictable line. The services line moves with apps, data, localization, custom code, and whether you are under or over the 50-employee line Odoo uses to point you at Success Packs or a partner.

Use the map below in the first scoping call so two proposals describe the same work. If a quote is a single lump, ask for the hour count, the import list, and the hypercare window so you can tell a 25-hour pack from a 200-hour one.

What pushes an Odoo project from a short pack to a longer one
DriverFits a shorter packPushes hours up
AppsOne app on One App Free, or a handful of standard appsManufacturing, quality, multi-warehouse, and eCommerce in the first phase
UsersNamed paying users, light users only where the capability list fitsEveryone given full backend access, including people who only need the shop floor or time off
Companies and entitiesOne company on Standard or CustomMulti-company, which is a Custom-plan feature
DataMaster data and open items, cleaned before importYears of history from several systems. Data-import help is not on every Success Pack
CodeStandard setup and StudioApp customization and developments, which need a services agreement. Extra modules carry an extra monthly maintenance charge
Where the work happensRemote configuration inside the packOnsite days. Travel time and travel expenses are billed separately

Data migration in an Odoo implementation

You can migrate data from an existing ERP or from Excel. Confirm that data-import assistance is inside the pack or the statement of work, because Odoo does not put that assistance on every Success Pack. Load master data (customers, vendors, products, chart of accounts) and open documents so the team can process the next order. Odoo's methodology tells project leaders to avoid importing historical transactions you do not need in the live database.

Clean the file before it hits Odoo. Duplicates, mixed units, and unreconciled receivables become day-to-day errors after cutover. Run at least one full test import into a staging database and walk one document from order to delivery to invoice to payment. Reconcile the trial balance to the cutover date you picked with finance.

Posted accounting entries block a later switch of the fiscal localization package. Set the United States or Canada localization before anyone posts. Classify each legacy customization as keep, replace with a standard feature, or retire, and write that list into the project plan so it does not reappear as surprise development in the last month.

  • Inventory every source system and name an owner for each file.
  • Standardize names, addresses, units, and tax categories in the source or a staging sheet.
  • Leave closed history in an archive unless a report needs it inside Odoo.
  • Write the rollback rule: which failed check sends you back to the source system, and where the backup sits.
  • Keep a second test import after the last cleanup. The first test finds the mess. The second proves the mess is gone.

Odoo implementers and implementation services

Odoo implementers fall into three paths, and Odoo states which one it expects. Companies under 50 employees usually implement with Odoo using Success Packs. Companies over 50 employees usually use a partner for local project management. Companies over 250 employees should contact Odoo directly. A team can also configure Community or Enterprise with its own staff when it already has the skills and the time. For a US or Canadian company of 20 to 100 people, the live choice is often a Success Pack, a partner, or a mix: Odoo hours for standard setup, and a local implementer for fiscal detail, data, and the weeks after go-live.

An Odoo implementation company that touches Enterprise must have an Enterprise subscription in place for that customer, including during implementation. The Partnership Agreement says partners may not offer services on Enterprise to a customer who does not have one. Ask for the subscription to be active before configuration starts. Official partner levels, measured on the last 12 months, require net-new Enterprise users and certified staff: Ready is 10 users and 1 certified employee. Silver is 75 users, 3 certified employees, and 70% retention. Gold is 300 users, 6 certified employees, and 80% retention. Certifications must be on at least one of the three latest versions.

Flectic implements Odoo for companies in that 20 to 100 person range in the United States and Canada. We are an independent consultancy. The next step is a working session with us, not a partner directory. On that call we size paying users, light users, the first apps, and whether a Success Pack covers phase one or the scope needs a statement of work. If you have not settled on Odoo yet, a free discovery call with Flectic is the independent step, and the written recommendation that follows tests Odoo and Dynamics 365 against your processes.

  • Ask who the named consultant is.
  • Ask whether data import and the hypercare window sit inside the hours. On a Success Pack, data-import assistance is not on every pack.
  • Ask whether phase one is a Success Pack or a statement of work, and what happens when the hours run out.
  • If the firm is an Odoo partner, ask which level it holds (Ready, Silver, or Gold) and on which version its certified people passed. That question is for a partner firm.
  • Support tickets do not replace a services agreement. Development questions are out of the ticket scope.
Who does the Odoo implementation
PathOdoo's own guidanceWhat you still own
Odoo, via Success PacksUsual path under 50 employeesData cleanup, decisions, and any work the pack does not include
A partnerUsual path over 50 employees, for local project managementAn active Enterprise subscription, a named lead, and scope control
Your own teamAvailable if you already have the skills and the hoursThe full configuration, import, training, and upgrade burden
Contact Odoo directlyOdoo's instruction for companies over 250 employeesA scope large enough that the packs page is the wrong front door

Where Flectic fits

Flectic is one of the paths in the table above: an independent consultancy that implements Odoo and Dynamics 365 for companies of 20 to 100 people in the US and Canada. We hold no certification from Odoo or Microsoft and earn no vendor quota on either.

  • Choose Flectic if you are not yet sure Odoo is the right platform and want it tested against Dynamics 365 first.
  • Choose Flectic if you want phases scoped and priced one at a time, with a senior consultant from discovery to launch.
  • Choose Flectic if you want an implementer to size paying users, light users and phase one before you buy a Success Pack.
  • Look elsewhere if you need an Odoo Ready, Silver or Gold partner, because Flectic holds no Odoo certification.
  • Look elsewhere if you are over 250 employees, where Odoo says to contact it directly.
  • Look elsewhere if your team already has the skills and time to configure Odoo itself.

Who owns which decisions

Projects that look like software trouble are often ownership gaps. Odoo's methodology puts a project leader on the delivery side and expects a customer single point of contact who can decide. Use a short RACI so a workshop does not end with a task nobody can close.

The executive sponsor holds budget and priority. The single point of contact holds scope and test sign-off. Department champions hold the process truth for their team. The delivery lead holds the plan and the risk call. Developers hold isolated custom modules, not an open request to recreate the old system.

Roles on an SME Odoo project
RoleOwnsHands back
Customer executive sponsorBudget, priority, and blocked decisionsDay-to-day ticket triage
Customer single point of contactScope decisions, test sign-off, champion listWriting specs with no product challenge
Department championsHow the work is done today, peer training, edge casesHosting, subscription tier, and architecture
Delivery project leaderPlan, configuration trade-offs, riskProcess changes the sponsor has not accepted
DevelopersIsolated modules, integrations, and testsOpen-ended rebuilds of the legacy system

Where customization blows the plan

Odoo's methodology says custom-development complexity grows with the square of the number of customizations, and it tells experts to minimize that work and to challenge specifications when cost exceeds benefit. Implementers writing about failed projects point to the same pattern: rebuilding the legacy system screen by screen, then paying to retest every module on the next major version. One practitioner account calls the Year 2 version of that problem customization gridlock, where the upgrade costs more than the company will approve, so the database stays on an old version.

Studio, included on the Custom plan, is the first place to put a field or a view. It is not a substitute for a process decision. Complex workflows and deep integrations still need modules, and those modules need a services agreement because standard support does not cover development questions. Extra monthly charges apply for maintenance of extra modules or lines of code. Performance work requires a Success Pack of at least 50 hours.

When scope changes mid-project, price the change before the work continues. More configuration means more pack hours. Customization means a separate services line. Onsite work adds travel time and travel expenses. A new app in phase two is a new slice of the same method, with its own hours, not a verbal add-on to a pack that is already consumed.

  • Write each customization as a module with a test, an owner, and an upgrade cost.
  • Prefer a standard workflow when the gap is habit. Keep code for a rule the standard app cannot express.
  • Budget extra-module maintenance as a recurring line. Odoo states an extra monthly charge for maintenance of extra modules or lines of code.
  • If the database falls outside the three covered major versions, a legacy fee can apply. See the version section before you accept a project that starts on an old release.

Training and daily use

Success Packs include training and coaching. That covers the consultant's time. It does not cover the wages of your staff while they learn. Panorama Consulting says the biggest barrier to ERP adoption is habit. Under pressure, users default to what they know, and lasting change comes from rewiring routines, not from the overview session alone.

Train key users during configuration, while a wrong field can still be changed. Build a role-by-app matrix. Warehouse staff need receipts, picks, and counts. They do not need a full accounting course. Budget internal time as hours times headcount times loaded cost, using your own labor rates. That line is absent from the license and Success Pack prices, so put it on the comparison sheet.

Measure use after go-live: share of orders created in Odoo, legacy logins, and tickets by department. Set a date to retire the old entry path. Champions on the floor in the first two weeks answer 'how do I do this' faster than a ticket queue, and the pack's remote coach is the backstop for setup questions.

  • Put training dates on the project plan next to the import dates. Training after go-live is recovery, not preparation.
  • Give each champion a short list of tasks they must complete in the test database before sign-off.
  • Review the same list at 30 days. Tasks that slipped back to spreadsheets are either a training gap or a setup gap. Those are different fixes.

Agentic AI on the Custom plan

As of October 2026, agentic AI is listed on the Custom plan, with Studio, multi-company, and the external API. It is a license feature. It is not the implementation. The subscription still excludes implementation services, and support tickets still exclude development and customization questions.

Teams that already use documentation search, automation tools, and analytics can draft checklists and test ideas faster. Odoo also supports external LLM integration and server actions. Those tools shorten a task inside a phase. They do not remove analysis, a test import, user testing, or the weeks after go-live.

Flectic's delivery is designed to deliver up to 3x faster cycle time. That is a design target for how we run the work, tied to fewer reversals and faster decisions. A Custom subscription does not, by itself, deliver that speed.

Go-live and the weeks after

Go-live is the start of running the business on Odoo. In ERP practice, the higher-response window that follows is often called hypercare. Panorama Consulting's hypercare checklist describes that window as higher response and closer monitoring, with durations commonly cited from shorter windows on simpler systems to about 30 to 90 days on complex ERP rollouts. Match the length to user count and process risk, and name the hours in the proposal.

Before the cutover weekend, freeze scope, sign the tests, load reconciled opening balances, and put champions on a call list. Agree the rollback rule in writing. After cutover, watch invoice cycle time, inventory counts, and tickets by app for the first month. Hold a 30-day review and a 90-day review: what broke, which habits returned, which app is phase two.

If you are on Odoo Online, the cloud SLA targets 99.9% monthly uptime, about 45 minutes of unplanned downtime, excluding planned maintenance. Hosting regions named by Odoo are Europe, the Americas, Asia-Pacific, the Middle East and Northern Asia, and Oceania. Backups are 14 full backups over at least 3 months, replicated in Europe and Canada, and customers cannot choose or restrict backup regions. Single-server disaster objectives are an RPO of 24 hours (near zero for SaaS) and an RTO of 6 hours. Odoo says these objectives are not legally binding guarantees. They are not a substitute for your own cutover backup.

  • A proposal that ends on launch day has left out the window where edge cases show up.
  • Custom modules need a regression pass on each upgrade. Standard features ride Odoo's upgrade. Your code does not.
  • Know which host you are on before you promise the company it will always sit on the newest major version. Online minor versions and Odoo.sh majors follow different clocks.

Odoo and Dynamics 365 for this size of company

Flectic implements Odoo and Microsoft Dynamics 365. For a company of 20 to 100 people, the fit question is stack, budget, and how much process change you will accept.

Odoo fits when you want phased apps, manufacturing and eCommerce in the same product, and the license prices published on the US page as of October 2026. Dynamics 365 Business Central fits when you already run on Microsoft 365 and want finance in that stack. Settle process scope and data quality before the platform vote. Vague scope stalls either product.

If you are still comparing, bring the same user count, the same phase-one apps, and the same import list to both conversations. Otherwise you are comparing a 50-hour Odoo pack with a full accounting migration on another product, and the numbers will not teach you anything.

Odoo 17 implementation and current versions

As of October 2026, Odoo 20 is the current major release. Its release notes are dated September 2026. Odoo 19.0 release notes are dated September 2025. Standard support lasts the first three years after a major release on Odoo Online, Odoo.sh, and on-premise. A new Odoo implementation should start on a version still inside that window.

Published end-of-standard-support dates are Odoo 20.0 in September 2029 (planned), 19.0 in September 2028 (planned), 18.0 in September 2027 (planned), 17.0 in September 2026, and 16.0 in September 2025. Odoo 17's standard support has ended. Extended support starts after standard support, costs an extra fee, and is available only on Odoo.sh for a limited number of versions and on-premise for any version. This guide does not treat any one older version as confirmed inside that paid window.

The Enterprise Subscription Agreement defines Covered Versions as the three most recently released major versions, with a new major version once a year. With 20 released in September 2026, those three are 20, 19, and 18. If the database is older than the Covered Versions, then once a year, and no earlier than six months after a new major release, the customer pays an extra fee equal to 25% of the annualized price based on the current per-user price and user counts. Odoo 20's notes are dated September 2026, so the earliest month that six-month clause allows is March 2027. An Odoo 17 implementation started in October 2026 would sit outside standard support from the first week, and outside the three covered majors.

Odoo major versions and standard support as of October 2026
VersionStandard support endsWhere it sits
20.0September 2029 (planned)Current major. Release notes dated September 2026. One of the three Covered Versions.
19.0September 2028 (planned)Release notes dated September 2025. One of the three Covered Versions.
18.0September 2027 (planned)One of the three Covered Versions. Still inside standard support.
17.0September 2026Standard support has ended. Outside the three most recent majors.
16.0September 2025Standard support has ended.

US and Canada localization during implementation

An Odoo implementation in the US has to configure the United States fiscal localization, not only install accounting. Odoo describes that localization as following US GAAP, with modules for the chart of accounts, check printing, NACHA ACH files, 1099 CSV export, AvaTax, and US payroll. The 1099 report is a CSV for e-filing through a third party. It is not a direct IRS filing from Odoo.

The Canada localization ships a Canadian chart of accounts, reports, and default fiscal positions for every province and territory plus International. Tax follows the delivery province. Canadian vendor EFT uses the CPA005 file format. Avalara AvaTax is available for companies in Canada and the United States. Hosting backups are replicated in Europe and Canada, and you cannot choose or restrict that backup region. That matters if a Canadian privacy review asks where copies sit.

The Enterprise agreement does not warrant that the software complies with any local or international law. Country fiscal localizations still have to be configured. Posted entries block switching the fiscal localization package, so the US or Canada pack is a kickoff decision, not a cleanup task. This guide prices licenses and services for companies in the United States and Canada. UAE project pricing is outside its scope.

Odoo Online's SLA names the Americas as a hosting region. Pair that with the backup rule above when you write the hosting choice into the project plan. If a customer requires a single backup country, Online's published backup design does not offer that choice, and you should settle hosting before import.

  • US phase one: chart of accounts, banks, sales tax or AvaTax, 1099 vendor flags, and NACHA if you pay by ACH.
  • Canada phase one: province of delivery on taxes, fiscal position, GST, HST, PST, or QST as the localization sets them, and CPA005 if you pay vendors by EFT.
  • Test a customer invoice in each province or state you ship to. A single happy-path tax test will miss the delivery rule.
  • Keep the accountant in the room when the localization is selected. A later switch is blocked once entries are posted.

Fast Odoo implementation or a comprehensive one

A fast Odoo implementation is a narrow one. One App Free is US$0 for a single app and unlimited users on Odoo Online. Pair it with a Starter pack (4 hours, US$493 for a new customer's first pack) or a Basic pack (25 hours, US$3,060 on that same first-pack discount) when the work is configuration, training, and a dedicated consultant. Cybrosys's 1 to 2 week band is the calendar shape of a basic setup. A company that already knows its chart of accounts and its product list is the one that can aim to be live inside a month.

A comprehensive Odoo implementation covers several departments, an import, and training that sticks. The 50-hour pack (US$5,950 new, US$7,000 returning), the 100-hour pack (US$10,625 new, US$12,500 returning), and the 200-hour pack (US$21,250 new, US$25,000 returning) are the published hour budgets. Odoo says 80% of projects inside the estimator's scope go to production in 200 hours or less. The same page states a 98% implementation success rate with a Success Pack versus 65% without one. Those two rates are Odoo's own comparison on that page.

Comprehensive work still has edges the pack does not automatically include: data-import assistance, onsite consulting, app customization, developments, and performance work. Performance issues need at least 50 hours. Companies over 50 employees are the group Odoo points to a partner. Multi-company and Studio require the Custom plan. A manufacturer with two entities and custom routings is past a single Success Pack. Cybrosys's complex band is more than 3 months, and Trearc reported 9 months from planning to go-live. Price that scope in a statement of work.

eCommerce implementation follows the same split. A site that only needs the website app can start on One App Free, and shoppers placing orders are not paying users. A store that also invoices, tracks stock, and charges US or Canadian tax is a multi-app project on Standard or Custom, with AvaTax available in both countries. Staff who edit orders in the backend are paying users. Put the shop in phase one only when product, tax, and payment are already defined. Otherwise ship finance and inventory first and add the storefront as the next slice.

Fast and comprehensive Odoo implementation, using published packs (October 2026)
ShapeHours and new-customer first-pack priceTypical contents
Fast, one app4 hours, US$493, or 25 hours, US$3,060One App Free or a tight Standard setup. Configuration, training, project management. Import help is not guaranteed on the pack.
Mid, several apps50 hours, US$5,950Standard apps, coaching, and configuration. Confirm import and any onsite days as extras.
Comprehensive, still on packs100 hours, US$10,625, or 200 hours, US$21,250Broader configuration inside the estimator. Custom code and performance under 50 hours sit outside the default inclusions.
Partner projectQuoted. No public US or Canadian rate card in this guide.Odoo's usual path over 50 employees. Local project management, localization, and a written hypercare window.

Odoo implementation plan, guide, and written rules

An Odoo implementation guide the operator can run is a plan with owners, not a slide title. Build it in this order. Name phase-one apps and the host. Count paying users and light users and apply the October 2026 rates. Pick Standard or Custom. Pick the US or Canada localization before any posting. Choose the hour pack or write the partner scope. List import files. Put training dates on the same calendar as test dates. Name the go-live month and the hypercare hours.

The written rules to attach to that plan are the Enterprise Subscription Agreement (version 13, 24 September 2026) and the Partnership Agreement. The first sets the 25% legacy-version fee, the 7% renewal cap, the 2-business-day bug-fix start, and the limit of support tickets. The second sets Ready, Silver, and Gold thresholds and the rule that Enterprise services require a subscription even during implementation. Success Pack inclusions and the 200-hour claim sit on the packs page. Keep those three documents with the plan so a scope argument has a source.

Review the plan when any of these change: user count, a second company, a custom module, a move from Online to Odoo.sh, or a go-live that slips past a fiscal period. Each one changes either the license, the hours, or the cutover date. Flectic will walk that plan on a 30-minute call and mark which lines a first phase can hold.

  • Phase, owner, hours, cutover date, import scope, training matrix: if one of those is missing, the plan is still a wish list.
  • Store the subscription order next to the plan so the 12-month discount window on initial users has a start date.
  • Store the version you will implement (18, 19, or 20 as of October 2026) in the plan header. An Odoo 17 start date needs a different support conversation.
  • For eCommerce, add payment provider, tax, and which visitors are portal users versus which staff are paying users. Those three lines change the license more than the theme does.

How Flectic can help

Flectic implements Odoo for companies of 20 to 100 people in the US and Canada, one app at a time on a single database. We are independent and hold no Odoo certification, so if Dynamics 365 fits better, we say so in writing. Core operations (four to six apps, a basic data import, up to 25 users) has a planning range of $6,000 to $30,000, not a quote. Review the Odoo implementation scope, then book a free discovery call.

Sources

  1. As of October 2026 the US pricing page lists One App Free at US$0 for one app and unlimited users on Odoo Online; Standard for all apps on Odoo Online; Custom for all apps on Odoo Online, Odoo.sh, or on-premise, plus Studio, agentic AI, multi-company, and the external API.

    odoo.comChecked true
  2. As of October 2026, Standard is shown as US$31.10 and US$38.90 per user per month, and Custom as US$61.00 and US$76.20 per user per month. The discount is valid for 12 months for the initial users ordered.

    odoo.comChecked true
  3. A Light User is listed at US$8.90. A light user is an active user designated Light User, or an active HR employee record not linked to an active non-portal user, with the capabilities listed in this guide.

    odoo.comChecked true
  4. Portal users and website visitors placing eCommerce orders are not paying users. A paying user has backend access to create, view, or edit documents, or is an employee record with no linked user.

    odoo.comChecked true
  5. Subscription plans include hosting, maintenance, and unlimited email support Monday to Friday, 24/5, in English, French, Spanish, or Dutch, plus free eLearning and upgrades. They exclude Odoo.sh hosting for custom developments, implementation and expert services, in-app credits, and maintenance of custom code. Odoo Online hosting is free with unmetered storage up to 100 GB under the acceptable-use policy.

    odoo.comChecked true
  6. Companies under 50 employees usually implement with Odoo using Success Packs; companies over 50 employees usually use a partner for local project management; companies over 250 employees should contact Odoo directly.

    odoo.comChecked true
  7. Success Pack returning-customer prices: Starter 4 hours US$580; Basic 25 hours US$3,600; Standard 50 hours US$7,000; Custom 100 hours US$12,500; Pro 200 hours US$25,000. New customers get 15% off the first pack only: US$493, US$3,060, US$5,950, US$10,625, and US$21,250.

    odoo.comChecked true
  8. Success Packs include a dedicated consultant for project management, email and phone support, training and coaching, and configuration. Data-import assistance, onsite consulting, app customization, developments, and performance work are not on every pack. Onsite travel is billed separately. Extra monthly charges apply for maintenance of extra modules or lines of code. Performance issues require a pack of at least 50 hours.

    odoo.comChecked true
  9. Odoo states a 98% implementation success rate with a Success Pack versus 65% without one, and that 80% of projects within the estimator's scope go to production in 200 hours or less. The estimator displayed an example project cost of EUR 4,500 before a 15% new-customer discount.

    odoo.comChecked true
  10. Odoo 20.0 release notes are dated September 2026. Odoo 19.0 release notes are dated September 2025.

    odoo.comChecked true
  11. Standard support lasts the first three years after a major release. End dates: Odoo 20.0 September 2029 (planned), 19.0 September 2028 (planned), 18.0 September 2027 (planned), 17.0 September 2026, 16.0 September 2025. Extended support is an extra fee, only on Odoo.sh for a limited number of versions and on-premise for any version. SaaS minor versions ship every two to three months and are not eligible for extended support.

    odoo.comChecked true
  12. Enterprise Subscription Agreement version 13, dated 24 September 2026: Covered Versions are the three most recently released major versions, with a new major once per year. A database older than the Covered Versions can incur a fee equal to 25% of the annualized price, once per year and no earlier than six months after a new major release. On renewal, charges can increase by up to 7% per year of the previous term if prior charges (excluding that fee) are below list. Bug-fix handling starts within 2 business days. Unlimited tickets cover bugs and guidance on standard features and Covered Extra Modules. Development questions need a separate services agreement. The agreement does not warrant compliance with any local or international law.

    odoo.comChecked true
  13. Partners may not offer services on Odoo Enterprise to customers without an Enterprise subscription, including during implementation. Ready: 10 net-new Enterprise users and 1 certified employee in the last 12 months. Silver: 75 users, 3 certified employees, 70% retention. Gold: 300 users, 6 certified employees, 80% retention. Certifications must be on at least one of the three latest versions.

    odoo.comChecked true
  14. Odoo Online cloud SLA targets 99.9% monthly uptime (about 45 minutes of unplanned downtime), excluding planned maintenance. Regions: Europe, Americas, Asia-Pacific, Middle East and Northern Asia, and Oceania. Backups: 14 full backups over at least 3 months, replicated in Europe and Canada. Customers cannot choose or restrict backup regions. Single-server objectives: RPO 24 hours (near zero for SaaS) and RTO 6 hours. Odoo says these objectives are not legally binding guarantees.

    odoo.comChecked true
  15. Canada localization (l10n_ca): Canadian chart of accounts, reports, and default fiscal positions for every province and territory plus International. Tax follows the delivery province. Avalara AvaTax is available in Canada and the United States. Canadian vendor EFT uses CPA005 via l10n_ca_payment_cpa005.

    odoo.comChecked true
  16. United States localization follows US GAAP as described by Odoo, with modules for the chart of accounts, check printing, NACHA ACH files, 1099 CSV export, AvaTax, and US payroll. The 1099 report is a CSV for e-filing through a third party, not a direct IRS filing from Odoo.

    odoo.comChecked true
  17. Posted entries block switching the fiscal localization package. Country fiscal localizations still have to be configured.

    odoo.comChecked true
  18. Community is the LGPLv3 core. Enterprise adds functional support, upgrades, and hosting. Install paths include Odoo Online, packaged installers, and source install, plus a Docker image. Switching Community to Enterprise is documented except for a source install.

    odoo.comChecked true
  19. Cybrosys publishes timeline bands of 1 to 2 weeks for a basic setup, 1 to 3 months for a mid-level multi-module project with migration and training, and more than 3 months for a complex multi-module, multi-entity rollout. Its FAQ says packages start from US$999 for a basic setup.

    cybrosys.comChecked true
  20. A testimonial published by Bista quotes Duff Jones of Trearc, Inc. (Tennessee) on a project within a 9-month period from ERP planning to go-live, and quotes Dennis McCarthy, a CFO in Detroit, saying the implementation was within budget and on plan, without a dollar figure.

    bistasolutions.comChecked true
  21. Odoo's implementation methodology says experts should challenge the work at critical steps, frames gap analysis at about 10%, kick-off at about 5%, and implementation at about 80%, and says custom-development complexity grows with the square of the number of customizations. The project leader combines project management, analysis, and product knowledge. The customer single point of contact is a success factor. The guidance says to avoid importing unnecessary historical transactions.

    odoo.comChecked true
  22. Odoo Online uses intermediary SaaS versions that are not supported on Odoo.sh or on-premise.

    odoo.comChecked true
  23. Odoo.sh FAQ: Odoo SaaS versions are exclusive to Odoo Online and intermediate versions are not supported on Odoo.sh.

    odoo.shChecked true
  24. ERP hypercare is described as higher response and closer monitoring, with durations commonly cited from shorter windows on simpler systems to about 30 to 90 days on complex ERP rollouts.

    panorama-consulting.comChecked true
  25. Panorama Consulting: the biggest barrier to ERP adoption is habit. Under pressure, users default to what they know. Lasting change comes from rewiring routines, not training alone.

    panorama-consulting.comChecked true
  26. Over-customization is cited by implementers as a leading cause of Odoo implementation failure, including attempts to replicate legacy processes one for one.

    banibro.comChecked true
  27. A practitioner account identifies customization gridlock as a Year 2 failure mode, where heavily customized systems stay on old versions because upgrade retesting becomes too expensive.

    linkedin.comChecked true
  28. Odoo supports external LLM integration and no-code AI via server actions. ERP teams also use documentation search, automation, and analytics tools around implementation tasks.

    uncannycs.comChecked true

Frequently asked questions

Where can I get implementation services, and how much does it cost?

Odoo says companies under 50 employees usually buy Success Packs and implement with Odoo, companies over 50 usually use a partner for local project management, and companies over 250 should contact Odoo directly. As of October 2026, new-customer packs run from US$493 for 4 hours to US$21,250 for 200 hours, with 15% off the first pack only. A partner engagement is quoted on a statement of work. Flectic scopes that work for US and Canadian firms of about 20 to 100 people, with the timeline and a fixed price for each phase set in a written proposal.

How much does Odoo implementation cost?

Split the bill into the subscription and the services. As of October 2026 the US pricing page shows Standard at US$31.10 and US$38.90 per user per month, and Custom at US$61.00 and US$76.20, with the discount valid for 12 months on the initial users ordered. Services are the Success Pack prices, from US$493 to US$21,250 for a new customer's first pack, or a partner quote. One vendor, Cybrosys, advertises basic setups from US$999. That figure is not an itemized US or Canadian project. The pricing page we used shows US dollars, not Canadian dollars.

How long does Odoo implementation take?

Odoo says 80% of projects inside its estimator's scope go to production in 200 hours or less. One partner publishes bands of 1 to 2 weeks for a basic setup, 1 to 3 months for a mid-level multi-module project with migration and training, and more than 3 months for a complex multi-entity rollout. Calendar time runs longer than consultant hours because your team still cleans data and signs off. Flectic's Odoo industry packages run 8 to 28 weeks, and a first phase outside the packages gets its own timeline in the written scope. One Tennessee company, quoted by a partner, described 9 months from ERP planning to go-live.

What do the Success Packs include?

Each pack includes a dedicated consultant for project management, email and phone support, training and coaching, and configuration. Data-import assistance, onsite consulting, app customization, developments, and performance work are not on every pack. Onsite travel time and expenses are billed separately. Performance issues require a pack of at least 50 hours, and extra monthly charges apply for maintenance of extra modules or lines of code.

What is the difference between the standard plan and the custom plan?

Standard covers all apps on Odoo Online. As of October 2026 it is listed at US$31.10 and US$38.90 per user per month. Custom covers all apps on Odoo Online, Odoo.sh, or on-premise, and adds Studio, agentic AI, multi-company, and the external API, listed at US$61.00 and US$76.20 per user per month. The discount on the lower figure lasts 12 months for the initial users ordered. Odoo.sh hosting for custom developments is extra. No public worker, storage, or staging price was on the pages used for these rates, so confirm it on the order form.

How do you define a paying user?

A paying user is someone with backend access to create, view, or edit documents, or an employee record with no linked user. Portal users, such as customers and suppliers viewing invoices, are not paying users. Website visitors who place eCommerce orders are not paying users either. Count backend staff before you multiply the per-user rate. Leaving shop-floor people on a full user license is a common way to overstate the subscription.

What is a Light User?

A Light User is listed at US$8.90 and is quoted through an Odoo advisor. Odoo defines one as an active user designated Light User, or an active HR employee record not linked to an active non-portal user. Listed capabilities include that person's own time off, expenses, appraisals, attendances, referrals, and planning, plus field service, inventory barcode operator, read-only Knowledge, payslips, POS, and the manufacturing shop floor. Ten Light Users at the listed US$8.90 is US$89, arithmetic on the listed price. The advisor quote sets the billing term.

Which is better, Odoo Community or Odoo Enterprise?

Community is the LGPLv3 core. Enterprise is the licensed edition that adds functional support, upgrades, and hosting. Partners may not offer services on Enterprise unless that customer has an Enterprise subscription, including during implementation. A company that wants those upgrades, hosting, and a supported go-live is buying Enterprise. Community still needs configuration, import, and training, and those services sit outside the core license. Switching Community to Enterprise is documented, except for a source install.

Can you migrate data from our existing ERP or Excel?

Yes. Success Packs do not include data-import assistance on every pack, so confirm the hours cover your files. Bring master data and open items first. Odoo's methodology says to avoid importing historical transactions you do not need. Run a test import and reconcile the opening trial balance to the cutover date. Set the US or Canada fiscal localization before anyone posts, because posted entries block a later switch of that package.

What happens if the project scope changes mid-way?

Buy additional hours, or a larger pack, when configuration work grows. Custom development is outside standard support tickets, which cover bugs and guidance on standard features and Covered Extra Modules, and it needs a separate services agreement. Onsite days add travel time and expenses. If you add custom modules, budget the extra monthly maintenance charge Odoo lists for extra modules or lines of code. Write the change into the project plan before the hours are spent.

More on the blog: Choosing an ERP or CRM