Source Database (read-only)
Read-only access for your migration. It cannot change a single row of the database you are leaving behind.
|
Access
Read only
|
Writes to your data
None, ever
|
Authentication
Your token only
|
Licence
LGPL-3
|
Install this module on the database you are leaving behind: the one that has served you faithfully for years. It holds every invoice you have issued, every customer conversation, every decision your business has recorded, and it has earned careful handling. So this module answers questions about your data, and cannot change a single row of the work you have done.
It cannot write. Not "does not": cannot.
Four properties, each one verifiable by you, without asking us for anything.
Your own database refuses writes
Every query this module runs is executed inside a PostgreSQL
READ ONLY transaction, so a write is refused by your database
server. The protection does not depend on our good intentions. Our tests
prove it at every endpoint, and you can run them against a copy of your
database yourself.
There is no login, anywhere
This module defines no user, changes no password, and accepts no credential other than the token you generate. It cannot be used to sign in to your system.
Nothing you send can become SQL
Table and column names are checked against your own catalogue; dates, limits and sort orders travel as bound parameters.
Every call lands in your own log
One line each: endpoint, outcome, duration, rows. Your sysadmin can read our entire activity in your logs, without asking us for anything.
The token is the only key
Open Settings > Odoo Migration Experts and press Generate Token. That creates a 46-character random key, and you paste it into the migration portal.
| Every token expires | 30 days by default, minimum 1. There is no "never expires": a key that never expires is a key you forget you gave out. |
| It is the only way in | Without it, every request is refused. |
| Regenerate at any time | The previous token stops working immediately. |
| Removal | Uninstall the module and the access ends with it. |
| 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, and it is short on
purpose: read it, or paste it into an LLM and ask "can this write to my
database?". The answer must be no, and you should not take our word for it.
You will also see this module on your new database: the destination connector builds on it. That is expected. Only the destination module can write, and only once it is armed.
When your migration is accepted, uninstall it. The database that carried you this far stays exactly as it was: still yours, still readable, still there.
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
|
| Technical Name |
odoomigrationexperts_database_source |
| License | LGPL-3 |
| Website | https://odoomigrationexperts.com |
Please log in to comment on this module