Tally or QuickBooks to Odoo: Migration Playbook

1. Inventory the source systems and obligations

List every source of business records, including spreadsheets, document folders and applications connected to the accounting system. Identify which source owns customers, products, invoices, payments and stock. Record export formats and limitations before selecting a migration date. Attachments stored in a separate portal may require a different extraction process from the ledger itself.

Ask finance and the relevant adviser what historical evidence must remain available and in what form. Do not discard history because it makes an import smaller. A readable archive can be appropriate, but only if users can retrieve the required records and relationships. Test the archive with an actual query, such as finding a prior-period invoice and the payment that settled it.

2. Choose the migration boundary deliberately

Decide whether the new system needs opening balances and open items, selected historical detail, or a wider transaction migration. Document why. Open customer invoices, supplier bills, unallocated payments and stock positions often need special attention because they continue to affect daily operations. The correct boundary depends on reporting, audit and operational needs rather than a universal rule to move everything or nothing.

Agree a cut-off date and how subsequent transactions will be captured. Define who can continue entering records in the old system during preparation and what changes must be re-exported. Without that rule, the rehearsal dataset and final dataset can differ in ways nobody tracks. Include the agreed boundary in the migration service scope.

3. Map fields and preserve stable references

Create a mapping sheet containing source field, target field, transformation rule, owner and sample value. Use stable identifiers to connect customers to invoices and products to movements. Do not rely on names alone: spelling variations and duplicate names are common enough to make an otherwise clean import ambiguous. Preserve source references where practical for investigation and reconciliation.

Odoo’s import documentation explains import testing and external identifiers for the documented version. Use the equivalent guidance for your target version and test the actual templates. Define date, currency, unit and tax-code conversions explicitly. A field that accepts text does not prove that the imported value has the intended accounting or operational meaning.

4. Clean data with accountable decisions

Separate technical formatting errors from business decisions. A duplicated separator in an address can be cleaned by a rule; deciding whether two supplier records represent the same legal entity needs an authorised owner. Maintain a change log and a reject list. Never fill unknown balances, tax identifiers or quantities with plausible values simply to make the import complete.

Prioritise active records and financially material exceptions, then work through the rest according to the agreed scope. Record unresolved issues with an owner and acceptance decision. If e-invoicing is part of the project, align cleanup with the invoice-data readiness checks so the same customer data is not cleaned twice against conflicting rules.

5. Reconcile balances and operational detail

After a trial import, reconcile the trial balance, receivables, payables and relevant bank balances. Review stock quantities and valuation using the agreed costing approach. Compare counts and values by entity and currency where applicable. An overall total can match while amounts are assigned to the wrong customer, so include sampled and exception-based detail checks.

Illustrative example: the old system shows AED 80,000 of customer receivables. The new total is also AED 80,000, but a credit note was assigned to a duplicate customer. The control total passes while collection work is wrong. Check ageing, document references and allocations, then have finance sign the reconciliation rather than accepting a successful import message as approval.

6. Rehearse real work and the cutover sequence

Ask users to perform a sale, purchase, return, payment and period-end review on the migrated test data. Include their real permissions and document outputs. Log defects and repeat affected scenarios after fixes. The rehearsal should include extraction, transformation, loading, reconciliation and user checks, with elapsed time recorded for each stage.

Use the measured rehearsal to choose the cutover window. A weekend may fit some projects, but it is not a promise for every database or business. Define the last point at which you can safely return to the old process, who makes that decision and how transactions created during the attempt will be handled. A backup alone is not a complete rollback plan.

7. Sign off, monitor and preserve the archive

At production cutover, freeze the agreed inputs, take the approved backups and follow the rehearsed sequence. Record reconciliations and the go/no-go decision. Give users a clear support route for the first operating days. Monitor rejected transactions, duplicate records and permission problems, and separate data corrections from requests to change the agreed workflow.

Retain the source exports, transformation rules, approvals and archive access instructions under appropriate security. Review the first reporting period with finance. If reconciliation or ownership keeps slipping, use the ERP project warning signs to escalate early. Migration is complete when the evidence and operating handover are accepted, not when the final upload finishes.

A practical reconciliation evidence pack

Keep one indexed folder for each rehearsal and the final cutover. Include the source export date, mapping version, imported record counts, rejected rows, balance comparisons and finance approval. Preserve an explanation for intentional differences such as records deliberately left in the archive. A reviewer should be able to establish which source snapshot produced the target data without asking the person who ran the import to remember the sequence.

For outstanding items, compare both the control account and the ageing detail. For stock, keep quantity comparisons separate from value comparisons and document any approved valuation method differences. For attachments, check a sample of links after the migration rather than counting files alone. Define who closes every discrepancy and what evidence is required. If a difference is accepted temporarily, state its business effect and deadline. Never turn a reconciliation into a cosmetic exercise by posting an unexplained balancing entry merely to make the totals agree.

A checklist to use in your next review