Migrate from Tally Prime to Microsoft Dynamics 365 Business Central

Tally Ledgers map directly to Dynamics 365 G/L Account records. We preserve the opening balance (debit or credit), closing balance, and mailing address. The primary/affects-reporting flag on Tally Ledgers determines whether the G/L Account is an Income Statement or Balance Sheet type. Cost Centre applicability from Tally maps to Dimensions in Dynamics 365 Business Central (Global Dimensions and Shortcut Dimensions). We export via XML template and transform to the OData or CSV import format required by the target app.

Tally Groups define the account hierarchy above Ledgers. We map them to Account Categories in Business Central or Finance. The affects-reporting flag determines the category group assignment (Asset, Liability, Income, Expense). Group-based budget masters in Tally map to G/L Budget entries in Dynamics with the same period and amount structure. We flag any Group with circular references or orphaned Ledgers during the pre-migration data audit.

Tally Party is a unified record type that carries both GSTIN and PAN for buyers and sellers. We split Parties into Dynamics 365 Customers and Vendors based on whether the Party has been used in a Sales or Purchase voucher. The 15-character GSTIN is validated against GST portal rules before import; invalid GSTINs are surfaced in a reconciliation report for the customer to correct. PAN, addresses (billing and shipping), and credit limits map to the corresponding Customer or Vendor fields. State codes are validated against India's 37 state UT codes.

Tally Stock Items map to Dynamics 365 Item records. Unit of Measure, opening quantity, standard cost, and standard price migrate directly. Godown-level stock quantities are disaggregated because godowns map to Locations (see entry below). We handle alternative units and price lists by creating corresponding Item Unit of Measure records and Price List lines in Dynamics. Opening stock quantity is imported as an adjustment entry or stockkeeping unit opening balance depending on the destination app configuration.

Tally Stock Groups provide the category hierarchy for inventory. We map them to Item Categories in Business Central or to Product Groups in Finance. The parent-child relationship between Stock Groups is preserved as the Item Category hierarchy in Dynamics. If the destination has a flat category structure, we collapse the hierarchy and flag the flattening for the customer's review before import.

Each Tally voucher type maps to the corresponding document type in Dynamics 365. We preserve original voucher numbers as the document number (with a configurable prefix if required), voucher date, party reference, GST amounts (CGST, SGST, IGST, and Cess), and narration. We sequence voucher import after the chart of accounts and opening balances are confirmed so that all ledger references resolve. Credit notes and debit notes map to their Dynamics equivalents with the original-reversed-document reference preserved.

Tally Godowns represent physical storage locations and have no native equivalent in standard Business Central or Finance. We map them to Locations (Business Central Essentials+) or Warehouse/Site records (Business Central Premium or Finance SCM). Each Stock Item's godown assignment becomes a Quantity on the corresponding Location record. If the customer has used godowns for internal cost allocation rather than physical storage, we map them to Dimensions or Departments in Dynamics and flag the distinction for confirmation during scoping.

Tally Cost Centres function like departments or cost pools for expense allocation. We map them to Departments in Business Central or to Projects in Finance/Project Operations depending on how the customer has used cost centres. If cost centres drive internal reporting rather than formal project accounting, we configure them as Global Dimensions. We note that Tally does not enforce cost-centre allocation on voucher lines, so some transactions may have nil or partial cost-centre assignment requiring manual review before import.

Tally currency definitions and the most recent exchange rates map to Dynamics 365 Currencies and Exchange Rate records. We import the exchange rate as of the migration cutover date and set up a Currency Exchange Rate Service connection or manual update schedule for ongoing rates. Realised and unrealised exchange gain/loss accounts from Tally map to the corresponding G/L Accounts in Dynamics.

Custom voucher type definitions in Tally (including naming series, numbering prefixes, and applicability to specific ledgers) are preserved as Journal Templates or Document Types in Dynamics 365. We map the numbering series configuration and agree on a prefix strategy with the customer to prevent duplicate document numbers in the destination system.

Tally Budget masters associate Groups or Cost Centres with period-based budget values. We map these to G/L Budget entries in Dynamics 365, preserving the budget name, period breakdown (monthly or quarterly), and amounts. Budget vs actual reporting requires matching the G/L Account range in the budget entry to the corresponding account group in Dynamics.

Tally price lists associate Stock Items with party-type-based pricing. We map these to Microsoft Dynamics 365 Sales Price Lists and Purchase Price Lists, preserving the item reference, unit of measure, price, and validity dates. Conditional pricing logic (volume breaks, customer-specific overrides) is documented separately for the customer's admin to rebuild in Dynamics Price Lists or the integrated Power Automate pricing workflow.