Moving off Odoo.sh — usually under an hour.
We accept your Odoo.sh backup, detect the version, restore on your chosen cloud, and cut DNS over. You keep the database, the filestore, and the addons. You stop renting the platform.
Four steps. No drama.
1. Assessment
You share an Odoo.sh backup (or grant temporary read access). We detect version, addons, filestore size, customisations, and any custom modules.
2. Restore
We provision the app on your chosen cloud (Hetzner / DigitalOcean / AWS / your existing server), restore the database + filestore, and run the standard post-restore checklist.
3. Verification
You log in to the restored instance and verify key workflows (login, sales/purchase, reporting, automations). Cron, scheduled actions and email are wired but pointed at staging until you cut over.
4. DNS cutover
You flip DNS. We monitor for the first 24 hours. Odoo.sh subscription stays live for 1–2 days as rollback safety, then cancels on your timeline.
What carries over (automatic)
- Database (full Postgres dump)
- Filestore (attachments, signed documents, images)
- OCA / community modules, including pinned versions
- Custom modules — copied verbatim, no rewrites required
- Scheduled actions, automations, server actions
- Email server config (SMTP / IMAP / fetchmail) — endpoints repointed
- Active users, password hashes, 2FA secrets
- Multi-company structure, access rights, record rules
- Translations and language packs
What changes (we'll tell you upfront)
- The hosting model — you now own the server, not rent the platform
- Backup storage moves to your chosen object-store (S3 / R2 / Hetzner Storage Box) with per-tenant encryption keys
- The dashboard URL — CloudWady has its own operator console; Odoo.sh's editor isn't recreated
- Built-in Odoo Editor / Studio output still works in the restored DB; the Odoo.sh-specific "shell" interface is replaced by SSH plus our operations console
- Some Odoo.sh-only environment variables are dropped (we keep the meaningful ones)
What we accept on the way in
Backup format
Standard Odoo backup ZIP (database + filestore) from any Odoo.sh staging or production branch. We also accept raw Postgres dumps + filestore tarballs if the ZIP export times out on large databases.
Versions
Odoo 14 through 19. Migrations across major versions are scoped separately — moving the platform first, upgrading second, keeps each step debuggable.
Sizes
Sub-1 GB databases typically restore in under 10 minutes. 10–50 GB takes 1–4 hours and is usually done after-hours. 50 GB+ we schedule a maintenance window and stream the filestore in parallel.
Cost
Odoo.sh charges per user + per worker on their infrastructure. BYOC means you pay the cloud provider's raw rate (typically €15–40/month at Hetzner for a small instance) plus a flat CloudWady platform fee. Most partners see a 60–80% reduction at steady-state.
Data residency
Odoo.sh runs in a small set of regions chosen by Odoo S.A. CloudWady BYOC lets you place the workload anywhere your provider has a region — EU-only, customer-specific, or your existing infrastructure.
Operational access
You get SSH on the server, root on the database, and full visibility into your deployments. Odoo.sh's "Editor" interface is intentionally restrictive; for partners managing many client tenancies, that's a permanent ceiling.
What we need from you
- The Odoo.sh project name and the branch you want to migrate (production vs staging)
- A choice of cloud region — or skip this and we'll suggest one based on your end-customer base
- DNS-record write access for the domain you plan to cut over (a one-time A-record / CNAME flip)
- One technical contact who can answer "is this customisation still used?" questions during the assessment phase
- 30 minutes for the cut-over window — usually after-hours or weekend
Migration questions
Can I keep Odoo.sh running in parallel?
Yes. We restore to a fresh hostname; you verify end-to-end, and only flip DNS when ready. Odoo.sh stays the source of truth until you say otherwise.
What about my custom modules?
They install on CloudWady the same way they did on Odoo.sh — from the Git repo you already have. We don't rewrite or vendor them.
What if my database is huge?
Above ~50 GB we schedule a parallel filestore stream while the DB restores. The full window is 4–8 hours; you stay on Odoo.sh until the second we cut over.
Can I roll back if something breaks?
Yes. Odoo.sh stays live for 1–2 days post-cutover. We monitor; if anything goes sideways, DNS flips back. We've never had to roll back, but the option exists.
Is the migration free?
For pilot partners during 2026-Q2: yes, operator-led migration is included in the onboarding. Self-serve migration is available from the dashboard for partners comfortable running the restore themselves.
What about email and SMTP?
Outbound SMTP, IMAP fetch, and bounce handling are all wired the same way — we copy the Mail Server records on restore. If you're on Odoo.sh's default mail service, you'll need to point us at your own SMTP (Mailgun, Postmark, Amazon SES, etc.) for the cut-over.
Ready to start the move?
Tell us about your Odoo.sh setup and we'll come back within one business day with a scoped migration plan. No commitment until you've seen the plan.