Migrate from Marg ERP to Microsoft Dynamics 365 Business Central

Marg's account groups and ledger hierarchy map to D365 G/L Account structure. Marg's statutory accounts for GST input/output, TCS, TDS, and e-waybill payables become D365 posting accounts under the appropriate account category (Cash, Bank, Customer, Vendor, or Direct/Indirect Expenses). We preserve opening balances, account types, and the full group-subgroup hierarchy, flagging any D365 default accounts that conflict with Marg's naming or posting convention.

Marg Parties serve as both customers and vendors depending on transaction history. We split by examining voucher types: parties with outbound sales or sales-returns become D365 Customers; parties with inbound purchases or purchase-returns become Vendors. Parties with both directions retain both records. We carry GSTIN, PAN, credit limit, payment terms, opening balance, and outstanding amounts into the respective D365 record. Marg Party groups map to D365 Customer and Vendor posting groups for correct receivable and payable posting.

Marg Items with MRP, HSN/SAC codes, batch tracking, salt names (for pharma), and multi-unit-of-measure map to D365 Items. We set Item type as Stockkeeping Unit for inventory-tracked items and Service for non-stocked. MRP becomes the suggested sales price; cost price maps to D365 Unit Cost. HSN/SAC codes migrate to the item's Tariff Number field. GST product posting groups are set based on the rate extracted from Marg's item-level GST registration.

Marg vouchers map to D365 posted sales invoices, purchase invoices, and credit/debit note records. The full line-item GST breakdown (CGST, SGST, or IGST rate and amount per line) migrates to D365 document lines with the applicable tax group and tax item group assignments. Marg's e-invoice number and e-waybill number are stored in custom fields on the migrated document header. We flag any vouchers that were only saved (not posted) in Marg and handle them as unposted documents requiring customer action before migration.

Marg Godowns map to D365 Sites (address and location parameters) and corresponding Warehouse records. Inter-Godown stock balances migrate as D365 Warehouse entries. Marg's Godown-specific pricing rules map to D365 location-based price groups if configured. We preserve the Godown's active/inactive status and flag any Godown with zero stock for archiving rather than migration.

Marg batch number and expiry date are stored at voucher line and stock level. We extract these as structured lot attributes and map to D365 Item Tracking Codes (lot number) and the lot's Expiration Date field. For pharma items, we validate that expiry dates are within a configurable future window (e.g., 30 days minimum remaining shelf life) and flag items approaching expiry for customer review before migration. Lot tracking must be enabled on the D365 item card before batch data is imported.

Marg maintains an asset register with original cost, accumulated depreciation, net book value, and Schedule XIV depreciation schedules. We extract all four values and load them into D365 Fixed Asset records. D365's depreciation book is populated with the same method (straight-line or written-down-value) and useful life; we recompute the first-year depreciation charge and flag any difference versus Marg's Schedule XIV result for the customer's finance team to validate. Depreciation entries migrate as posted fixed asset journal lines rather than source documents.

Marg bank accounts (including ICICI Bank auto-ledger integration) map to D365 Bank Accounts with account number, bank name, and SWIFT/IFSC codes. Marg's cheque register and bank reconciliation statements are extracted as CSV and mapped to D365 Bank Account Reconciliation records for historical reference. Cash accounts map to D365 G/L Accounts of type Bank Account for financial reporting consistency.

Marg stores GST rate (CGST+SGST or IGST) per voucher line, not at the party or item level. We build a rate-mapping table during scoping that maps each unique Marg GST rate combination to a D365 Tax Group (for transaction-level applicability) and Tax Line (for rate and amount calculation). This table handles composition-tier transitions mid-period by preserving the rate at the time of each voucher.

Marg's party-wise outstanding receivables and payables, and Godown-wise stock balances, migrate as D365 General Journal lines. Customer open invoices load as open sales lines with residual amounts. Vendor open invoices load as open purchase lines. Stock balances load via item journal with appropriate location (Warehouse) references. Opening balance migration runs after master data but before transactional history to ensure the trial balance is in equilibrium before the first live posting.

Marg does not expose a formal custom-field API; any user-defined fields appear as extra columns in the XLS/CSV export output. We handle these as ad-hoc mappings by creating D365 custom fields via the extension model (AL-based extensions or Power Apps field add-in for Business Central) and mapping them where the data type is inferable from the export value. Full preservation cannot be guaranteed; we document every unmapped custom field in the handoff report for manual entry or future extension development.

Marg's eRetail, salesman mobile app, and MargPay transaction data are stored in subsidiary systems that do not share a common data store with the desktop/cloud ERP. These records are not reachable via Marg's export utility and cannot be included in the migration scope. Any app-only transactions must be manually re-entered or retrieved from the respective app's backup export if available.