Moving from Tally to Odoo is less a data-copy job than a decision about how the business will run afterwards. The data part is manageable: Tally exports cleanly and Odoo imports it. The harder part is deciding what to bring across, what to leave behind and when to switch. This guide sets out what normally moves, what has to be rebuilt, and how to run the changeover without stopping billing.

Short answer. Masters (ledgers, parties, stock items) and opening balances move across. Open invoices and bills move across so collections and payments continue. Old voucher history usually stays in Tally as a read-only archive. Reports, print formats, approvals and user roles are rebuilt in Odoo, not copied.

First, are you sure you need to move?

Many businesses that think they need an ERP only need to see Tally data in more places. If accounts and stock are fine and the complaint is "I can't see it from my phone", read how to see Tally data outside Tally first. Migration makes sense when orders, purchase, production, dispatch or approvals are handled in WhatsApp and spreadsheets, and Tally only records the result. Our Tally vs Odoo guide covers that decision.

What normally moves from Tally to Odoo

Tally dataIn OdooHow it usually travels
Chart of accounts (ledgers and groups)Chart of accountsExport, map Tally groups to Odoo account types, import
Customers and suppliers (sundry debtors / creditors)Contacts with GSTIN, address, payment termsExport, clean duplicates and missing GSTINs, import
Stock items, units, groupsProducts, units of measure, categoriesExport, map HSN codes and units, import
Closing balancesOpening balances at the cut-over dateTrial balance as of the last day in Tally, posted as an opening entry
Outstanding billsOpen invoices and vendor billsBill-wise outstanding list imported so receipts match later
Closing stockOpening stock quantities and valuesStock summary at cut-over, loaded as an inventory adjustment
Past vouchersUsually not importedKept in Tally as a read-only archive for audit

What you rebuild instead of copy

  • Reports. Tally's day book, outstanding and stock reports do not carry over. Odoo has its own reports, and any custom TDL report needs an equivalent built.
  • Invoice and print formats. Your GST invoice layout, letterhead and terms are set up again in Odoo.
  • Users and rights. Decide who creates, who approves and who only views. Odoo makes this explicit, which most Tally setups never did.
  • Workflows. Quotation to order to delivery to invoice is where Odoo earns its keep, and it has to be configured to match how you really work.

A sensible order of work

  1. Pick a cut-over date at a month end or, better, a financial-year boundary, so opening balances are clean.
  2. Clean Tally first. Duplicate ledgers, parties without GSTIN and unused stock items are cheaper to fix before export than after import.
  3. Configure Odoo for your company, GST, chart of accounts, warehouses and approval flow before loading data.
  4. Import in a test database and compare the trial balance, receivables and stock value with Tally. They must match to the rupee.
  5. Train the users on a copy, using your own invoices and parties.
  6. Go live, then reconcile the first month with your chartered accountant before closing Tally for new entries.

Where migrations go wrong

  • Trying to import every historic voucher, which multiplies the clean-up and adds little value.
  • No fixed cut-over date, so the team posts in both systems and the books drift apart.
  • Skipping the test import, then finding the receivables don't match on day one.
  • Leaving out the person who actually does the daily Tally entry. They know where the data is untidy.

Odoo implementation and Tally migration in Ambattur, Chennai

We are in SIDCO Industrial Estate, Ambattur, and the same team handles Tally integration, hosting and your website, so Odoo, the server and the data sit with one accountable team. Bring a sample Tally export and we will tell you what moves cleanly.

Call +91 99620 05753  •  Email prakash@salasar.tech
Salasar Technologies, 58, 3rd Street, EB Road, North Phase, Pattaravakkam, SIDCO Industrial Estate, Ambattur, Chennai 600098

Send Us a Tally Export Sample
FAQs

Tally to Odoo Migration — Common Questions

1. Can I migrate my Tally data to Odoo?

Yes. Tally can export masters (ledgers, parties, stock items) and transactions to Excel, CSV or XML, and Odoo can import them after they are cleaned and mapped. In most projects the masters and opening balances are imported, and the old transaction history stays in Tally as an archive rather than being replayed voucher by voucher.

2. Do I have to move all my past vouchers into Odoo?

Usually not. The common approach is to import closing balances as opening balances on a clear cut-over date, import open invoices and bills so receivables and payables carry forward, and keep the old Tally company data read-only for audit and reference.

3. Can Tally and Odoo run side by side?

Yes, for a short parallel run. Some businesses keep posting in Tally while the team learns Odoo, then compare month-end figures before switching. It costs extra effort, so keep the overlap short and set a firm cut-over date.

4. Will Odoo handle GST the way Tally does?

Odoo has an India localisation with GST taxes, HSN codes and GST returns support. It still has to be configured for your tax setup, and your chartered accountant should check the first month's figures against what you would have filed from Tally.

5. Is migrating to Odoo better than adding a dashboard on top of Tally?

Only if the problem is the workflow, such as orders, purchase, production and dispatch handled outside Tally. If Tally handles accounts and stock well and you only need to see the numbers elsewhere, a read-only dashboard is cheaper and less disruptive.

6. Who can do a Tally to Odoo migration in Chennai?

Salasar Technologies, in SIDCO Industrial Estate, Ambattur, does Odoo implementation, Tally integration, hosting and website work as one team. Call +91 99620 05753 to discuss your Tally data and what you want Odoo to do.