Migrate from Tally Prime to Odoo ERP

Tally Ledgers map directly to Odoo account.account records. We preserve the primary/affects-reporting flag from Tally's group settings to set Odoo's account type (receivable, payable, revenue, expense, or other). Opening balance from Tally's Dr/Cr column migrates as Odoo's opening debit or credit amount. If Tally uses multiple GST registration numbers across ledgers, we create one Account per GSTIN in Odoo's Indian localisation configuration.

Tally's nested Groups (Sundry Debtors, Sundry Creditors, Duties and Taxes, Bank Accounts, Cash-in-Hand) map to Odoo account.group records using the parent_left/parent_right tree structure. The affects-reporting flag on each Tally Group determines whether Odoo uses it for financial statement generation. We maintain the full hierarchy so that the trial balance and P&L groupings match the Tally source output.

Tally Parties with GSTIN and PAN migrate to Odoo res.partner records. The Tally Party type (Sundry Debtor or Sundry Creditor) determines whether the partner is tagged as customer or supplier in Odoo. GSTIN is stored on the Indian address record (l10n_in_gstin field) and validated against the GST portal API during pre-migration audit. PAN, shipping address, billing address, and credit limit from Tally migrate to the corresponding Odoo fields.

Tally Stock Items map to Odoo product.product records with HSN code, unit of measure, and opening quantity. We map the Tally stock item's GST rate and tax category to Odoo's l10n_in_hsn_code and the applicable tax group. Batch and expiry date tracking in Tally migrates to Odoo's lot_id and use_expiration_date fields only if those features are enabled in the destination database configuration.

Tally Stock Groups provide the inventory category hierarchy and map to Odoo product.category records using the parent_path tree structure. The parent-to-child relationships are preserved so that Odoo's reporting by category matches the grouping logic used in Tally's stock reports.

Tally Godowns represent physical warehouse or storage locations and map to Odoo stock.warehouse records. If the customer has multiple godowns representing sub-locations within one physical warehouse, we create a single Odoo warehouse and use stock.location records to model the godown hierarchy. Single-location deployments without detailed godown usage map directly to the default Odoo warehouse. Godown-level stock quantities are disaggregated to warehouse-level during import.

Tally Sales Vouchers map to Odoo account.move records with move_type = out_invoice. Voucher number becomes the Odoo invoice reference, voucher date becomes invoice date, party reference links to the mapped res.partner, and the GST amount and rate split into Odoo's tax lines. We sequence sales invoices before purchase bills so that outstanding receivable aging reports in Odoo reflect the correct open items from day one.

Tally Purchase Vouchers map to Odoo account.move records with move_type = in_invoice. Vendor GSTIN, PAN, and invoice number from the Tally voucher migrate to Odoo's vendor bill fields. Reverse-charge GST entries in Tally are modelled in Odoo using the l10n_in_reverse_charge flag on the tax line.

Tally Payment and Receipt vouchers map to Odoo account.move records with move_type = entry, using the appropriate journal (cash or bank). Journal vouchers map similarly with the journal selected by matching the Tally voucher type name to the configured Odoo journal. All line items reference the mapped account.account records and maintain the debit/credit amounts from the source voucher.

Tally Cost Centres (departments or cost pools used for expense allocation) map to Odoo account.analytic.account records. If the Tally data uses cost-centre-based budgeting, we create corresponding analytic plans in Odoo and link the budget lines during the budget migration step. Tally does not enforce cost centre usage on vouchers; we migrate the assignments present in the source data and flag any vouchers with missing cost centre references.

Tally Budget masters associate groups or cost centres with period-based budget values and map to Odoo budget.plan records. The budget lines reference the mapped account.group or analytic account. If the destination Odoo instance does not have the Budget app installed, we migrate the budget values as tags on the account.analytic.account records for manual reference.

Tally Price Lists associate stock items with party-type-based pricing and map to Odoo product.pricelist records. Party-type conditions (customer vs supplier) become pricelist item rules in Odoo. Conditional pricing logic in Tally that uses complex conditions may require manual configuration in Odoo's Pricelist Rules editor; we document the full rule set from Tally for the customer's admin to implement.