Odoo 14 phase-out on Odoo.sh

Odoo.sh has blocked Odoo 14. Choose freedom.

Odoo.sh now blocks every database still on Odoo 14. Tell us where you stand and we will find the fastest way to get you running on servers you own.

  • Free migration

  • 100% data & code ownership

  • On-demand backups & restores

  • High availability

Get back up and running

Two minutes. An engineer replies within one business day.

You are

Already decided? Create your account

On Odoo.sh, the deadline is a lockout

Not a warning. A blocked database.

"When an Odoo version reaches 6 years of age, it is fully phased out from Odoo.sh on October 31 of that year. [...] any database still running a phased-out version will be permanently blocked, with no exceptions possible."
Odoo.sh FAQ, versions lifecycle
  • Blocked, with no exceptions

    Since October 31, 2026, Odoo 14 databases on Odoo.sh no longer work. There is no extension to ask for.

  • Upgrading under a deadline is risky

    Jumping several versions with custom modules in a few weeks is how upgrades break. Moving first takes the clock off.

  • It happens every year

    Odoo 15 is blocked on October 31, 2027, and Odoo 16 in 2028. On your own servers, you set the pace.

What you get

Move now. Upgrade when you are ready.

Free migration

We restore your Odoo 14 database, filestore and custom code onto your own server, from the backup you have. Later, we upgrade it to a supported version. Both are free.

100% data & code ownership

Your database lives on servers you own, your code in your own Git repository. Root access, your region, your provider. Nobody can block your Odoo on a deadline again.

On-demand backups & restores

Scheduled backups to storage you control, plus a backup whenever you want one. Restore any of them in a click, to production or to a staging copy.

High availability

Grow past one server: run several Odoo app nodes on one shared database, so a single machine going down does not take your business with it.

How it works

Off Odoo.sh first, upgraded on your schedule

  1. 01

    Create your account

    It takes a minute. Tell us what you run on Odoo.sh today.

  2. 02

    Connect your server

    Link a server you own, at the provider and in the region you choose, plus your Git repository.

  3. 03

    We move you, still on 14

    Database, filestore and code restored from your backup and tested. You keep working as before, on Odoo 14.

  4. 04

    Upgrade when ready, free

    We upgrade the database and port your modules on a staging instance. Production moves when your team signs off.

Partners welcome.

More migration. More customers. More revenue.

Have clients on Odoo 14 at Odoo.sh? Bring them over, keep the relationship, and run all their instances from one console on servers they own.

FAQ

Odoo 14 on Odoo.sh, answered

What happened on October 31, 2026?

Odoo.sh fully phased out Odoo 14. According to the Odoo.sh FAQ, any database still running a phased-out version is permanently blocked, with no exceptions possible. Odoo 14 installations on your own servers are not affected.

What is free?

Two things. Moving your Odoo 14 database, filestore and custom code from Odoo.sh to a server you own. And, when you are ready, upgrading that database and porting your custom modules to a supported Odoo version. We scope both with you before any work starts. Your servers are billed by your own provider.

Can we keep running Odoo 14 after the move?

Yes. CICDoo runs Odoo 11 through the latest release on your own servers, so nothing forces a rushed upgrade. Odoo 14 is no longer supported by Odoo, though, so we recommend planning the free upgrade once you are settled.

What does "100% data and code ownership" mean in practice?

The servers are yours, rented from the provider you choose in the region you choose, with root access. Your database, filestore and backups sit on infrastructure you control, and your code stays in your own Git repository. If you ever leave CICDoo, everything keeps running where it is.

How do backups and restores work?

Backups run on a schedule to storage you control, and you can take one on demand at any moment, for example right before an update. Any backup can be restored in a click, to production or to a staging copy for testing.

Do you support high availability?

Yes. A project can run several Odoo app nodes on one shared database, so losing one machine does not take Odoo down. We size the setup with you; most migrations start on a single server and grow into it.

Our Odoo 14 database is already blocked. Can you still help?

Tell us what you have. If you hold a recent backup of your database and filestore, or can still get one, we restore it on a server you own, still on Odoo 14, with your code from your Git repository. We say honestly during scoping what is possible.

Community or Enterprise?

Both. Enterprise customers keep their own Odoo Enterprise subscription; CICDoo does not resell Odoo licenses.

How much downtime should we expect?

Your Odoo.sh project stays live while we prepare and test the copy. The final switch is a short planned window, typically outside business hours.

We are on Odoo 15 or 16. Does this apply to us?

The same rule blocks Odoo 15 on Odoo.sh on October 31, 2027 and Odoo 16 on October 31, 2028. The offer is the same, and moving early means no deadline at all.

Your Odoo should not have an off switch.

Get your Odoo 14 running again for free, on servers nobody can block.

No per-seat fees. Your servers stay yours.