Migrate from TallyPrime to Acumatica

Every TallyPrime primary and sub-ledger maps to an Acumatica GL Account with the matching Account Class (Asset, Liability, Income, Expense). If TallyPrime uses Cost Categories for segment reporting, we map each Cost Category to an Acumatica Subaccount dimension so the Tally cost-centre-wise P&L translates to an Acumatica subaccount-based income statement.

TallyPrime stock groups map directly to Acumatica Stock Categories without transformation. The category hierarchy (parent/child structure) is preserved using the Parent Category field in Acumatica's Item Classes screen. This ensures that inventory reports and BOM rollups maintain the same drill-down structure in both systems, allowing existing TallyPrime inventory reporting templates to be replicated in Acumatica with minimal reconfiguration after migration.

TallyPrime stock items map 1:1 to Acumatica Stock Items. For each godown (warehouse) in TallyPrime, we create a corresponding Item Warehouse row in Acumatica with branch-specific on-hand quantities and valuation. The primary Tally rate maps to the Acumatica Last Cost price type; if MRP is tracked, it stores as a custom field.

Each TallyPrime godown becomes an Acumatica Branch configured with the Warehouse attribute enabled. Branches without warehouse inventory capability are created with the Inventory Control flag disabled. This mapping allows Tally's godown-wise stock report to translate directly to Acumatica's branch-level inventory enquiry, preserving the same stock visibility hierarchy that users rely on for warehouse-level picking and replenishment decisions.

TallyPrime unit definitions (Simple, Compound) map to Acumatica UOM records without transformation. Compound units such as 'Dozen Boxes' or 'Box of 24 Units' map using Acumatica's Compound UOM feature with a base-unit multiplier. All conversion factors between units are preserved in the migration, though Acumatica requires UOM classes to group related units — we create the appropriate UOM class before loading units to ensure conversion dropdowns work correctly in inventory transactions.

TallyPrime's 'Sundry Debtors' group maps to Acumatica Customers; 'Sundry Creditors' maps to Acumatica Vendors. The split is determined by the TallyPrime ledger group assignment. GST registration type (Regular, Composition, SEZ, OIDAR) is stored as a custom field on both Customer and Vendor records in Acumatica.

TallyPrime sales vouchers map to Acumatica AR Invoices. If TallyPrime uses inventory tracking on the sales voucher, we also generate an Inventory Issue document to decrement stock at the branch. The original Tally voucher number is stored in the External Reference field on the AR Invoice so audit trails link back to the source.

TallyPrime purchase vouchers map to Acumatica AP Bills. Inventory-receiving purchase vouchers also generate an Inventory Receipt document at the appropriate branch to update stock on-hand quantities. Landed cost allocation (freight, insurance) from TallyPrime is preserved using Acumatica's landed cost feature on the Receipt, allowing the total purchase cost to be distributed across inventory items for accurate landed cost accounting.

TallyPrime payment vouchers split by counterparty type: payments to Vendors become Acumatica AP Payments linked to the outstanding AP Bill; receipts from Customers become AR Payments applied against open AR Invoices. Payments to or from Banks map to Cash Management payments against the appropriate GL account, maintaining the same cash-account linkage that TallyPrime vouchers establish in its cash books.

TallyPrime receipt vouchers for Customer payments map to Acumatica AR Payments with the Customer lookup so the payment auto-applies to open invoices based on due date or reference number. Receipts from other sources (other income, capital contributions, loans) map to Cash Management receipt transactions against the relevant GL account, ensuring non-operating cash inflows are classified correctly in the financial statements.

TallyPrime journal vouchers map directly to Acumatica Journal Transactions with no transformation required. Each journal line's debit/credit amounts, account, and subaccount are preserved exactly as entered in TallyPrime. Adjustment journals such as debit notes and credit notes that affect payable or receivable balances are loaded as separate AP/AR documents rather than journal entries to ensure correct AR/AP aging and outstanding balance tracking.

TallyPrime debit notes against suppliers map to AP Adjustments (debit memos) in Acumatica. Credit notes to customers map to AR Adjustments (credit memos). The adjustment reason code maps to an Acumatica reason code. If the note affects GST liability, the tax amount carries into the adjustment's tax amount field.

TallyPrime cost categories are a reporting dimension, not an account type. In Acumatica, we map each cost category to a Subaccount dimension so that the Tally cost-centre-wise P&L translates to an Acumatica financial report using Subaccount row layouts. If the Project Accounting module is active, project codes can alternatively serve this function.

TallyPrime stores GSTIN on party ledgers and applies GST rates on voucher lines. In Acumatica, we create a Tax Zone per state (e.g., Maharashtra GST Zone), define Tax Categories for each GST rate (5%, 12%, 18%, 28%), and attach the GSTIN as a custom field on Customer and Vendor records. The Tally GST rate on each line maps to the matching Acumatica Tax Category.