Destination Database
Write access for the new database only, and only once you arm it.
|
Install on
The NEW database
|
Writing
Off until you arm it
|
Authentication
Your token only
|
Licence
LGPL-3
|
Install this module on the database you are moving into, never on the one you are leaving behind. It adds the one thing a migration cannot do without: the ability to write your years of work into their new home. We know what we are being trusted with, so that ability is fenced in every way we could think of, and the fence is described below rather than hidden.
Writing stays off until you say so
One tick box, and it is yours, not ours.
Installed is not armed
Even with this module installed and a valid token, nothing can be written here until an administrator ticks "This database receives a migration" in Settings.
Why the box exists
If this module ever lands on the wrong database, or is left behind after a migration, an unticked box is what stands between a leaked token and your live data.
Off is safe, not useless
Reading keeps working while it is off, which is how a connection is checked before anyone commits to anything. Untick it once you accept the migration and the connector is disarmed without uninstalling anything.
The same key, the same limits
| Token | The same one the read endpoints require: 46 random characters, compared in constant time, refused once it expires and refused entirely while it is unset. |
| Logging | Every call is written to your own Odoo log: endpoint, outcome, duration, rows. |
| Two modules | Installing this also installs Source Database (read-only): the shared read endpoints and the Settings section live there. Two modules on your new database is the expected picture, and only this one can write. |
| Removal | Uninstall both modules once you accept the migration, and the access ends with them. |
| If your token stops working | A migration whose token is refused cannot continue, so we do not keep your data waiting for it: 48 hours after the refusal, the copy we downloaded is deleted automatically. Your migration and its report stay - only the data goes - so you generate a new token whenever you are ready and it starts again from a fresh download. Your own databases are never touched by any of this. |
Read it before you trust it
controllers/main.py is the entire surface, including the write
endpoint. We do not hide it: a migration writes to your new database, and you
should be able to see exactly how, and exactly how it is fenced.
A migration should feel like moving into a bigger house, not like handing someone the keys to the old one.
Support
| Found a bug, or something we should improve? | Open an issue at gitlab.com/omigrationexperts/ome-addons/-/issues. The code is public, so the reports are too: you can see what has been raised, what we fixed, and when. |
| A question about your own migration? | Write to info@odoomigrationexperts.com and a person answers. |
See what your migration looks like, free
A free analysis connects read-only, tells you plainly what your database holds, and quotes your migration. Nothing runs, nothing changes, and nothing is charged before you decide. Take your time: we would rather you were sure.
Start a free analysis| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Community Apps Dependencies | Show |
| Technical Name |
odoomigrationexperts_database_destination |
| License | LGPL-3 |
| Website | https://odoomigrationexperts.com |
Please log in to comment on this module