Migrate your TallyPrime data

TallyPrime supports multiple Companies within a single data file. We export each Company as a discrete unit and recreate the company structure (name, GSTIN, fiscal year configuration, base currency) in the target ERP. Multi-company consolidation is handled by mapping inter-company ledgers explicitly.

Ledgers are the core chart of accounts in TallyPrime and include GST classification, mailing details, bank info, and opening balances. We map Tally's ledger hierarchy to the target's account structure, preserving GST treatment and bifurcating GST-ledgers (SGST, CGST, IGST, Cess) into separate accounts in systems that model tax accounts differently.

Vouchers cover all transaction types—Sales, Purchase, Receipt, Payment, Contra, Journal, Debit Note, Credit Note. We sequence voucher export by date and apply a cutoff-date filter so that opening balances and current-year transactions are cleanly separated. GSTIN validation and HSN/SAC mapping are applied at voucher line level.

Stock Items include HSN/SAC codes, opening quantity, rate, and value, and are linked to Godowns for multi-location stock. We export Items with their full BOM (Bill of Materials) where applicable, mapping stock units and pricing to the destination's item master.

Godowns represent TallyPrime's multi-location inventory model. We export Godown-stock mappings and consolidate or expand them depending on whether the destination supports multi-location inventory. Godowns with zero stock are flagged for optional exclusion.

Parties carry GSTIN, PAN, mailing address, contact details, credit limits, and opening receivables/payables. We export all party masters with GSTIN validation and preserve outstanding opening balances as separate ledger entries. Credit period and pricing level settings are mapped as custom fields where the target does not have native equivalents.

TallyPrime allows highly customized Voucher Types with numbered series, print layouts, and approval workflows. We map standard voucher types to destination equivalents and flag any voucher type that has custom numbering or print configurations requiring manual rebuild in the target.

UoMs are simple name/alias pairs in TallyPrime. We export the full UoM list and create corresponding units in the destination, handling compound UoMs (e.g., 'dozen boxes') by splitting into component units.

TallyPrime supports multi-currency transactions. We export currency definitions and exchange rates, applying the applicable rate at the voucher date. Historical exchange rates from the voucher log are preserved for reconciliation.

Cost Categories and Profit Centers are TallyPrime's internal segmentation tools for segment-wise P&L and balance sheet. These are destination-specific and do not map 1:1 to most ERPs; we export them as tagged vouchers and recreate them as analytical dimensions or cost-centre tags in the target where supported.

Bank ledgers with IFSC codes, account numbers, and cheque printing configurations are exported as standard ledgers. Reconciliation data (cheque numbers, dates, matching status) is preserved as voucher-level annotations and reconstructed in the target's bank reconciliation module.

Fixed Assets in TallyPrime are tracked via stock items with a 'Track as Asset' flag and separate depreciation books. We export asset registers with book values, accumulated depreciation, and depreciation rate configurations, mapping to the destination's fixed asset module where one exists.

TallyPrime Budgets link to Ledgers and define periodic or YTD control values. These are exported as named budget records and mapped to the target's budget module, if available, or stored as custom records where the destination does not have native budget management.

GSTR-1, GSTR-3B, e-Invoice, and e-Way Bill records are TallyPrime exports stored in JSON and XML formats. We carry forward the GST portal filing history reference numbers and ITC opening balances from these exports. Filing history on the GST portal is not affected by migration—we focus on ensuring ITC opening balance continuity in the new ERP.