Migrate from Tally Prime to Epicor Prophet 21

Tally Prime Groups define the hierarchy above Ledgers and carry the primary/affects-reporting flag that controls whether they appear in financial statements. Epicor ERP stores accounts in a flat GL Account table with a AccountType field that determines classification (Asset, Liability, Equity, Revenue, Expense). We map Tally Groups to Epicor GL Accounts with AccountType set according to the group's nature, and preserve the Group-Ledger parent relationship as Epicor's account segment structure. Groups without a ledger directly attached are mapped as summary GL accounts.

Tally Prime Ledgers are the core account records with opening balances, closing values, and transaction references. We export them via XML, preserve opening debit and credit amounts, and create corresponding GL Account records in Epicor ERP. Tally's opening balance vouchers must be migrated and re-accepted in Epicor before subsequent transaction import to avoid zero-balance carry-forward issues. Opening balance date and period are preserved as the GL Account's effective start date.

Tally Parties carry GSTIN, PAN, billing and shipping addresses, credit limits, and payment terms. We map them to Epicor Customer (for parties with sales vouchers) and Supplier (for parties with purchase vouchers) records. GSTIN validation against the GST portal API is performed during pre-import audit, and invalid GSTINs are surfaced for correction before the final import. The Tally GSTIN-linked party reference is preserved in Epicor's Tax ID field.

Tally Prime Sales vouchers (with voucher type Sale, Sale+ GST) map to Epicor ERP AR Invoice records. The original voucher number is preserved in Epicor's InvoiceNum field, the voucher date becomes the InvoiceDate, and the Party reference resolves to the Customer record created from the corresponding Tally Party. GST tax amounts separate into Epicor's tax rate fields tied to the relevant Tax Region.

Tally Prime Purchase vouchers map to Epicor ERP AP Invoice records. The original voucher number and date migrate, and the Party reference resolves to the Supplier record. Reverse-charge GST entries in Tally map to Epicor's GST tax handling on the purchase side with the applicable reverse-charge flag set per line.

Tally Payment vouchers map to Epicor AP Payment records linked to the corresponding AP Invoice; Receipt vouchers map to AR Receipt records linked to the corresponding AR Invoice. Voucher narration migrates as payment reference. The bank or cash Ledger from Tally maps to the corresponding Epicor Cash Account GL number.

Tally Prime Journal vouchers map to Epicor ERP GL Journal Entries. Each journal line's Dr/Cr amount and Ledger reference map to the corresponding GL Account and amount in the Epicor journal entry. The voucher Narration field migrates as the Journal Entry description, and voucher numbering is preserved per the agreed numbering strategy confirmed during scoping.

Tally Prime Stock Items with unit of measure, opening quantity, rate, and HSN/SAC code map to Epicor ERP Part records. The stock item's godown assignment is handled separately through the Godown mapping below. We map the stock item's base unit of measure to Epicor's UOM class and set Part Type to Manufactured or Purchased depending on the voucher history. HSN codes migrate to the Part's GTIN or Harmonized Code field.

Tally Stock Groups provide the category hierarchy for inventory items and map to Epicor ERP Part Class or Product Group. The parent-child hierarchy is preserved as Epicor's class tree structure. The affects-reporting flag on the Stock Group maps to Epicor's reporting classification on the Part Class.

Tally Prime Godowns represent physical warehouse or storage locations. Most cloud ERPs including Epicor do not have a native godown concept as a first-class object. We map each Tally Godown to an Epicor ERP Warehouse record, and godown-level stock quantities disaggregate into Epicor's PartBin records scoped to that warehouse. If a Tally stock item is assigned to multiple godowns, it creates multiple PartBin entries under the corresponding Epicor Warehouses. Stock items without a godown assignment default to Epicor's primary warehouse.

Tally Cost Centres function like departments or cost pools for expense allocation. We map them to Epicor ERP Project segments or Department codes depending on whether the customer uses Epicor's project module. Tally does not enforce cost-centre allocation on vouchers; where a Tally voucher references a Cost Centre, that reference migrates as an Epicor Project reference on the GL journal entry line.

Tally Prime price lists associate stock items with party-type-based pricing. We map these to Epicor ERP Customer Price Groups and Part-specific price lists. Where Tally prices are party-type-gated (e.g., wholesale vs. retail), we create Epicor Price Break records tied to the corresponding Customer Price Group. Complex conditional pricing logic that relies on Tally's built-in price-list conditional features may require manual rebuild as Epicor price rules post-migration.

Tally Prime currency definitions with exchange rates and realised/unrealised gain-loss tracking map to Epicor ERP Currency and Exchange Rate tables. We map the most recent exchange rates as Epicor Exchange Rate records with the applicable effective dates. Gain/loss ledger references from Tally map to the corresponding Epicor GL accounts for currency revaluation.

Tally Prime Budget masters associate groups or cost centres with period-based budget values. We map these to Epicor ERP Budget records where the target system's budget module is licensed. Budget periods map to Epicor's fiscal period structure, and budget amounts map to GL amount fields by account. Multi-dimensional budgets (by group and cost centre simultaneously) may require decomposition into separate Epicor budget records per dimension.

Tally Prime custom voucher type definitions (naming series, numbering prefixes, applicability to specific ledgers) map to Epicor ERP Transaction Types or Entry Event codes. We preserve the naming series prefix and current numbering sequence so that Epicor continues numbering without gaps or duplicates. The voucher type's applicability to specific ledgers maps as Epicor Entry Event-to-GL account restrictions.

Tally Prime data encrypted under TallyVault cannot be accessed without the customer's decryption key and the TallyVault service being active. We flag TallyVault records during the pre-migration audit and escalate to the customer. If the decryption key is unavailable, the encrypted records cannot be extracted and are excluded from the migration scope. We document the excluded record count and type in the migration handoff report.