Migrate from TallyPrime to Odoo ERP

TallyPrime Company records map to Odoo ResCompany. We extract each Company with its GSTIN, fiscal year configuration, and base currency and create corresponding Odoo companies. Multi-company setups in TallyPrime require Odoo's multi-company configuration (Settings > Users > Companies) with separate warehouse and journal assignments per company. If the destination is a single Odoo database serving multiple companies, we configure company_id domain rules on all documents.

TallyPrime Ledgers split into two Odoo record types. Party Ledgers (Customers and Suppliers) map to Odoo res.partner records with GSTIN, PAN, mailing address, credit limits, and opening receivable/payable balances. Income and Expense Ledgers map to Odoo account.account records in the chart of accounts with the correct account_type (income, expense, asset, liability, equity) and GST tax mapping. Opening balances carry forward as equity or retained earnings entries depending on account type.

TallyPrime Vouchers (Sales, Purchase, Receipt, Payment, Contra, Journal, Debit Note, Credit Note) map to Odoo Account Move records in the corresponding journal. We preserve the original Tally voucher number as a reference field (ref or name) so historical documents remain traceable for GST portal reconciliation. Voucher date and line-level ledger assignments migrate directly. We apply a cutoff-date filter and run a trial balance verification before and after migration to confirm no balance sheet discrepancy.

TallyPrime Voucher Types map to Odoo Journals. Each voucher type (Sales, Purchase, Payment, Receipt, Bank, Cash, General) becomes a corresponding journal with its own sequence for numbering. Custom voucher types with specific numbering series map to Odoo journal sequences that we configure before voucher import. Journal point_of_sale type is used only if Odoo's POS module is in scope.

TallyPrime Stock Items map to Odoo Product records. HSN/SAC codes migrate to the product's l10n_in_hsn_code field. Opening quantity, rate, and value migrate as an initial stock quant (stock.quant) in the configured warehouse. If the product has BOM (Bill of Materials) configured in TallyPrime, we map it to Odoo's mrp.bom records in the Manufacturing module. Product variants in Odoo handle Tally items with multiple specifications.

TallyPrime Godowns represent multi-location inventory. Each Godown maps to an Odoo stock.warehouse with child stock.location records for sub-locations. If Odoo is configured with a single warehouse, Godown-stock mappings consolidate into the main warehouse's internal locations. If Odoo Manufacturing or multi-warehouse is in scope, each Godown becomes a distinct warehouse with its own routes and replenishment rules.

TallyPrime Parties with GSTIN, PAN, mailing address, contact details, and credit limits map to Odoo res.partner records. Customer flag maps to customer_rank or is_company; Vendor flag maps to vendor_rank. GSTIN validation is preserved in the l10n_in_gstin field. Opening receivables and payables migrate as partner ledger balance entries in the respective Payables or Receivables account. Contact persons and phone/email details migrate to the partner's contact records.

TallyPrime Cost Categories map to Odoo Analytic Account plans, and Profit Centers map to Analytic Account records. Segment-wise P&L in TallyPrime replicates in Odoo through analytic distribution on account move lines. We export the full Cost Category and Profit Center hierarchy and create corresponding analytic plan structures in Odoo. If Odoo Enterprise with Accounting is in scope, multiple analytic plans per account are supported.

TallyPrime fixed assets tracked as stock items with Track-as-Asset flag and separate depreciation books map to Odoo account.asset records. Book value, accumulated depreciation, and depreciation rate migrate as asset values and depreciation lines. We preserve the depreciation method (straight-line or WDV as configured in Tally) and create corresponding asset profiles in Odoo. Asset category assignments map from Tally's asset classification ledger.

TallyPrime Budgets linking to Ledgers with periodic or YTD control values map to Odoo budget.budget records with budget.post lines tied to the migrated account codes. If Odoo Enterprise accounting is not in scope, budgets are documented as named records in a custom spreadsheet for the customer's admin to configure post-migration. Budget variance reporting in Odoo uses the Accounting module's budget reporting views.

TallyPrime Units of Measure (simple name/alias pairs and compound units like 'dozen boxes') map to Odoo uom.uom records with category matching and rounding precision. Compound UoMs split into component units and mapped to Odoo's related UoM category. We export the full UoM list before product migration so that product creation can reference valid UoM IDs.

TallyPrime e-Invoice JSON, GSTR-1, GSTR-3B, and e-Way Bill data does not replicate inside Odoo because the GST portal maintains authoritative filing records. We carry forward GST portal reference numbers and ITC opening balances as Odoo opening balance entries. GST tax rates and classifications from Tally map to Odoo account.tax records with the correct l10n_in tax type (gst, cess, igst, cess_non_advol). Fiscal positions handle interstate versus intrastate tax mapping.