Odoo backups you can restore, download and move
Your live database and its files are saved every day. You don't set anything up. Put a backup back on any branch, download it as a normal Odoo file, or keep all your backups in your own storage.
Backups that run on their own
Daily production backups
Every production database is backed up once a day, with its files. You don't set anything up, and no day is skipped.
Backups you can count on for months
On paid plans, we keep every backup from the last 7 days. After that, we keep one backup a week for 3 months. That's about 19 points in time you can go back to.
Manual backups before a big change
Take a backup of any branch whenever you want, and add a note like "before the upgrade". Manual backups are kept for 90 days.
A copy before every update
Before your modules are updated, the database is copied. If the update fails, we put the copy back and your old code too. Your data is never left half done.
Every database, one by one
If one project runs many Odoo databases, each one gets its own backup. You can back up, restore or download one database or all of them.
Get your data back
Restore to any branch
Put any backup on any branch of the same project. You can copy production to staging to test with real data, or put an older backup on production to undo a mistake. A development branch works too, when you need to track down a bug.
A clear warning before you overwrite
A restore replaces the database on the branch you pick. When that branch is production, the dashboard warns you before you confirm.
Move your data in and out
Download any backup
Every backup downloads as a normal Odoo zip file, with the database and the files. Odoo makes the same kind of file, so it works anywhere Odoo runs. You're never locked in.
A safe copy for testing
When you download a copy, pick one of two kinds. An exact copy is your data as it is. A test copy has email, scheduled actions and live connections turned off, so it can't send anything by mistake. You can also leave the files out to get a smaller download.
Import a backup from any host
Upload a standard Odoo backup and restore it onto a branch. We read the Odoo version first. If we can't run that version, you get a clear message before anything is touched. Backups made on other hosts import as they are.
A step-by-step move from your old host
Our guide covers the whole move. It shows what to write down first and how to get a clean backup. Then you test on staging and switch your domain. It works for any host, or for a server you run yourself.
Keep your data where you want it
Your own backup storage
Send backups to your own Amazon S3 or Google Cloud Storage bucket, or to a folder on the server. A test button checks that your server can reach it. On AWS, the server can use its own role, so you don't need to store a key.
Use your own managed PostgreSQL
Run your Odoo databases on Amazon RDS, Google Cloud SQL, Azure or your own PostgreSQL cluster. You type the login on your server. It stays there, and we never see it.
Read-only access for your reports
Connect Power BI, Metabase, Grafana or a script to a branch's database. It can read, but it can't change anything. The link is encrypted, and it only works from the IP addresses you allow. Until you add one, it's all blocked. Limits stop a big report from slowing Odoo down.
Data that stays in one place
On your own server, your data, files and backups stay on machines you control. On our managed cloud, you pick the region. Your backups stay in that region too.
Where each feature works
Frequently asked
Can I leave with my data?
Are staging and development branches backed up?
How far back can I go?
My backup is bigger than 2 GB. Can I still move to your managed cloud?
Where are backups stored on your managed cloud?
I run my Odoo on my own server. Who looks after the backups?
Want to see how your backups would work?
Tell us where your Odoo runs today and how big it is. We'll show you how the backups, the restore and the move would work for you.