Migrate from Tally Prime to Infor CloudSuite Corporate

Tally Ledgers are the core account records and map directly to Infor's chart of accounts. We flatten Tally's Group-Ledger hierarchy by mapping each Ledger's parent Group to the corresponding Infor account group or category. Opening balances and closing values from Tally migrate as initial amounts on Infor account records. The primary/affects-reporting flag on each Ledger determines whether it is classified as a P&L or Balance Sheet account in Infor. Tally cost-centre allocations on Ledgers require Infor's dimension-tagged posting configuration.

Tally Groups define the hierarchy above Ledgers (Primary, Secondary, Affects-Reporting flags). We map these to Infor account groups that determine the financial statement classification. Tally's Group-under-Group nesting requires flattening into a single-level account group structure in Infor. The mapping preserves the affects-reporting flag so that Infor's financial statements reflect the same account classification as Tally's Balance Sheet and Profit & Loss reports.

Tally Parties carry GSTIN, PAN, billing/shipping addresses, and credit limits that map to Infor Business Partner records. We validate all GSTIN values against the GST portal API during the pre-import audit and flag invalid GSTINs for correction before the final import run. Party type (Customer vs Supplier) maps directly to Infor's Business Partner type. Tally's payment terms and credit limits migrate as terms and credit-hold fields on the Business Partner. GSTIN validation is critical because Infor's India localisation module references GSTIN for GSTR filing.

Tally Stock Items include unit of measure, opening quantity, rate, and HSN/SAC codes. We map these to Infor Item Master records with the corresponding unit of measure, standard cost, and tax codes. HSN and SAC codes from Tally migrate as classification fields on the Infor Item. Note that Tally's per-godown stock quantities are disaggregated during migration and assigned to Infor warehouse location records rather than a single quantity on the Item.

Tally Godowns represent physical warehouse or storage locations with per-item stock quantities. Most Infor CloudSuite editions do not have a native Godown concept; instead they use warehouse and location fields on inventory items. We disaggregate Tally's godown-level stock quantities into separate Infor warehouse records, with the quantity per warehouse reflected in the Item's on-hand by location. If the customer uses godowns as logical cost centres for internal reporting, we map these to Infor cost centre dimensions or department codes. The mapping requires careful attention to whether Tally godowns are physical locations, logical divisions, or both.

Tally Stock Groups provide the category hierarchy for inventory items and map to Infor's item category or product group structure. We preserve the group-to-item parent relationships so that Infor's inventory reporting reflects the same product classification as Tally. If the customer uses Tally's secondary groups for sub-categorisation, these map to Infor's additional category assignment capability or a custom attribute.

All Tally transaction types stored as Vouchers map to corresponding Infor transactions with voucher number, date, party reference, amount, and tax breakdown preserved. We reclassify voucher line items against the mapped chart of accounts. Original voucher numbers are preserved as reference numbers in Infor. Voucher date sequencing is maintained so that Infor's posting sequence matches Tally's. We flag any voucher that fails Tally's own exceptions report during pre-migration validation so the customer corrects and re-exports before we run the final import.

Custom voucher type definitions in Tally (naming series, numbering prefixes, applicability to specific ledgers) are preserved as transaction type metadata in Infor. We configure Infor's document type or transaction type codes to match the customer's Tally voucher type naming conventions. If the customer has disabled voucher type numbering in Tally, we agree on a numbering strategy with Infor before import to prevent duplicate voucher numbers, which Infor treats as errors.

Tally Cost Centres function like departments or cost pools for expense allocation and map to Infor's department or project cost-centre fields. Tally does not enforce cost-centre allocation on every voucher, so we identify the allocation rate (what percentage of vouchers carry cost-centre tags) during the data audit. We note that Infor's cost-centre enforcement may be stricter than Tally's; any vouchers without cost-centre assignments in Tally may require default assignments or manual review during migration.

Tally currency definitions and the most recent exchange rates map to Infor's currency module. Foreign currency transactions with realised and unrealised gain/loss tracking migrate as journal entries in Infor with the corresponding exchange rate and gain/loss account assignments. We validate that Infor's decimal precision for the currency matches Tally's settings.

Tally Budget masters associate groups or cost centres with period-based budget values. We map these to Infor budget or forecast records where the target system supports comparable period-based budget tracking. Infor editions without a native budget module require manual budget entry post-migration using the exported budget figures as a reference spreadsheet. This is documented in the migration deliverables so the customer admin can re-enter budgets in Infor's budget forms.

Tally price lists associate stock items with party-type-based pricing (e.g., retail, wholesale, special rate). We map these to Infor's price list or customer-specific pricing records. Conditional pricing logic (volume breaks, date-effective pricing) may require manual configuration in Infor because Tally's price list conditional logic does not have a direct equivalent in all Infor editions. We document the pricing rules from Tally in a lookup table for the customer's admin to configure in Infor's price management module.