One Odoo baseline. Propagated, compared and kept current across your entire client fleet.
Dooplik isn't just a go-live tool. It's version control for your Odoo configuration: compare any instance against your reference, push a fix to one client or to ten, and absorb version upgrades without breaking everything.
Three steps, replayed at every signature.
External API credentials for the source instance and for the destination instance. Nothing to install on the Odoo side: Dooplik works only through the external API, which is what makes it usable on Odoo Online.
Dooplik reads both instances and shows you the gap: what is missing, what differs, what is already there. Push everything, or untick object by object. Save the selection as a preset for the next client.
The run executes in the background and respects Odoo's external API rate limit — expect a long operation, not an instant one. When it finishes, the report lists every object: created, updated, repaired, skipped, quarantined or failed.
Six problems you already know.
Dooplik compares installed modules on both sides and installs the missing ones on the target before propagating anything else. Skip that step and half your models and views have nowhere to land.
Every object is written with its XML ID and found again by it, and relational fields are remapped between databases through ir.model.data. Running the same propagation twice updates — it does not duplicate.
Odoo ships a minor version roughly every two months. Your source instance stays where it is while every destination instance is created on the current one: the gap widens by itself. Dooplik detects views the destination refuses to validate and repairs them before carrying on.
Untick a step, a model, a view. What is left becomes a reusable preset: the baseline shared by every client on one side, the per-client variations on the other. Presets are shared across the team from the Agence plan up.
Excel, PDF and JSON. Every object carries its status — created, updated, repaired, skipped, quarantined, failed — with Odoo's own error message where there is one. You know exactly what is left to do by hand before handing the instance over.
Credentials are encrypted at rest with AES-256-GCM under a per-account derived key, and are never copied to the target. Dooplik keeps no copy of the record content it moves. Hosted in the European Union.
What about the Studio ZIP export?
It is the first thing everyone tries, and it does help. Its limits are documented by Odoo — here they are, plainly.
| What has to happen | Studio export/import | Dooplik |
|---|---|---|
| Install the missing apps | No — the underlying modules are not added as dependencies. | Installs the module delta before propagating anything else. |
| Work across two different versions | No — the target must match the version, with the same apps already installed. | Works across the version gap and repairs the views the target rejects. |
| Carry over approval rules and automations | No — the ones tied to a user are not imported. | Propagates them and remaps their references to the target database. |
| Tell you what failed | No — the ZIP fails with no usable detail. | Object-by-object report, with the status and Odoo's own message. |
Studio export limits as documented by Odoo. Go and check them — we are not asking you to take our word for it.
We charge per go-live, not per seat.
A go-live is one configuration propagation to one target instance. Seats are unlimited on every paid plan, and comparing two instances stays free and unlimited on all of them.
Run a first real client go-live with Dooplik, no card required.
- 1 client go-live per month
- 1 target instance
- Unlimited instance comparison
- Missing apps installed on the target
- Excel audit report
- Logs kept for 7 days
- 1 seat
The pace of an integrator signing a few clients a month.
- 3 client go-lives per month
- 3 target instances
- Unlimited seats
- Object-by-object selection and reusable presets
- Data propagation (products, contacts, price lists…)
- PDF and JSON reports, scheduled runs
- 2FA, ticket support, read-only API
The pace of a practice that ships continuously.
- 10 client go-lives per month
- 15 target instances
- Unlimited seats
- Presets shared across the whole team
- Advanced comparison history
- Execution logs kept for a year
- Everything in the Studio plan
No quota to watch, and the tool wired into your pipeline.
- Unlimited client go-lives
- Unlimited target instances
- Unlimited seats
- SSO / SAML sign-in
- Full API and webhooks
- White-label reports
- Scheduled data propagation
The next client you sign, and every one after.
Create an account, connect your source instance, and start with the comparison: it is free, unlimited, and it never writes anything anywhere.
Create a free account