Migrate from Marg ERP to Odoo ERP

Marg Items include HSN/SAC codes, MRP, batch-level tracking, salt names for pharma products, and multi-unit-of-measure. We map each Marg item to an Odoo Product template with type (product, consumable, service) set according to Marg's item category. MRP becomes a custom field on the product form; HSN becomes the l10n_in_hsn_code field if the Indian localization module is active. Salt names and batch tracking migrate as product attribute values if Odoo's lots-and-serials module is installed. Multi-UOM migrates via Odoo's uom_uom table with a custom field mapping Marg's internal unit codes to Odoo UoM records.

Marg Parties are ledger accounts with GSTIN, PAN, credit limits, and payment terms. We classify each Marg Party by its account type: purchase-ledger parties become Odoo Vendors; sales-ledger parties become Odoo Contacts; parties appearing on both ledgers create both records with shared GSTIN and PAN stored on the commercial partner. Party-level opening balances and outstanding amounts migrate as separate reconciliation entries rather than being rolled into the first voucher import.

Marg Sales Invoices, Purchase Bills, Credit Notes, and Debit Notes map to Odoo Account Moves with invoice type set accordingly. The most complex part of this migration is extracting the GST rate at the voucher line level and mapping it to Odoo's tax group structure. We build a rate-mapping table per Marg version, computing CGST+SGST splits or IGST based on the supplier's and customer's state codes. Vouchers with e-waybill or e-invoice references are flagged in a custom field for the customer's team to regenerate under Odoo's Indian e-invoicing module post-migration.

Marg's multi-location inventory uses Godown as the primary location entity. We map each Marg Godown to an Odoo Warehouse (stock.warehouse) with the corresponding location_id pointing to the physical location in Odoo's stock.location tree. Inter-godown stock balances migrate as opening stock quant records at the lot or product level. Marg's godown-level transfer vouchers do not map directly to Odoo internal pickings; we document the transfer history as a reconciliation report for the customer to action as needed.

Marg tracks batch number and expiry date at both the voucher and stock-quantity level for pharmaceutical compliance. We extract these as structured lot_number attributes on Odoo stock.production.lot records, linked via stock.quant to the relevant product and warehouse. The lot's use_date field carries the expiry date. This mapping requires Odoo's stock_picking_batch or lot_expiry module to be active; we flag whether it is installed during scoping.

Marg maintains a fixed-asset register with depreciation under Indian Schedule XIV conventions (Companies Act). We extract the asset's original cost, accumulated depreciation, net book value, useful life, and depreciation method (straight-line or written-down value). Because Odoo's depreciation engine uses Schedule III (Companies Act 2013) conventions by default, we recompute the depreciation schedule at Odoo and flag any difference in the first year's charge. The original Marg Schedule XIV values are stored as custom fields on the Odoo asset record for audit.

Marg's ledger structure is flat, while Odoo uses a hierarchical account structure with account groups. We preserve every Marg account code, name, and opening balance, then reconstruct the hierarchy in Odoo by mapping each account to the appropriate parent_id in the account.account table. Statutory accounts for GST input/output, TCS, and TDS are identified by their GSTIN-linked naming convention and mapped to the corresponding Odoo tax accounts. Opening balances for all accounts are loaded as Odoo move lines on an opening-date journal entry.

Marg integrates with ICICI Bank for auto-ledger entries and reconciliation. We extract bank account balances, cheque registers, and bank reconciliation statements and map them to Odoo bank and cash journals (account.journal). Marg's bank-to-ledger reconciliation documents migrate as Odoo move lines for the customer to reconcile manually or via Odoo's bank reconciliation engine post-migration. ICICI-specific auto-ledger integration requires reconfiguration in Odoo and is documented as a post-migration step.

Marg does not expose a formal custom-field API. Any user-defined fields appear as extra columns in the export output but have no guaranteed schema, label, or data-type documentation. We handle Marg custom fields as ad-hoc column mappings during migration, but cannot guarantee they will be identified correctly or mapped to an equivalent Odoo custom field. We flag every unmapped extra column in the export as a reconciliation gap for the customer's admin to review post-migration.

Marg's eRetail, salesman app, and MargPay transaction data are stored in subsidiary systems that do not share a common data store with the desktop or cloud ERP. Transactions created exclusively in the mobile apps are not accessible via Marg's file export and cannot be included in the migration. We document the existence of these systems and recommend the customer review their app-specific transaction history separately before cutover.