Odoo support, hosting and upgrades: Your Odoo. Your server. Your code. Your data.
Our job is to keep it running. We take over, host, support and upgrade Odoo for businesses of every size. People who know Odoo do the thinking. AI agents do the legwork under their review. You own your server, your code and your backups, and you can leave with thirty days' notice.
Only need the upgrade? We take you to Odoo 19, or to Odoo 19 Community with no Enterprise license, as a one-off project with no subscription, hand everything over, and step away. Upgrade, then go.
Free-service drawing: every submission on this site through November 30, 2026 enters your business. No purchase needed. Grand prize: 12 months of Managed Odoo fees waived. Rules
Or call us: +1 515-644-1400, any time. How to start.
What you own from day one
-
The serverA Hetzner Cloud project in your company's name. We work in it with an API token you can delete, never as the owner.
-
The codeA git repository you control, with every custom module and every change committed and attributed.
-
The backupsNightly database and filestore copies to a Backblaze B2 bucket you hold the keys to. Restores are tested, not assumed.
-
The billsHetzner and Backblaze bill you directly, at their prices, with no markup from us. Leave us and nothing moves: your system keeps running, except that Allodi Print goes back to Odoo's standard PDF download, and our fee stops after 30 days' notice.
-
The credentialsRoot access, database password, mail and integration secrets, documented and stored in your own vault.
-
The exitMonth-to-month retainer. If you leave, or if we are ever unavailable, everything above keeps working without us. The one exception is Allodi Print: printing goes back to Odoo's standard PDF download. On the way out we hand over a final backup and the credentials we created, and remove our access, within ten business days at no charge (what happens then).
The problems are not exotic. They are the same six, over and over.
We read a year of public Odoo user discussion before starting this company. The complaints cluster tightly, and none of them are about Odoo being a bad product.
-
The partner holds the keys
Code repository, hosting account and passwords sit with the implementer. Leaving means starting over, so the price of staying keeps going up.
-
Upgrades that re-do everything
Each major version, custom modules have to be ported by hand. The quote to do it is often a second implementation, so people stay on old versions and pay surcharges instead.
-
Hosted plans that keep changing
Odoo's subscription terms change from time to time, databases on older versions carry a surcharge, and Python-based customizations on Odoo Online are now billed by lines of code. Budgeting is hard when the terms move.
-
Bank reconciliation that never balances
Feeds drop, statements import twice, receivables show money that was collected months ago. The books are technically in Odoo and practically in a spreadsheet.
-
Email that quietly stops
Outgoing mail fails and nothing tells you. Quotes, invoices and purchase orders sit unsent until a customer or vendor calls.
-
Hosting you cannot reach
On Odoo.sh, staging databases are deleted after a month, the server's IP address can change, and scheduled actions run no more often than every five minutes. Slow pages get blamed on hosting when the fix is a missing index.
Sources, as of September 2026: Odoo.sh branches and backups (staging databases deleted after one month), Odoo.sh FAQ (IP address changes), Odoo.sh advanced (scheduled actions, submodules) (scheduled actions no more often than every five minutes), Odoo Enterprise Subscription Agreement (25% extra fee on older versions, Python-based customizations billed per 100 lines of code). Odoo changes its terms and documentation from time to time; the linked pages are the current word.
Four things we do
Each one has a defined scope, a defined deliverable and a defined end. Details, deliverables and timeframes are on the services page.
-
Rescue and rehost
For companies leaving a partner, Odoo Online or Odoo.sh.
We move your database, filestore and custom code onto a cloud server your company owns, with tested backups, documented integrations and the credentials we create handed to you. One-time fee.
- Fee
- $750 per database, in three milestones (see pricing)
- Typical length
- Two to six weeks depending on size, including parallel testing
- You end up with
- A server, a repo, a backup bucket and a runbook, all in your name
-
Managed Odoo
For companies that want someone on the hook every month.
Hosting operations, nightly backups to Backblaze B2 with a missed-backup alarm, security patches and a block of small-fix hours. Month to month.
- Fee
- $75 a month plus $15 per internal user (see pricing)
- Response
- Server down or data at risk: within 1 business hour, or within 1 hour at any time with the optional 24/7 add-on. Small fixes are usually done in days, not weeks.
- Commitment
- None. Cancel with thirty days' notice
-
Upgrade to Odoo 19 and de-Enterprise
For companies on any earlier version of Odoo, back to Odoo 8, with custom modules and a licensing bill they would rather not have.
A fixed-scope project that ports your custom modules to Odoo 19, replaces Enterprise-only apps with OCA equivalents where you want them, and rehearses the upgrade on a copy until it is boring.
Odoo 20 is now available. New major versions usually need a few months of fixes before they are ready for day-to-day business, so today we recommend Odoo 19 for production and plan moves to 20 once it has matured. As of September 30, 2026, Odoo's own upgrade service does not offer 20 yet; Odoo's September 2026 announcement to its customers expects it by the end of November 2026. From 19, that later step is a short one.
- Fee
- Published price from your module count (see pricing)
- Typical length
- Four to twelve weeks depending on module count.
- Result
- Odoo 19 Community today, or 20 once it has matured, on your own server. Enterprise if you keep it
- Commitment
- None. No subscription needed: take the handover and go (upgrade, then go)
-
Customization cleanup
For companies whose Odoo has grown years of Studio fields, half-used custom modules and automations nobody remembers setting up.
We inventory every customization in your system, find what is unused, broken, duplicated or risky, and hand you a keep, fix, consolidate or remove plan. Then we carry it out on a copy first, and on production with your approval. You end up with a smaller system you understand, and a much cheaper next upgrade.
- Fee
- Published tiers, set by the number of customizations the free scan finds (see pricing)
- Typical length
- Two to six weeks
- You end up with
- A documented, smaller, upgrade-ready system
Use us to get to Odoo 19, then be gone.
An upgrade to Odoo 19, or a move from Enterprise to Odoo 19 Community with no Enterprise license to renew, is a one-off project. It does not need a Managed Odoo subscription, before or after.
You pay a fixed price from the published tables, set by the free scan's counts: by custom modules to port, none: $0, 1 to 5: $750, 6 to 15: $2,000, 16 to 40: $4,500, over 40: $4,500 plus $100 per module over 40; plus $500 per major version jumped and $250 per Enterprise app replaced. It is billed 30% at start, 40% at staging sign-off and 30% at completion, and the project fees in the scan's quote are binding for what the scan counts.
The upgrade is rehearsed on copies of your database until it runs clean, your team signs off on a staging copy, and production is upgraded on one scheduled night with a rollback point. If your Odoo is on Odoo Online or Odoo.sh today, the move to your own server is a separate one-off project, also without a subscription, done before or after the upgrade.
At acceptance you get every ported module in your repository with full source, licensed to you under LGPL-3, the upgrade script that ran on the night, and the handover: the credentials we created, a backup test report, the runbook, the integrations sheet and a list of who has access to what. Defects you report in the portal within 14 days of acceptance are fixed at no charge. Then we remove our access to your server, repository and backups and confirm it in writing, unless you ask us to keep it.
After that, running the server is up to you or whoever you choose. Managed Odoo is there if you want it later; it is never a condition. How an upgrade-only project ends.
How to start, without a sales call
Every step is online, and we are a phone call away at +1 515-644-1400 if you would rather talk.
-
Get your price
Enter your companies and users in the calculator. Plans, add-ons and hourly rates are published, so the number on screen is the one we quote from. This step is optional and needs no name or email.
-
Run the free scan
The read-only scan confirms the counts and changes nothing. You run the scan file yourself, or upload a backup and we run it. You give your contact details when you send the result file or ask for the upload link. A person at Allodi sends your quote from the published prices; its one-time project fees are binding for what the scan counts, and it holds for 30 days.
-
Sign and pay online
Read every contract document on the quote page, sign, and pay the first payment only, by card or bank.
-
Onboarding begins
Your welcome email, portal login and onboarding ticket arrive once you have signed and any payment due at signing is made or under way. Most moves take two to six weeks from signing to cutover, depending on size, and the cutover itself is one evening you pick.
Every step, your first weeks on a move, and what protects you
Why a small fix takes hours here and weeks elsewhere
Most Odoo support requests are small: a report column, a field that should be required, a workflow email that fires at the wrong time, a bank statement that will not import. The work is not hard. The waiting is.
When you open a ticket, a person at Allodi works it with an AI agent that reads your database and code and prepares a proposed change, tried on a copy first. The person reviews it, and only then is the change applied, logged and reported back to you. Outside a short list of pre-approved routine actions, nothing is changed without that approval, and code deployments, money, tax, user access and security settings, messages sent from your Odoo, and migrations or restores of production always go to a person first. Read the full approval flow.
Who we work best with
A good fit
- Companies of any size running Odoo, usually in manufacturing, distribution, retail, construction or services. Pricing scales per user and per company.
- Already live on Odoo, Community or Enterprise, on Odoo.sh, a partner's server or your own, or on a major version of Odoo Online. We host and support Odoo 16 or later as it is, and upgrade from any earlier version, including Odoo 8. We move you onto a server in your name.
- Owners and finance or operations leads who want to own their system and understand what is being done to it.
- Anywhere in the world, except where sanctions apply. EU/EEA, UK and Swiss businesses are also covered by our data processing agreement.
Often better served elsewhere
- First-time implementations that need process design, training and change management across departments. A full-service implementation partner fits better, and we are glad to recommend one.
- Consumers and sole traders outside the US. We work with registered businesses.
- Anyone looking for AI to run their books unattended. Every change we make has a person behind it.
Who you are dealing with
Allodi is a product of KEIGHT LLC, based in Des Moines, Iowa. Mark Kladivo started it inside Corn Belt Aluminum, the Iowa manufacturer he owns, which runs on Odoo 18, on infrastructure it manages itself, and is moving to Odoo 19 Community: the same project we sell. Before that, Mark and Lisa Kladivo ran pcCentral, a desktop hosting company, for fifteen years, with more than 5,000 users, until it was sold in 2018.
Changes to a customer's system outside a short list of pre-approved routine actions need approval from a named person at Allodi, and so, always, does anything that deploys code, touches money, tax, user access or security settings, sends messages from your Odoo, or migrates or restores production. Today that person is Mark Kladivo. The first conversation is with a person who works on Odoo, not a sales desk.
Who runs Allodi. Case study: the manufacturer Allodi was built in.
Start from where your Odoo is today
Plain guides to the situations we are asked about most. Each one lists the caveats, the steps and the published price.
- Leaving Odoo.sh: the migration checklist, from your GitHub repository to cutover evening.
- Migrating from Odoo Online to a server you own, and the intermediate-version limit to check first.
- Odoo.sh vs self-hosted cost, worked out with published prices for three company sizes.
- Odoo hosting on a server your company owns, with backups you hold the keys to.
- Odoo support in Des Moines, Iowa, for the Midwest and the rest of the US.
- Odoo Enterprise to Community migration, app by app, rehearsed on a copy.
- Upgrading to Odoo 19, Community or Enterprise, with your custom modules ported.
- Switching Odoo partners, and what to hold before you tell them.
- Rescuing a stalled or failed Odoo project, starting with your own data and code.
- The free, read-only Odoo database scan, which turns your counts into a quote from the published prices.
Start with your price
Enter your companies and users and your price is on screen. Send it to us from the same page, or start the free scan today.
- Plans, add-ons and hourly rates are published; larger projects are quoted up front, and the project fees in the free scan's quote are binding for what the scan counts.
- On a move, the start milestone is refunded if your database cannot run on the new server, unless the cause is on your side or a third party refuses to release your data (conditions).
- Managed Odoo is month to month: thirty days' notice, no minimum term.
- Your server, code, backups and credentials are in your company's name.
Or call us: +1 515-644-1400, any time. How to start.