Migrate from TallyPrime to Epicor Prophet 21

Each TallyPrime Company maps to an Epicor Company entity with its own fiscal year configuration, base currency, and Chart of Accounts. We extract company name, GSTIN, mailing address, and fiscal year start/end from the Tally company master, then create corresponding Epicor Company records. If the destination is a single Epicor tenant with multiple companies, inter-company voucher handling requires Epicor elimination journal configuration post-migration.

TallyPrime Ledgers map to Epicor GL Accounts within the destination Chart of Accounts. We preserve the ledger hierarchy (Groups and Sub-groups), GST classification (GST rate applicability, nature of supply), and opening balances as GL Account period-opening entries in Epicor. Tally's Cost Categories and Profit Centers map to Epicor Business Unit and Segment dimensions respectively, which are configured as reporting dimensions in Epicor's Financial Reporting module rather than as ledger-level fields.

TallyPrime Vouchers split by voucher type: Sales and Credit Note vouchers map to Epicor AR Invoice; Purchase and Debit Note vouchers map to Epicor AP Invoice; Receipt vouchers map to AR Receipt; Payment vouchers map to AP Payment; Contra, Journal, and non-trade vouchers map to Epicor Journal Entry. Voucher date sequencing is preserved; we apply a cutoff-date filter so that the last closed period in TallyPrime flows into the first open period in Epicor without balance gaps.

TallyPrime Stock Items map to Epicor Part Master records. We carry forward HSN/SAC codes, opening quantity, opening rate, and opening value. Tally's Track as Asset flag becomes a Part Type classification in Epicor. For non-BOM stock items, the mapping is direct. For manufactured items with BOMs in TallyPrime (where BOM is tracked manually via stock item relationships), we transform to Epicor Part BOM structures during migration.

TallyPrime Godowns map to Epicor Warehouses and Bin Locations in a two-level structure. Each Godown becomes a Warehouse; if TallyPrime Godowns have sub-locations or sections, these map to Bin Locations within the warehouse. We export the Godown-stock mapping to populate Epicor PartBin records so that opening stock positions are correct per location at go-live.

TallyPrime does not have a native BOM module; BOM is typically managed via stock item relationships or manual records. We audit the customer's BOM practices during scoping and, where BOM data exists in Tally, transform it into Epicor Part BOM structures with the manufactured Part as the header and component Parts as lines with quantity-per and bom-seq. This requires a configuration phase in Epicor Data BPM before import because BOM creation involves header, detail, and revision records.

TallyPrime Parties with GSTIN and party type of Sundry Debtor map to Epicor Customer; party type of Sundry Creditor maps to Epicor Supplier. We preserve GSTIN, PAN, mailing address, contact details, credit limits, and opening receivables/payables as Epicor Customer or Supplier financial records. Party-specific Tally features like TCS/ TDS applicability are stored as custom fields or tax jurisdiction rules in Epicor.

TallyPrime UoMs map to Epicor UOM Class (grouping, e.g., Length, Weight, Volume) and UOM Code entries within each class. Compound UoMs such as 'dozen boxes' are split into component units during transformation. We export the full UoM list during the master-data phase and create corresponding Epicor UOM records before any Part or voucher import that references them.

TallyPrime multi-currency definitions and historical exchange rates extract to Epicor Currency records and Exchange Rate tables. We apply the applicable rate at each voucher date by matching the voucher exchange rate from TallyPrime's voucher log to Epicor's exchange rate effective-date table. Multi-currency voucher amounts in foreign currencies become Epicor transactions with the appropriate currency and exchange rate references.

TallyPrime voucher types with customized numbering series, print layouts, and approval workflows are documented and mapped to Epicor Document Types. We flag any voucher type with custom TDL-driven behavior (customized invoices, auto-calculations) as a manual-rebuild item in the handoff document. Standard voucher types (Sales, Purchase, Receipt, Payment, Journal) map to Epicor equivalents without configuration work.

TallyPrime bank and cash ledgers with IFSC codes, account numbers, and cheque configurations map to Epicor Bank Account records. Cheque printing configurations are documented for manual rebuild in Epicor's payment printing setup. Bank reconciliation data (cheque numbers, dates, matching status) is preserved as Epicor Payment Apply records for open items at cutover.

TallyPrime fixed assets tracked via stock items with 'Track as Asset' flag map to Epicor Asset Master records. We export asset register data including book value, accumulated depreciation, depreciation method, and last depreciation date, and create Epicor Asset records with corresponding depreciation books. TallyPrime depreciation books map to Epicor Depreciation Calculation methods.

TallyPrime Budget records linked to ledgers with periodic or YTD control values map to Epicor GL Budget records where the customer's Epicor edition supports budget management. If the destination Epicor tier does not include budget management natively, we store budget data as custom GL Analysis records and deliver the budget matrix as a structured import template for the customer's admin to load post-migration.

TallyPrime e-Invoice JSON, GSTR-1, and GSTR-3B filing references and ITC opening balances carry forward as opening ledger entries and tax jurisdiction rules in Epicor. The GST portal maintains the authoritative filing record, so the last-filed period GSTR reference number is documented as the cutover boundary. Epicor has no native Indian GST module; customers operating in India typically use a third-party GST add-on (e.g., Tally GST Bridge or Zoho Tax) for ongoing compliance filing. We provide a GST re-onboarding checklist for the customer's compliance team.