The part you should ask about
You're handing us your whole business. Here's how we treat it.
An Odoo backup contains your customers, invoices, prices, and history — everything. If a company asks you to send that over, you should expect a straight answer about what happens to it. This is ours.
In 20 seconds
Private expiring upload links · EU object storage · no production passwords · used only for your quote and upgrade · no AI training · deleted on a published schedule
In transit
Files go from your browser straight into protected EU object storage over a private, time-limited upload link — encrypted in transit, never routed through an email inbox or our website function, and never placed on the public web. Large backups upload in chunks; nothing changes about the handling.
At rest
Your backup and code sit in protected EU storage. Access is limited to authorised people doing your quote and upgrade and the infrastructure providers needed to run the service. We do not use an offshore development team. The current infrastructure list is on our Subprocessors page.
What we use it for
Two things: preparing your quote, and performing your upgrade. That's the whole list. Your data isn't mined, benchmarked, shared, or used to train anything.
When it's deleted
Quote-only files are normally deleted within 30 days after the quote expires or is declined. After paid delivery, project files are deleted within 30 days after confirmed download or within 60 days after delivery, whichever occurs first. We don't keep a database copy around "just in case." Legal and accounting records do not include the project database and follow their required retention periods.
Where it's processed
Project files are stored and worked on in the European Union. Finnish company · EU processing · DPA incorporated into every Order · named subprocessors. Our Data Processing Agreement also includes global transfer terms and applicable US state processor restrictions.
What we never ask for
Live passwords, or access to your production server. We work from a backup — your running system stays untouched, and only you decide when the upgraded version goes live.
For your IT person or Odoo partner
The technical validator in your organisation can check everything independently:
- What's needed: a quick estimate only needs your current version, target version, approximate module count, and work email. A committed fixed price requires a database copy (
.ziporpg_dump) and your custom addons folder so we can inspect the system before issuing the written scope. - How uploads are handled: chunked, direct-to-EU-object-storage over private expiring links — never through email or our website function.
- What the analyzer reports: the free pre-migration analyzer runs locally (nothing phones home) and reports module counts, custom vs OCA/vendor code, and JS/POS/website/stock risk flags.
- What verification looks like: every project ships with a reconciliation report — see a sample verification report.
- Production boundary: we work only on copies and never access or deploy to production. The go-live decision and execution stay with you.
- What you receive: the migrated database, the ported addons, the verification report, and plain go-live instructions written for whoever runs your system — with an optional scheduled final run.
- What stays yours: the production deployment, DNS/hosting changes, and anything created in the live system after the supplied backup.
Questions your IT or compliance people want answered?
Put us in touch directly: support@odooupgradedone.com. Straight answers, no runaround.
Ready when you are
Your current version, target version, approximate custom-module count, and work email are enough for a quick estimate. For the committed fixed price, upload both the database copy and addons through the protected portal.
Get an estimate