ERP migration
Field-level mapping, validation, and rollback between Marg ERP and Epicor Prophet 21. We move data and schema; workflows are rebuilt natively in Epicor Prophet 21.
Marg ERP
Source
Epicor Prophet 21
Destination
Compatibility
11 of 14
objects map 1:1 between Marg ERP and Epicor Prophet 21.
Complexity
BStandard
Timeline
5-8 weeks
Overview
Moving from Marg ERP to Epicor ERP is a cross-architecture migration: Marg is a desktop-first Indian distribution and pharmacy ERP with no public API and file-based exports, while Epicor ERP is a manufacturing-focused platform with deep MES integration, a DMT bulk import tool, and a cloud-hosted Kinetic deployment model. The most significant difference is that Marg's GST composition is stored at the voucher line level with Indian statutory compliance (e-invoicing, e-waybill, GSTR filing) built into every transaction, whereas Epicor's tax engine is country-agnostic and requires manual configuration of Indian GST rates. We preserve the GST rate per voucher line as structured metadata and re-apply it to Epicor's tax codes at the destination. Marg's Godowns (multi-location stock entities) map to Epicor Warehouses with inter-location balances preserved. Marg's fixed-asset depreciation uses Indian Schedule XIV conventions that require net book value extraction and recomputation at the destination. Marg's mobile app transactions, custom fields outside the export schema, and workflow/automation logic do not migrate; we deliver a written inventory of automations requiring rebuild in Epicor Kinetic's process automation framework.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a Marg ERP object lands in Epicor Prophet 21, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
Marg ERP
Item
Epicor Prophet 21
Part
1:1Marg Items (products, raw materials, packing materials) map to Epicor Part with PartNum, Description, TypeCode (stock vs non-stock vs service), and Unit of Measure. Marg's MRP-linked pricing, HSN/SAC codes, and pharma salt names transfer to Epicor Part's standard and user-defined fields. We handle multi-unit-of-measure by mapping Marg's primary and secondary UOM to Epicor's PartUOM rows. Marg batch and expiry tracking maps to Epicor's Lot/Serial number tracking at the Part and PartBin level, but note that Epicor's lot traceability is configured per Part rather than stored at the voucher line like Marg.
Marg ERP
Party / Ledger Account
Epicor Prophet 21
Customer and Supplier
1:manyMarg Parties are combined debtor-creditor ledger accounts. We split them by examining the Party Type flag and transaction history: Parties with only sales vouchers map to Epicor Customer; Parties with only purchase vouchers map to Epicor Supplier; Parties with both require Customer and Supplier records created separately. Marg's GSTIN, PAN, credit limits, payment terms, and outstanding balances transfer to the corresponding Epicor party tables. Opening AR/AP balances migrate as historical transactions against the party records.
Marg ERP
Voucher (Sales Invoice)
Epicor Prophet 21
Sales Order + Invoice
1:1Marg sales vouchers map to Epicor SalesOrder and corresponding Invoice records. The voucher line-level GST rate (CGST+SGST or IGST) is preserved as Epicor Tax connectivity records linked to the line. Marg's e-invoice and e-waybill reference numbers store as OrderHed extension fields since Epicor does not have native Indian e-invoicing. We flag vouchers with ABN billing references for the customer's admin to re-enter in Epicor.
Marg ERP
Voucher (Purchase Bill)
Epicor Prophet 21
Purchase Order + Receipt + Invoice
1:1Marg purchase vouchers map to Epicor POReceipt and corresponding AP Invoice records. Marg's party-wise GSTIN validation at purchase maps to Epicor's Supplier Tax ID validation. Marg's input tax credit tracking maps to Epicor's Tax Liability reporting. We preserve the voucher-level batch and expiry references for pharma purchases by attaching them as line-level notes in Epicor.
Marg ERP
Voucher (Credit Note / Debit Note)
Epicor Prophet 21
AR/AP Adjustment or Return
1:1Marg credit notes (sales returns) and debit notes (purchase returns) map to Epicor AR and AP adjustment records. The original voucher reference is preserved as a linked document. GST adjustment amounts transfer to the corresponding tax line in Epicor's tax engine.
Marg ERP
Godown (Stock Location)
Epicor Prophet 21
Warehouse
1:1Marg's Godowns map to Epicor Warehouses with the Godown code as WarehouseCode and the Godown name as WarehouseDesc. Inter-Godown stock balances transfer as Epicor PartBin initial quantities. Marg's Godown-level item re-order levels map to Epicor's PartWhse reorder settings. If Marg has sub-Godown locations (shelves, racks), we map those to Epicor Bins within the Warehouse.
Marg ERP
Godown Transfer
Epicor Prophet 21
Transfer Order
1:1Marg inter-Godown transfers map to Epicor Transfer Orders. Source Godown maps to FromWarehouse, destination Godown maps to ToWarehouse, and the transfer quantity with batch/expiry references transfer as Transfer Order lines. Transfer timestamps are preserved in Epicor's TransferOrderHed.
Marg ERP
Batch & Expiry Tracking
Epicor Prophet 21
Lot / Serial Number
1:1Marg batch number and expiry date stored at the voucher line level and in Marg's batch register map to Epicor Lot numbers with LotDescription carrying the expiry date as structured text. For pharma items requiring strict expiry enforcement, we configure Epicor's Part Lot Control to require Lot assignment at receipt and validate against expiry at shipment. Epicor's lot traceability is controlled at the Part level, not the voucher level like Marg, so the customer's Epicor admin configures Part Lot Control per item after migration.
Marg ERP
Fixed Asset
Epicor Prophet 21
Asset
1:1Marg's fixed-asset register (original cost, accumulated depreciation, net book value, useful life, and asset category) maps to Epicor Asset records. Marg uses Indian Schedule XIV straight-line and WDV depreciation methods; we extract net book value and recompute the depreciation schedule in Epicor's configurable depreciation engine. Any difference in the first year's charge is flagged in the reconciliation report. Marg's asset location (Godown) maps to Epicor Asset AssetAttribute or a linked Asset Location record.
Marg ERP
Chart of Accounts (Ledger)
Epicor Prophet 21
GL Account
1:1Marg's full account hierarchy (sales, purchase, expense, asset, liability, and statutory accounts for GST input/output, TCS, TDS) maps to Epicor GL Account records with AccountType and Category assignments. Marg's opening balances per ledger account migrate as Epicor GL Journal entries with a special journal entry type for opening balances. Statutory GST accounts require manual verification of the Epicor tax integration setup by the customer's accountant.
Marg ERP
Bank / Cash Account
Epicor Prophet 21
Bank and Cash Account
1:1Marg's bank accounts (including ICICI Bank integration for auto-ledger entries) and cash accounts map to Epicor Bank and Cash Account records. Bank reconciliation statements from Marg transfer as Epicor BankRec header records, with individual reconciliation lines mapped to matching transactions. Marg's cheque register maps to Epicor's payment running and cheque printing functionality.
Marg ERP
Stock Summary
Epicor Prophet 21
PartBin and PartWhse
1:1Marg's current stock summary (item-wise quantity per Godown) maps to Epicor PartBin records (item per warehouse per bin) and PartWhse records (item-warehouse assignment with reorder settings). Marg's stock valuation method (cost price, MRP, or last purchase price) maps to Epicor's inventory valuation method on the Part. Any negative stock in Marg is flagged and resolved before migration to avoid Epicor inventory validation errors.
Marg ERP
Custom Fields
Epicor Prophet 21
UD Fields (User-Defined)
lossyMarg's user-defined fields appear as extra columns in the export output but have no formal schema documentation. We identify each extra column during the parser build phase and map them to Epicor UD (User-Defined) fields on the corresponding table (Part_c, Customer_c, Supplier_c, etc.). Epicor's UD column setup requires the customer's Epicor admin to create the UD field definitions before data import; we provide the field list and sample values.
Marg ERP
Workflow / Automation
Epicor Prophet 21
Process Automation
lossyMarg workflows (auto-entry rules, alert triggers, e-waybill auto-generation rules) do not migrate as code. We document each active Marg workflow with its trigger condition, action, and applicable entity scope, and provide a recommended Epicor Kinetic Business Process Management or custom BPM equivalent. The customer's Epicor admin or implementation partner rebuilds them post-migration.
| Marg ERP | Epicor Prophet 21 | Compatibility | |
|---|---|---|---|
| Item | Part1:1 | Fully supported | |
| Party / Ledger Account | Customer and Supplier1:many | Fully supported | |
| Voucher (Sales Invoice) | Sales Order + Invoice1:1 | Fully supported | |
| Voucher (Purchase Bill) | Purchase Order + Receipt + Invoice1:1 | Fully supported | |
| Voucher (Credit Note / Debit Note) | AR/AP Adjustment or Return1:1 | Fully supported | |
| Godown (Stock Location) | Warehouse1:1 | Fully supported | |
| Godown Transfer | Transfer Order1:1 | Fully supported | |
| Batch & Expiry Tracking | Lot / Serial Number1:1 | Mapping required | |
| Fixed Asset | Asset1:1 | Fully supported | |
| Chart of Accounts (Ledger) | GL Account1:1 | Fully supported | |
| Bank / Cash Account | Bank and Cash Account1:1 | Fully supported | |
| Stock Summary | PartBin and PartWhse1:1 | Fully supported | |
| Custom Fields | UD Fields (User-Defined)lossy | Not supported | |
| Workflow / Automation | Process Automationlossy | Fully supported |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
Marg ERP gotchas
Marg-to-Marg native export is the only documented bulk data path
No public API means migration is always file-based
Cloud plan user-count and company-count gates are migration prerequisites
GST rate and composition tier are stored per transaction line, not per party
Marg's fixed-asset depreciation schedules use Indian Schedule XIV conventions
Epicor Prophet 21 gotchas
Third-party bolt-on integrations complicate migration scope
Dirty data without standardized processes compounds migration risk
SDK customizations and BPMs may not survive platform upgrades
Report-based export only for non-technical users
Per-user pricing model requires accurate user count before migration planning
Pair-specific challenges
Migration approach
Scoping and Marg export characterisation
We conduct a discovery call to enumerate all active Marg companies, voucher types, Godowns, batch tracking requirements, custom fields, fixed assets, and active workflows. We request a sample export from the customer's Marg system using the A/c & Inventory Export utility and reverse-engineer the column ordering and naming conventions. We identify any inactive Marg companies and flag them for exclusion. We confirm whether Marg's cloud or on-premise version is in use and whether the export utility is accessible. The scoping output is a written migration scope document with a custom parser specification for the identified Marg export format.
Epicor DMT schema preparation
We provide the customer with a UD field specification list (table name, field name, data type, length) for all Marg user-defined fields that will migrate. The customer's Epicor admin creates these UD fields in the target Epicor environment before migration begins. We also provide the Epicor tax code specification (CGST rate, SGST rate, IGST rate combinations) so that the customer's accountant or Epicor consultant can pre-load the Indian GST tax codes. We validate Epicor connectivity and DMT permissions with the customer's Epicor admin.
Marg data extraction and transform pipeline
We extract data from Marg in dependency order using the A/c & Inventory Export utility: Items first, then Parties, then Godowns, then Chart of Accounts, then Fixed Assets, then Vouchers (oldest first to preserve audit continuity). Each export is parsed using the custom parser built in Step 1. We build a GST rate-mapping table from all voucher lines, resolve the Party split (Customer vs Supplier vs both), map Godowns to Epicor Warehouses, and extract net book values for fixed assets. The transform pipeline outputs DMT-compatible CSV files for each Epicor entity.
Sandbox migration and reconciliation
We run a full migration into the customer's Epicor Sandbox environment (Full Copy or Partial Copy depending on data volume). The customer's operations lead reconciles record counts (Parts in, Customers in, Suppliers in, Warehouses in, GL Accounts in, Assets in, Orders/Receipts/Invoices in) and spot-checks twenty to fifty records per entity against the Marg source data. Godown-to-Warehouse mapping, GST rate assignment, batch/lot preservation, and fixed-asset opening balance accuracy are the primary reconciliation dimensions. We correct any mapping errors before production migration begins.
Production migration in dependency order
We run production migration in Epicor dependency order: Part UOM and Part records first, then Warehouse and PartBin initial stock, then GL Accounts, then Bank and Cash Accounts, then Fixed Assets, then Customer and Supplier records (with opening balances), then Sales Orders and AR Invoices, then Purchase Orders and AP Invoices, then Transfer Orders. DMT runs in batches of 2,000 records per entity with row-count reconciliation after each batch. Any record rejected by Epicor validation is logged, corrected in the source transform, and re-queued.
Cutover, delta sync, and automation handoff
We request a twenty-four-hour freeze window for the final delta export of any records created or modified after the initial export snapshot. We replay the delta into Epicor and disable write access to Marg for the cutover window. We validate Epicor's opening balances against Marg's final trial balance. We deliver the Marg workflow and automation inventory document to the customer's Epicor admin team with BPM rebuild recommendations. We provide a one-week hypercare window for reconciliation issues. We do not rebuild Marg workflows as Epicor BPMs inside the migration scope; that is a separate engagement or an internal admin task.
Post-migration data archive
We package the full Marg export files, transform logs, and DMT import logs into a structured archive (CSV and JSON) and deliver them to the customer for cold storage. Marg's accumulated historical data (old vouchers beyond the migration scope, audit logs, and attachment files) can optionally be archived to a separate data store to prevent performance load on the live Epicor environment. The customer retains the Marg archive for statutory audit access for the period required by Indian tax law.
Platform deep dives
Marg ERP
Source
Strengths
Weaknesses
Epicor Prophet 21
Destination
Strengths
Weaknesses
Complexity grading
Standard ERP migration. 2 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Marg ERP and Epicor Prophet 21.
Object compatibility
2 of 8 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
Marg ERP: Not publicly documented.
Data volume sensitivity
Marg ERP doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during Marg ERP to Epicor Prophet 21 migration scoping. Not seeing yours? Book a call.
Walk through your Marg ERP to Epicor Prophet 21 migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave Marg ERP
Other ways to arrive at Epicor Prophet 21
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.