ERP migration
Field-level mapping, validation, and rollback between Marg ERP and Infor CloudSuite Corporate. We move data and schema; workflows are rebuilt natively in Infor CloudSuite Corporate.
Marg ERP
Source
Infor CloudSuite Corporate
Destination
Compatibility
11 of 12
objects map 1:1 between Marg ERP and Infor CloudSuite Corporate.
Complexity
BStandard
Timeline
10-14 weeks
Overview
Moving from Marg ERP to Infor CloudSuite is a cross-platform data migration from a legacy desktop-first Indian ERP to a multi-tenant AWS-hosted cloud suite. Marg ERP has no documented REST API; every migration is file-based, using Marg's built-in A/c & Inventory Export utility, which produces XLS or CSV dumps with non-standard column ordering that we parse per-customer per-version. Infor CloudSuite ships with a migration utility purpose-built for external data ingestion: it accepts source data through a migration database, generates a Data Assessment Report, and imports mapped tables in a defined dependency sequence. We manage the schema translation between Marg's entity model (Items, Parties, Vouchers, Godowns, Batch Registers, Fixed Assets, Chart of Accounts) and Infor CloudSuite's equivalent tables, preserve line-level GST rates rather than party-level defaults, and extract batch and expiry metadata for pharma compliance. Marg's custom fields and app-layer data (MargPay, eRetail) do not migrate. We deliver a written inventory of Marg workflows and automations for the customer's Infor admin to rebuild post-migration.
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.
Source platform
Marg ERP platform overview
Scorecard, SWOT, gotchas, and pricing for Marg ERP.
Destination platform
Infor CloudSuite Corporate platform overview
Scorecard, SWOT, gotchas, and pricing for Infor CloudSuite Corporate.
Data migration guide
The complete Infor CloudSuite migration guide
Data model, import mechanisms, field mapping strategy, pitfalls, and cutover — by the engineers running it.
Destination checklist
Infor CloudSuite migration checklist
Pre- and post-cutover tasks for moving onto Infor CloudSuite Corporate.
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 Infor CloudSuite Corporate, 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 (Products)
Infor CloudSuite Corporate
Item (Product Master)
1:1Marg Items carry MRP, HSN/SAC codes, batch tracking, and salt names for pharma. We map Marg item fields to Infor CloudSuite's Product Master (Item master, Item warehouse, and Item cost records), handling multi-unit-of-measure via Infor's unit-of-measure class structure and mapping Marg's MRP to the Item's price field with the applicable price list type. HSN codes map to the Infor tax classification. Godown-level stock quantities from Marg's stock summary export map to Infor's Item Warehouse records per location.
Marg ERP
Party (Ledger Account)
Infor CloudSuite Corporate
Customer / Supplier
1:manyMarg Parties with Party Type of Customer map to Infor Customer; those with Party Type of Supplier map to Infor Supplier. Marg GSTIN, PAN, credit limit, and payment terms map to the corresponding Infor entity fields. Marg stores opening balances per Party; these map to Infor AR/AP open item records. If multiple Marg companies are consolidated into a single Infor entity, we merge duplicate Parties by GSTIN dedupe key and flag any conflicts in the Party reconciliation report.
Marg ERP
Voucher (Sales Invoice)
Infor CloudSuite Corporate
Sales Invoice / AR Invoice
1:1Marg Sales Vouchers map to Infor AR Invoice. Marg stores GST rate (CGST+SGST or IGST) at the voucher line level; we extract every distinct line-level rate code and build a GST rate-mapping table that drives Infor's tax engine configuration before invoice import. Marg's e-invoice reference number (if generated) maps to Infor's external reference field. The voucher status (Posted, Pending, Cancelled) maps to Infor's Invoice status.
Marg ERP
Voucher (Purchase Bill)
Infor CloudSuite Corporate
Purchase Invoice / AP Invoice
1:1Marg Purchase Vouchers map to Infor AP Invoice with the same line-level GST extraction logic as sales. Marg's e-waybill reference on purchase entries maps to Infor's external reference. Marg's supplier invoice number stored in the voucher narration field maps to Infor's supplier invoice number for 2B matching.
Marg ERP
Voucher (Credit Note / Debit Note)
Infor CloudSuite Corporate
AR Credit Memo / AP Debit Memo
1:1Marg Credit Notes and Debit Notes map to Infor AR Credit Memos and AP Debit Memos respectively, with the original voucher reference preserved as a linking field. The line-level GST rate on the original transaction is used to validate that the credit or debit note's tax reversal matches at the destination.
Marg ERP
Godown (Stock Location)
Infor CloudSuite Corporate
Warehouse
1:1Marg Godowns map directly to Infor CloudSuite Warehouse records. We preserve inter-Godown stock balances by extracting Marg's Godown-wise stock summary and mapping each Godown to its corresponding Infor Warehouse. Godown-level item balances (opening stock, closing stock) map to Infor Item Warehouse opening quantities. Marg's Godown address and contact details map to the Infor Warehouse address fields.
Marg ERP
Batch and Expiry Register
Infor CloudSuite Corporate
Lot / Serial Number Tracking
1:1Marg's batch number and expiry date stored at voucher line and stock level migrate to Infor's Lot/Serial number tracking via the Item Lot Master. For pharma distributors, we preserve the batch manufacturing date, expiry date, and batch supplier as structured lot attributes. Infor CloudSuite Industrial's lot traceability features support forward and backward lot traceability that mirrors Marg's batch tracking scope.
Marg ERP
Fixed Asset Register
Infor CloudSuite Corporate
Fixed Asset
1:1Marg maintains fixed assets with cost, accumulated depreciation, and useful life under India's Schedule XIV conventions. We extract net book value, accumulated depreciation, and original cost separately and create Infor Fixed Asset records with the original cost and accumulated depreciation entered as opening values. Marg's straight-line and written-down-value depreciation schedules map to Infor's depreciation method configuration, with any first-year difference flagged for admin review.
Marg ERP
Chart of Accounts
Infor CloudSuite Corporate
Chart of Accounts
1:1Marg's account hierarchy including statutory accounts for GST Input, GST Output, TCS, and TDS maps to Infor's Chart of Accounts. Marg's opening balances per account transfer to Infor's general ledger opening balance records. Marg company-level account structures are consolidated if multiple Marg companies migrate to a single Infor legal entity. We flag any account codes that conflict with Infor's reserved account number ranges.
Marg ERP
Bank / Cash Account
Infor CloudSuite Corporate
Bank Account / Cash Account
1:1Marg bank account balances, cheque register, and bank reconciliation statements export via the bank book report. These map to Infor Bank Account records with the current balance as the opening reconciled balance. Unreconciled cheques map to Infor's outstanding cheque register as open items. Marg's ICICI Bank auto-ledger integration details are noted as a configuration reference for the customer's Infor admin to re-establish with their bank.
Marg ERP
Custom Fields
Infor CloudSuite Corporate
N/A
1:1Marg does not expose a formal custom-field API. User-defined fields appear as extra columns in the export output and are handled as ad-hoc mappings where possible, but field-level preservation cannot be guaranteed for all custom field types. We include a column-by-column inventory of all extra export columns in the scoping report and map them to Infor wherever the Infor schema supports an equivalent custom field. Any unmapped custom fields are documented for manual entry or Infor customization scope.
Marg ERP
Mobile App Data (eRetail, MargPay)
Infor CloudSuite Corporate
N/A
1:1Marg's eRetail, salesman app, and MargPay transaction data are stored in subsidiary systems that do not share a common data store with the main Marg ERP database. These records are not accessible via the A/c & Inventory Export utility and are outside migration scope. Any transactions recorded exclusively in the mobile app must be reconciled manually or re-entered in Infor CloudSuite post-migration.
| Marg ERP | Infor CloudSuite Corporate | Compatibility | |
|---|---|---|---|
| Item (Products) | Item (Product Master)1:1 | Fully supported | |
| Party (Ledger Account) | Customer / Supplier1:many | Fully supported | |
| Voucher (Sales Invoice) | Sales Invoice / AR Invoice1:1 | Fully supported | |
| Voucher (Purchase Bill) | Purchase Invoice / AP Invoice1:1 | Fully supported | |
| Voucher (Credit Note / Debit Note) | AR Credit Memo / AP Debit Memo1:1 | Fully supported | |
| Godown (Stock Location) | Warehouse1:1 | Fully supported | |
| Batch and Expiry Register | Lot / Serial Number Tracking1:1 | Fully supported | |
| Fixed Asset Register | Fixed Asset1:1 | Fully supported | |
| Chart of Accounts | Chart of Accounts1:1 | Mapping required | |
| Bank / Cash Account | Bank Account / Cash Account1:1 | Fully supported | |
| Custom Fields | N/A1:1 | Not supported | |
| Mobile App Data (eRetail, MargPay) | N/A1:1 | Not 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
Infor CloudSuite Corporate gotchas
Infor OS tier-based usage limits gate API and BaaS capabilities
Custom Fields use inconsistent naming across Infor editions
SQL migration utility requires source database access
Multi-site and multi-currency data require separate period closure sequencing
REST API payload and timeout limits restrict bulk migration throughput
Pair-specific challenges
Migration approach
Discovery and export characterisation
We audit the source Marg ERP installation across all active companies, identifying the Marg version, installed modules (pharma, retail, FMCG), and export utility availability. We request sample exports from each module (Items, Parties, Vouchers, Godowns, Batch Register, Fixed Assets, Chart of Accounts, Bank Book) and reverse-engineer the column layout per export. We also identify any inactive companies, zero-balance accounts, and records pending e-invoice or e-waybill generation. The discovery output is a written migration scope, a Marg export format characterisation report, and an Infor CloudSuite edition recommendation based on the customer's industry and functional requirements.
Infor schema preparation and prerequisite data setup
We work with the customer's Infor implementation team to configure the Infor CloudSuite target environment: creating warehouse codes, unit-of-measure class structures, HSN/SAC tax rate schedules, GSTIN configuration for Indian compliance, and Chart of Accounts structure. We configure Infor's tax engine using the GST rate-mapping table built from Marg's line-level voucher data. Infor's migration database is provisioned as a staging layer between the parsed Marg export and the Infor production tables. This phase requires Infor admin access and runs concurrently with export characterisation.
Export parsing, transformation, and sandbox migration
We run Marg's A/c & Inventory Export for each module and parse the output using the version-specific parser built in scoping. GST rate codes, batch numbers, expiry dates, and Godown references are extracted as structured fields. Vouchers are sequenced by dependency: Parties before Vouchers, Items before Vouchers, Godowns before stock balances. We run a sandbox migration into Infor CloudSuite using a partial or full copy of the parsed data to validate the mapping, check the Data Assessment Report for row-level errors, and reconcile record counts against Marg source totals before any production data moves.
Owner and location reconciliation
We reconcile Marg Godowns (stock locations) to Infor Warehouse codes and flag any Godowns without a corresponding Infor warehouse. Marg's fixed-asset custodians are mapped to Infor Fixed Asset owners. Marg bank accounts are mapped to Infor Bank Account records with current and opening balances validated. Any unmapped Godowns or bank accounts go to a reconciliation queue for the customer's Infor admin to resolve before the production migration phase begins.
Production migration in dependency order
We run production migration in strict record-dependency order: Chart of Accounts and opening balances first, then Godowns and Warehouses, then Items and Products, then Parties (Customers and Suppliers), then Vouchers (sales invoices, purchase bills, credit notes, debit notes in sequence), then Batch and Lot Register data, then Fixed Assets, then Bank/Cash reconciliations. Each phase emits a row-count reconciliation report and a sample record validation against the Marg source before the next phase starts. GST rate validation runs as a separate check after voucher import, comparing Infor's calculated tax against Marg's stored line-level tax.
Delta export, cutover, and automation handoff
We schedule a final delta export of any records created or modified in Marg between the initial export date and the cutover date, apply the same parsing and transformation, and import the delta into Infor. We freeze Marg write access during the final 24-to-48-hour window and validate Infor live data completeness before declaring cutover. We deliver a written inventory of Marg workflows, custom fields, e-invoicing templates, and any Marg-specific automations that require rebuild in Infor CloudSuite's workflow or Infor OS process automation tools. We do not rebuild Marg automations as Infor workflows inside migration scope; that work is handed off to the customer's Infor admin or implementation partner.
Platform deep dives
Marg ERP
Source
Strengths
Weaknesses
Infor CloudSuite Corporate
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 Infor CloudSuite Corporate.
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 Infor CloudSuite Corporate migration scoping. Not seeing yours? Book a call.
Walk through your Marg ERP to Infor CloudSuite Corporate 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 Infor CloudSuite Corporate
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.