ERP migration guide
Odoo to Tellency Migration: Data & Cutover Guide
An Odoo-to-Tellency migration should begin with a fit assessment and a sample export. Decide what must move, what remains available as history and how the business will prove the new opening position is correct.
Written by Tellency · Reviewed October 24, 2026. This is a vendor-authored evaluation. Product editions, regional availability and commercial terms should be confirmed with each provider.
Plan a workflow demo →Inventory the actual Odoo implementation
Record the edition, hosting, installed apps, custom fields, custom modules and connected services. Assign an owner to each business process and integration. A standard export may not capture the meaning of a customised workflow, so collect examples of how staff actually use it.
Choose the history and open work to retain
Separate master data from transaction history and unfinished work. Customers, suppliers, products and account mappings are different migration objects from open orders, unpaid invoices, deposits and stock positions. Agree what is imported, what is archived and how staff will retrieve old evidence.
Map business meaning before file columns
Define units, locations, tax codes, price lists, document statuses and customer identifiers. Include duplicates and inactive records. Trial the mappings on a representative sample before estimating the remaining data work. Do not assume an exported field name means the same thing in both systems.
Reconcile the opening position
Compare trial balance, bank positions, receivable and payable ageing, stock quantities and inventory values. Resolve differences rather than carrying them into the new operation. The finance and stock owners should sign off the reconciled totals and the treatment of unfinished transactions.
Rebuild the integration and permission boundaries
For each connected website, app, payment service or reporting tool, name the record owner and transfer rules. Recreate roles and approval paths deliberately. Odoo’s current pricing distinguishes external API/customisation scope; record the actual source and target arrangements rather than assuming the old integration can be copied unchanged.
Cut over with a rehearsal and a fallback
Set a transaction freeze, final export, reconciliation sequence and decision owner. Rehearse a normal order and an exception in Tellency before go-live. Document the conditions that allow launch, the support route and the action to take if a critical check fails. Timescale and tooling follow the agreed scope.
Questions before you choose
Is there a universal one-click Odoo migration?
This guide does not promise one. The migration depends on the actual data, customisation, history and integration scope, and should be tested with sample exports.
What should be reconciled before going live?
At minimum, the agreed financial balances, receivables/payables, bank positions, stock quantities and values, plus unfinished orders and other committed work.
Official sources and review notes
Sources were reviewed on October 24, 2026. Vendor documentation describes capabilities; your proposal and configured demonstration establish the scope you purchase.