Moving from Odoo Online to your own server

Should you move at all?

Odoo Online is a good service. Odoo runs the servers, the backups and the upgrades, and you never think about PostgreSQL. If it does everything you need, staying is a perfectly sound choice.

Companies usually move to their own server for one of these reasons:

• Custom or community modules. Odoo Online does not run non-standard apps, such as your own Python modules or most modules from the Odoo Apps store and the OCA.
• Control over upgrades. On your own server, you decide when to move to a new major version, after testing it.
• Data location and access. You choose the cloud and region, and you can query the database directly for reporting.
• Performance and size. You choose the server size for heavy workloads or a large database.

If you need custom code but do not want to run servers, Odoo.sh is Odoo's own middle ground. Our article on Odoo.sh limitations helps you compare it with your own cloud.

Step 1: Check your Odoo version

Odoo Online runs Odoo's newest code, including intermediate releases such as 16.3 or 17.2 that are never published for self-hosting. According to Odoo's guide to changing hosting solution, these intermediate versions are not supported on Odoo.sh or on-premise. A database on one must first be upgraded to the next major version, waiting for its release if needed. For example, a database on 16.3 has to move to 17.0 first.

To see your version, open the database manager in your Odoo account and click the gear icon next to the database name. If it shows a major version, such as 18.0 or 19.0, you can move it as it is. If it shows an intermediate version, ask Odoo about upgrading to the next major version before you plan the move.

Step 2: Sort out your subscription

Every Odoo Online database runs Odoo Enterprise. To keep the same apps on your own server, you need an Enterprise plan that allows on-premise hosting. As of November 2026, that is Odoo's Custom plan; the Standard plan is for Odoo Online only.

If your database has an active subscription, Odoo's documentation asks you to contact your Customer Service Manager or Odoo support to transfer it. Do this early, so the new database can be registered on the day you move. Our guide to using your Odoo Enterprise subscription on your own servers explains registration and user counts.

You will also need the Enterprise source code for the same version. Odoo provides it through its download page, and gives Odoo partners access to the odoo/enterprise repository on GitHub.

Step 3: Prepare the new server

• Size it for your users. Two vCPUs and 4 to 8 GB of RAM suit a small team; see our Odoo server sizing guide for larger ones.
• Leave room on the disk for the database, the filestore and a few local backups. The filestore (attachments, images and documents) is often larger than the database itself.
• Install the exact major version your backup uses, with the Enterprise addons in the addons path.
• Set up HTTPS behind a reverse proxy, with Odoo's database manager turned off for the internet once the restore is done.

Step 4: Download the backup

In the Odoo Online database manager, use the gear icon next to the database to download a backup. The backup is a zip file with the database dump and the filestore, which is the standard format Odoo's database manager restores. Odoo's documentation notes that if the file is too large to download, you can contact Odoo support for it.

Download a test backup now, and plan to take a fresh one on moving day. Data entered in Odoo Online after your backup will not be on the new server.

Step 5: Restore and test

Restore the database

Restore the zip on the new server through Odoo's database manager, or with your hosting tool. When Odoo asks whether the database was moved or copied, choose moved for the real migration, so it keeps its identity. For a test restore, treat it as a copy, and do not let it email customers.

Test what Odoo Online did for you

• Sign in with a few real users and check their access rights.
• Studio customizations are stored in the database. Check your custom fields, views and automations.
• Scheduled actions such as recurring invoices and reminders run on the new server.
• Payment providers and connectors point back to the new address. Some need their webhook URL updated.
• Reports and PDFs print correctly, with the right fonts and layout.

Then install any custom or community modules you moved for, on a staging copy first. Our guide to Odoo staging environments explains why that copy matters.

Step 6: Replace what Odoo Online handled

On Odoo Online, several jobs were done for you. On your own server they are yours:

• Email. Odoo Online used Odoo's mail servers. Now you need an outgoing mail provider, SPF, DKIM and DMARC records and a way to receive replies. See configuring email for self-hosted Odoo.
• Backups. Set up daily backups of the database and filestore, with a copy off the server. See our Odoo backup strategy.
• Updates. Pull Odoo's fixes regularly, and test them on staging first.
• Monitoring. Watch uptime, disk, memory and failed backups.
• The domain. The yourcompany.odoo.com address stays with Odoo Online. Use your own domain, and update the base URL in Odoo's system parameters.

Step 7: Move day

1. Tell users when Odoo Online will stop accepting changes.
2. Download a final backup with the filestore.
3. Restore it on the new server as a moved database, and register it.
4. Point your domain at the new server and check HTTPS and the base URL.
5. Send and receive a test email, and confirm scheduled actions run.
6. Keep the Odoo Online database untouched for a while, in case you need it.

For a longer list of go-live checks, see our Odoo production hosting checklist.

Moving from Odoo Online with CloudPilot

CloudPilot does the server side of the move on your own cloud account or server:

• Create an instance from your backup. Upload the Odoo Online zip and CloudPilot restores the database and filestore, for Odoo 18, 19 or 20.
• Odoo Enterprise with your subscription code, using the Enterprise source from a connected GitHub account that has access to odoo/enterprise.
• A free subdomain with SSL to test on, then your own domain with a certificate issued and renewed for you.
• Staging copies with outgoing email and scheduled actions neutralized, and Git deploys for the custom modules you moved for.
• Daily backups with offsite copies, and monitoring with alerts.

See Move an existing Odoo database to CloudPilot for the steps, managed Odoo hosting for what CloudPilot looks after and pricing for each plan.

Moving from Odoo Online: questions