Inventory the environment and functions
Identify the Odoo version, hosting method, apps, customisations, companies, and currencies. Write what you will migrate and what stays in archive, and assign an owner for each data set.
Migrating to TenXshift
From Odoo to connected work.
With a plan you can verify.
A suggested migration plan reviewed with your team before execution. Bulk-import tools are available; field, history, attachment, and integration scope needs technical matching.
Reference copy and export
Save a reference copy per your privileges and hosting method, and export the required data sets with their identifiers and relationships. Review Odoo documentation for your version; a backup is not a direct TenXshift import file.
Data-model mapping
Map parties, suppliers, employees, projects or analytic accounts, and funding lines to the target model. Turning a project or analytic account into a grant needs commercial interpretation and review — not just a rename.
Choose the finance starting point
Agree a cut-over date with finance: will full history move, or only balances and open commitments? Define which purchase documents, payments, and grants continue after migration.
Trial a linked sample
Start with reference data, then a grant and its lines, then linked transactions. Review fields, attachments, roles, and exceptions in a trial environment; do not copy Odoo customisations as if they were automatically available features.
Reconcile and departmental acceptance
Compare record counts, balances, currencies, grant lines, and open commitments. Spot-check relationship and report samples, and log differences and each department’s acceptance decision.
Cut-over and go-live
Define a window to freeze relevant changes, migrate last differences, then run a final verification. Keep Odoo as a read reference per agreement, with a decision owner and a clear rollback plan before you start.
When do we consider migration successful?
Go-live needs approval from data owners and departments — finishing an upload without an error message is not enough.
Data matches
Counts, balances, commitments, and relationships are reviewed against an agreed acceptance list, with differences handled.
Processes are runnable
A sample grant, purchase request, approval, and spend are reviewed through to reporting, with team roles tested.
Rollback plan is clear
The source of truth is retained, freeze boundaries are known, and the rollback decision-maker and handling of new transactions are predefined.
Official Odoo references · Details vary by version and hostingExport and import data — Odoo 19 ↗Managing backups in Odoo Online ↗
There is no automatic migration tool here, and no guarantee that all Odoo data will transfer. Duration, cost, and scope are set after a sample review and field mapping.