Odoo Backup & Restore That Works with Odoo's Database Manager

Why This Matters

The old problem: OEC.sh used a custom backup format. It worked for internal restore operations, but if you downloaded a backup and tried to restore it through Odoo's built-in Database Manager at /web/database/restore, it would fail. The format was not compatible with odoo-bin db restore either.

That meant backups were locked into OEC.sh. You could not take a backup and open it in a standalone Odoo instance, hand it to a partner for testing, or import it from Odoo.sh without a manual conversion step. This update removes that limitation entirely.

What Changed

We now use Odoo's native odoo-bin db dump and odoo-bin db load commands. Backups are standard .zip files containing:

backup.zip
  ├── dump.sql          # Plain SQL format
  ├── filestore/        # Raw files (not compressed)
  └── manifest.json     # Odoo metadata: version, modules list

This is the exact same format that Odoo.sh and Odoo Online produce. Any tool that works with Odoo's native backups works with OEC.sh backups now.

What You Can Now Do

Restore backups via Odoo DB Manager interface (/web/database/restore)
Import backups from Odoo.sh or Odoo Online directly — zero conversion needed
Move environments between OEC.sh servers without format changes
Download a backup and open it in any standalone Odoo instance

Migrating from Odoo.sh? Three Steps.

If you are moving from Odoo.sh to OEC.sh, the backup is already in the right format. No conversion, no reformatting, no third-party tools.

Download your backup from Odoo.sh

Go to your Odoo.sh project, select the branch, and download the backup. It is already in native Odoo ZIP format.

Upload to OEC.sh

In the OEC.sh dashboard, navigate to your project and upload the backup file.

Select environment and restore

Choose the target environment and click Restore. OEC.sh detects the format automatically and restores the database and filestore.

That's it. The format is already compatible.

50% Faster Backups

Beyond the format change, we also redesigned how backup data moves from your server to cloud storage.

OLDDouble transfer

VM  ──▸  Platform server  ──▸  Cloud storage
         (2x transfer, 2x bandwidth, temporary storage on platform)

NEWDirect upload

VM  ──▸  Cloud storage (direct via presigned URL)
         (1x transfer, zero platform bottleneck)

Result: Approximately 50% faster backup transfers. Zero platform bottleneck. No temporary storage on the platform server. The platform is now a pure orchestrator — it sends SSH commands and presigned URLs but never touches customer data.

Pre-Restore Safety Net

Restoring a backup replaces your current database. That is irreversible if you do not have a snapshot of what was there before.

Before any restore operation, OEC.sh automatically takes a snapshot of the current database. If the restore breaks something or you need to roll back, your previous state is one click away. No manual backup-before-restore needed.

This applies to all restore operations — whether you are restoring from an automated backup, uploading a file from Odoo.sh, or moving an environment between servers.

Backward Compatible

Old backups in cloud storage still work. The system auto-detects the format when restoring:

odoo_native

New format

dump.sql + filestore/ directory inside a standard ZIP

oecsh_legacy

Old format

pg_dump custom format (-Fc) + filestore.tar.gz

dump_only

DB dump only

Database dump without filestore (for lightweight snapshots)

No migration of existing backups is needed. All new backups are created in the native Odoo format. Old backups remain restorable as-is.

Try Native Backups

Odoo-native backup format, direct Odoo.sh import, 50% faster transfers, and automatic pre-restore snapshots. Available on all OEC.sh plans.

Start for free Backup & recovery guide

Frequently Asked Questions

Can I restore an Odoo.sh backup on OEC.sh?

Yes. Odoo.sh produces backups in the same native ZIP format that OEC.sh now uses. Download your backup from Odoo.sh, upload it to OEC.sh, select the target environment, and restore. No conversion or reformatting is needed.

Are old OEC.sh backups still compatible?

Yes. The system auto-detects the backup format. Old backups using the legacy format (pg_dump custom format + filestore.tar.gz) continue to work without any migration. New backups are created in the native Odoo format going forward.

Does OEC.sh backup the filestore too?

Yes. Every backup includes both the PostgreSQL database dump (dump.sql in plain SQL format) and the complete filestore directory containing all uploaded files, attachments, and assets. The filestore is included as raw files, not compressed, inside the ZIP archive.

How often does OEC.sh create backups?

OEC.sh creates automated daily backups for all environments. You can also trigger manual backups at any time from the dashboard. Backup retention depends on your plan and cloud storage configuration.

Can I download my backup and restore it locally?

Yes. Download the backup ZIP from OEC.sh, then restore it using Odoo’s built-in Database Manager at /web/database/restore, or use the odoo-bin command line tool. The format is standard Odoo native — it works with any Odoo instance running the same major version.

OEC.sh Backups Now Use Odoo's Native Format