Tally to Odoo Migration: Cost, Timeline, and Data Scope

TallyPrime is excellent at vouchers and GST returns. The strain starts when stock, production, branches and sales teams need the same live numbers. Our Tally to Odoo migration service moves your books into a full ERP without starting from zero.

This guide is for owners, CFOs and accountants at Indian and GCC SMEs weighing Odoo vs Tally, or any Tally alternative, who want real numbers first. For the wider process across any source system, see our Odoo migration guide.

What data moves from Tally to Odoo, and what stays in Tally?

In a Tally to Odoo migration, masters and open balances move, structures like groups and godowns are mapped, and closed-year history usually stays in Tally. The table shows where each Tally item lands.

Tally item	Becomes in Odoo	Treatment
Ledger groups	Account types in the chart of accounts	Maps
General ledgers	Accounts in the chart of accounts	Maps, often fewer
Sundry debtors and creditors	Customers and vendors	Moves
Party GSTINs and states	GSTIN on each contact	Moves
Cost centers	Analytic accounts	Maps
Stock items and units	Products and units of measure	Moves
HSN/SAC codes	HSN/SAC code on each product	Moves
Godowns	Warehouses and stock locations	Maps
Company GST registrations	Company or branch with its own GSTIN	Maps
Opening balances	One opening journal entry at cutover	Moves
Open bills, bill by bill	Open customer invoices and vendor bills	Moves
Closed-year vouchers	Read-only Tally archive	Usually stays
TDL customizations	Odoo settings, Studio or a module	Rebuilt

Moving open bills one by one, not as a lump balance, lets your team collect and pay from Odoo on day one. Ledgers not kept bill by bill in Tally need their open invoices rebuilt.

Full voucher history can move too. It is the biggest driver of data migration cost, so decide it year by year.

Opening balances are where most teams get stuck. One Tally user on the Odoo forum asked how to set opening balances in Odoo and got only a pointer to another thread.

How do you export data from TallyPrime?

TallyPrime exports masters and vouchers natively in XML and Excel, and it can also share data with Excel or scripts through ODBC. Pick the method by what you are extracting.

Tally's export help says you can export accounting and inventory masters with ledger balances, and specific or all vouchers with dependent masters. Formats include Excel, XML, JSON, PDF and HTML.

• Masters: press Alt+E, choose Masters, and export ledgers, groups, stock items and godowns with their balances.
• Vouchers: press Alt+E, choose Transactions, and export the vouchers you need; XML keeps the voucher structure for scripted loading.
• Reports: open the trial balance, outstanding bills or stock summary and press Ctrl+E to export the current report for reconciliation.
• ODBC: enable ODBC in TallyPrime's client/server settings; Tally's guide notes the default port is 9000 and Excel can pull ledgers and stock items directly.

Export each financial year separately and keep the files as your audit trail.

How do you import Tally data into Odoo?

Odoo imports Excel or CSV files into almost any record, so Tally data loads through mapped spreadsheets or a script, tested first on a copy. The built-in importer is enough for most SME masters.

Odoo's import guide covers contacts, products, bank statements, journal entries and orders in .xlsx or .csv. Every import has a Test button that checks the file before anything is written.

• Use External IDs: carry Tally ledger and item names as External IDs, so invoices link to the right customer and product.
• Load in order: chart of accounts, taxes, contacts, products, then opening stock, open invoices and bills, and finally the opening entry.
• Split big files: Odoo's docs warn that large imports can time out and advise smaller batches.
• Script the history: multi-year vouchers usually load through a script or module reading Tally XML.

Odoo has no built-in Tally importer. Third-party connector apps exist, but when an Odoo 18 user asked for a Tally link on the forum, the accepted answer was no connector, manual only. Check what any connector really covers.

How does Odoo handle Indian GST after you leave Tally?

Odoo's India localization covers GST taxes, e-invoices, e-way bills, TDS and TCS alerts, GSTR-1 filing and GSTR-2B matching, so GST work moves into the ERP. You set it up once and test it before cutover.

According to Odoo's India localization docs, the main features are:

• e-Invoice: confirmed invoices go to the NIC e-invoice portal, and the PDF carries the IRN, acknowledgment number and QR code.
• E-way bill: created from an invoice, or from a receipt or delivery with the E-waybill Stock module.
• GSTR-1 and GSTR-2B: send GSTR-1 to the GST portal and fetch GSTR-2B to match against vendor bills.
• TDS and TCS: set a section on an account, and Odoo alerts you when an invoice or bill crosses the threshold.

You need API users on the NIC e-invoice and e-way bill portals and API access on the GST portal. Odoo's docs name BVM IT Consulting Services India Private Limited as the GSP.

Clean HSN codes before import. Odoo's GSTR-1 checks flag missing codes, and product HSN codes must not begin with 99, while service codes must begin with 99.

What does Odoo cost in India, including GST and e-invoice credits?

Odoo in India costs Rs 725 per user a month on Standard or Rs 1,350 on Custom, billed yearly, plus low pay-per-use credits for e-invoices, e-way bills and GST filing. New users get a first-year discount.

On Odoo's pricing page, the Indian first-year price is Rs 580 for Standard and Rs 1,080 for Custom, and a Light User costs Rs 195. Custom adds Studio, multi-company and the external API, which groups with several companies need.

In-App Purchase credits are extra. For Indian compliance, Odoo sells these packs:

Odoo IAP service	Pack prices	Free credits
eInvoice Service	1,000 invoices for EUR 15 to 10,000 for EUR 90	20
eWayBill Service	100 for EUR 3 to 10,000 for EUR 90	20
GSTR India eFiling	100 requests for EUR 5	20
Indian EDI	1,000 credits for EUR 3 to 50,000 for EUR 90	200

Credits never expire, and unused credits are refundable within 30 days. Illustrative: 1,000 e-invoices a month at the Starter rate costs about EUR 15.

Illustrative license math: 10 Standard users cost Rs 87,000 a year at Rs 725, or Rs 69,600 in the first year at Rs 580. Our Odoo pricing guide covers the costs beyond licenses.

How much does a Tally to Odoo migration cost by company size?

On iVentureTeam's published ranges, a Tally to Odoo project costs $3k to $9k for a small firm, $9k to $27k for a mid-size firm and $27k to $150k+ for a large group, with data migration at $1.2k to $9k. These are ranges, not quotes.

Company size	Typical setup	iVentureTeam range	Timeline
Small, 5 to 25 users	One entity, accounts, sales and stock	$3k to $9k	4 to 8 weeks
Mid-size, 25 to 100 users	One or two entities, warehouses, some custom flows	$9k to $27k	8 to 14 weeks
Large, 100+ users	Several entities, heavy manufacturing, integrations	$27k to $150k+	12 to 24 weeks
Data migration from Tally	Masters, open items, chosen years of history	$1.2k to $9k	Inside the project

Our Tally page puts most SME Tally moves at $4.8k to $15k all-in, and multi-company or heavily customized groups at $15k to $36k. Odoo licenses are extra.

The number moves with years of history, the count of Tally companies, godown and batch depth, TDL customizations and integrations. See the full breakdown on our Odoo implementation cost page, or get a range in minutes with the Odoo implementation cost calculator.

How long does a Tally to Odoo migration take, step by step?

Most SME Tally to Odoo migrations take 6 to 10 weeks, and groups with five or more Tally companies take 10 to 14 weeks. This is the order we follow.

1. Tally audit (week 1): list companies, financial years, voucher types, custom fields and masters, then report on data quality.
2. Mapping and setup (weeks 1 to 2): map ledgers to the Odoo chart of accounts and configure GST, e-way bills, warehouses, products and contacts.
3. Pilot migration (weeks 2 to 4): load one financial year and match the trial balance, ledger summaries and open balances against Tally.
4. Remaining history (weeks 4 to 6): load any further years in scope and reconcile each one.
5. Sign-off and cutover (weeks 6 to 8): your CA reviews the reconciliation, Tally is frozen, and Odoo goes live over a weekend.
6. Hypercare (30 days): daily check-ins with your accountant while Tally is still fresh as a reference.

Training and user testing run alongside steps 2 to 5. Start cleaning duplicate ledgers and items before kickoff, because messy masters cause most slips.

Should you cut over at financial year start or mid-year?

Cut over on 1 April when you can, because Odoo then holds the whole financial year; a mid-year cutover works but needs more reconciliation. India's financial year runs from 1 April to 31 March.

Factor	Financial year start (1 April)	Mid-year
Opening entry	Closing balances of the finished year	Balances on the cutover date
Year-to-date reports	All in Odoo	Split between Tally and Odoo
GST returns	Whole year filed from Odoo	Year split across two systems
Statutory audit	Previous year closed in Tally	Auditors check two systems for one year
Credit notes on old invoices	Fewer edge cases	Tally-era invoices need care
Calendar pressure	Year-end close and go-live collide	Any quiet month works

A practical middle path is a quarter start, so GST periods and management reports line up.

Watch credit notes. Odoo's GSTR-1 checks warn that credit notes for invoices from a given financial year should not be included after 30 November, so plan returns on Tally-era invoices with your CA.

How long should you run Tally and Odoo in parallel?

Run Tally and Odoo in parallel for one full monthly close, long enough to prove the numbers match, and no longer. Longer parallel runs double the data entry and tire the team.

At month end, these must match between the two systems:

• Trial balance
• Customer and vendor outstanding, bill by bill
• GST output and input tax
• Stock quantity and value per godown or warehouse
• Bank balances after reconciliation

Avoid daily syncing. One forum user wanted to import the Tally daybook into Odoo daily, and the replies pointed to custom work. A short manual parallel month costs less.

New to Odoo books? Our guide on how Odoo Accounting works explains journals and reconciliation. Keep the final Tally backup for auditors.

What changes for GCC companies moving from Tally to Odoo?

GCC companies follow the same data plan, but swap Indian GST setup for VAT and their local fiscal localization. Ledgers, parties, items and open bills map the same way.

Odoo's UAE localization includes a UAE chart of accounts, VAT tax groups, a VAT return in the FTA format and a corporate tax report. Map each party's TRN and each Tally VAT ledger to the matching Odoo tax.

Indian and GCC entities can share one Odoo database with multi-company on the Custom plan. Our guide to Odoo VAT compliance in the GCC covers the regional side.

Tally to Odoo migration by industry

The data plan is the same everywhere, but each industry has one Tally habit that drives the effort. For production setups, see Odoo ERP for manufacturing.

Industry	Pain or cost driver	Odoo approach	How iVentureTeam helps
Manufacturing	BOMs and production tracked in Excel	Odoo MRP with bills of materials and work orders	Map production flows, load BOMs
Trading and distribution	Many godowns and bill-wise party balances	Warehouses, locations and open invoices per bill	Clean parties, move open bills
Retail and eCommerce	Sales posted to Tally as daily totals	POS and eCommerce on one stock ledger	Connect channels, set GST by state
Pharma and FMCG	Batch and expiry tracking	Lots with expiry dates in Inventory	Load batches with opening stock
Services and projects	Cost centers used as projects	Analytic accounts and project billing	Map cost centers to analytics
GCC trading	VAT ledgers and foreign-currency parties	UAE localization and multi-currency	Set VAT taxes and TRNs

How iVentureTeam helps with Tally to Odoo migration

We plan the data scope with you, move it, and prove the numbers match before Tally is switched off. We have delivered 150+ ERP projects across 35+ countries with 40+ Odoo specialists over 13+ years.

• Tally audit: a data-quality report on your companies, years, voucher types and masters.
• Mapping and GST setup: chart of accounts, taxes, e-invoice and e-way bill, configured through our Odoo implementation services.
• Data migration: masters, open bills, opening balances and chosen history, handled by our Odoo migration services team.
• Parallel run and reconciliation: trial balance, outstanding, GST and stock matched side by side.
• Hypercare: 30 days of close support after go-live.

Tally to Odoo migration case study: Handling Comercial

An industrial manufacturer in the UAE and India moved six disconnected systems, Tally among them, onto one Odoo stack in 9 weeks. Tally ran its accounts, Excel ran MRP, and a homegrown PHP app ran inventory.

There was no live view of stock, month-end close took 11 working days, and two earlier ERP attempts had been scrapped.

We ran a 1-week diagnostic and mapped 47 processes. A custom Odoo module imported 6 years of Tally journals into Odoo's accounting, reconciled. The system went live on Odoo 19 on Odoo.sh for 240 users across 3 plants, with cutover over a single weekend.

Within 30 days of go-live, the first month closed in Odoo in 4.2 working days, down from 11. Stock accuracy moved from about 62% to 99.7%. Read the Handling Comercial Tally to Odoo manufacturing case study.

The bottom line on Tally to Odoo migration

Move masters, open bills and opening balances, keep closed years in Tally unless you truly need them in Odoo, and cut over at a period start after one matched parallel close. That plan keeps cost and risk low.

Budget for licenses, GST credits and migration work, and test GST flows on a copy first. Most SMEs are live within 6 to 10 weeks.

Ready to plan your move from Tally to Odoo?

Bring your Tally company list and we will size the migration with you. Get a Tally to Odoo migration estimate, call +91-90235-15208, or email business@iventureteam.com.