Migrate from Tally Prime to Acumatica

Each Tally Prime company becomes one Acumatica Company record under an Organization. If Tally is running in multi-company mode, each company maps to its own Acumatica Company. Inter-company transactions in Tally require Acumatica inter-company journal setup after migration. The Organization is the container and must be created first. Each Company maintains its fiscal year and tax settings. If Tally has inter-company journals, Acumatica's inter-company journal setup must be enabled after migration.

Tally groups like 'Sundry Debtors', 'Bank Accounts', and 'Direct Incomes' map to Acumatica Account Groups with the same usage classification (Assets, Liabilities, Income, Expense). The group hierarchy is preserved in Acumatica's account tree. Account Groups must exist before individual accounts are created.

Individual ledgers in Tally — such as specific bank accounts, expense line items, or revenue accounts — map to Acumatica GL Accounts. Each GL Account is assigned an Account Group, a Branch (for branch-level posting), and a Subaccount if cost-centre reporting is needed. The Tally ledger type (dr/cr posting behavior) is translated into Acumatica's posting class.

Tally party ledgers of type 'Sundry Debtors' become Acumatica Customers. The GSTIN registration on the Tally party maps to the Tax Registration ID on the Customer's address record. Tally's credit limit maps to the Customer Credit Limit field. The party balance becomes the Customer document balance in Acumatica AR.

Tally party ledgers of type 'Sundry Creditors' become Acumatica Vendors. The same GSTIN-to-Tax-Registration-ID mapping applies as with Customers. Outstanding payable balances in Tally import as open AP documents in Acumatica — either as Bills or as GL Adjustment transactions depending on the invoice-versus-voucher structure.

Tally stock items map to Acumatica InventoryItem records. Each inventory item gets a default warehouse assignment from the Tally Godown. The item's sales price and purchase price in Tally map to Sales Price and Cost columns in Acumatica's inventory price table. Stock item UOM and conversion factors translate to the Acumatica Units of Measure definition on the item.

Tally godowns (warehouses) map to Acumatica Warehouse records. Each warehouse gets a Branch assignment to support branch-level inventory tracking. Godown addresses in Tally become the Warehouse address in Acumatica. If batch tracking is active in Tally, the batch register in Acumatica (IN202500) must be pre-loaded with Tally batch data before inventory transactions import.

Tally voucher types like 'Sales', 'Purchase', 'Receipt', 'Payment', 'Journal', and 'Credit Note' map to Acumatica transaction types. Each voucher type becomes a combination of the Acumatica module (AR, AP, GL) and the document type. Custom voucher types in Tally are preserved as standard transaction types in Acumatica — special TDL-coded voucher behaviors require a functional equivalent in Acumatica's workflow or customization layer.

Tally sales vouchers import as Acumatica AR Invoices. The invoice date, invoice number, line items (stock items), quantity, rate, discount, and tax amounts all map field-for-field. The GSTIN of the customer and the e-invoice reference number from Tally are stored in custom fields on the AR Invoice since Acumatica's standard invoice form does not include a dedicated e-invoice number field.

Tally purchase vouchers import as Acumatica AP Invoices using the same field mapping pattern as AR. Vendor GSTIN, HSN-SAC codes, and reverse-charge flags from Tally map to the corresponding Acumatica tax and vendor fields. Purchase invoices linked to inventory items generate the correct stock movements in Acumatica's inventory sub-ledger.

Tally cost categories and individual cost centres do not have a direct Acumatica equivalent. For GL-level allocation, they migrate as Subaccounts. For project-based allocation, they require the Project Accounting module with cost codes. FlitStack AI surfaces the full cost-centre tree in the migration plan so your admin chooses the correct Acumatica representation before data lands.

Tally maintains voucher-numbering series per voucher type. Acumatica manages document numbers via Numbering Sequences defined per module and document type. Each Tally voucher series is mapped to the corresponding Acumatica sequence before import. If the Tally series is alphanumeric, Acumatica's sequence format must be configured to match or the prefix/suffix pattern is preserved in the document reference number.

Tally price lists defined per stock item and party type do not map to a single Acumatica object. They are decomposed into Customer Price Classes (for customer-group pricing) and Inventory Price Records (for item-specific pricing). The migration plan lists every Tally price list with its item-party combination so the admin can recreate the correct pricing structure in Acumatica.

Bank ledgers in Tally map to GL Accounts with an Account Type of 'Bank'. For bank reconciliation functionality in Acumatica, a corresponding Cash Account record must also be created in Cash Management. The Tally bank reconciliation statement data is preserved as a reference document for post-migration reconciliation.