Migrate from ERPNext to Infor CloudSuite Corporate

ERPNext Customer DocType maps to Infor Customer Party record. The ERPNext Customer Name, primary email, and phone migrate to Infor's Name, Primary Contact Email, and Primary Contact Phone fields. Address records (ERPNext Address DocType) map to Infor Address records linked via the Customer's address book. We run a pre-import deduplication pass against the existing ERPNext database to merge duplicate customer names before generating the Infor import file.

ERPNext Supplier DocType maps to Infor Supplier Party record. Supplier type, PAN/GST registration, and default currency from ERPNext migrate to Infor Supplier fields. ERPNext's Supplier Item cross-reference (preferred supplier per item) maps to Infor's Item Supplier cross-reference table. We extract the full supplier-address and contact relationship as relational CSVs to preserve address lookup integrity in Infor.

ERPNext Item DocType maps to Infor Item Master. Item Group from ERPNext becomes Infor's Item Group; brand, UOM (unit of measure), and barcodes migrate directly. ERPNext's valuation method (FIFO, Moving Average, Standard Rate) maps to Infor's cost method field. Custom fields stored in the ERPNext Custom Field DocType are exported separately and mapped to Infor custom fields on the Item Master during schema build. Item images export as file metadata with URL references for re-download during Infor load.

ERPNext supports nested BOMs to arbitrary depth with operation routing and workstation definitions. We flatten the BOM tree during extraction into a flat component list with parent item and quantity per assembly, then reconstruct it in Infor's BOM structure. Multi-level BOM routing (operation sequences, workstation assignments, cycle times) maps to Infor's routing and work center definitions as configuration records. Infor's BOM validation rules are applied after load to catch missing components or invalid quantities. Tier and edition constraints: Infor CloudSuite Industrial includes full BOM and routing management; CloudSuite Distribution focuses on kit-level assembly without routing complexity.

ERPNext's Stock Ledger (v14+ with perpetual inventory) stores every stock movement as a separate DocType record. We extract open stock balances as of the migration date and closed transactions (for audit trail) as a separate historical archive file. Infor's inventory model (periodic vs perpetual) must be confirmed during scoping, as this changes how stock balances are loaded. Warehouse structure with bin-level data from ERPNext maps to Infor's warehouse and location hierarchy.

ERPNext Sales Order DocType maps directly to Infor Sales Order. Order header fields (customer reference, po_no, delivery date) migrate to Infor's corresponding header fields. Line items with packed items and product bundle components extract as separate relational CSVs so the full order structure (including sub-items) is preserved. Open Sales Orders migrate with their current status; cancelled and completed orders archive to a separate historical file. Taxes and discounts from ERPNext's tax rule engine map to Infor's tax code assignments.

ERPNext Purchase Order DocType maps to Infor Purchase Order. Supplier, purchase series, and schedule dates migrate directly. Line items with UOM, quantity, and rate from ERPNext map to Infor POLine. Open Purchase Orders (not yet received) migrate with status preserved; closed POs archive separately. ERPNext's auto-receipt workflow flag maps to Infor's receipt tolerance settings.

ERPNext Invoices map to Infor Invoice documents. This is the highest-risk mapping in the migration because ERPNext v14+ decouples payments from invoices via the Payment Ledger. We run a pre-extraction join across Sales Invoice, Payment Entry, and Payment Ledger to determine each invoice's actual paid/unpaid status before mapping to Infor. Invoices identified as paid in the Payment Ledger are set to Paid status in Infor; unpaid invoices carry their outstanding amount. A mismatch between the ERPNext invoice status and the Payment Ledger resolution results in Infor invoices appearing unpaid even when settled, which must be corrected before go-live.

ERPNext Project DocType with nested Tasks, assignees, time logs, and milestone dates maps to Infor Project. We flatten the ERPNext project hierarchy: top-level tasks become Infor work breakdown structure items, and subtasks preserve the parent-child relationship via the Infor task numbering scheme. Time logs from ERPNext migrate as project labor entries in Infor. ERPNext's Project Type and billing details map to Infor's project classification and billing method fields.

ERPNext Employee DocType stores department, designation, date of joining, salary structure, and attendance records across multiple DocTypes. We consolidate these into an Infor Employee profile: basic demographics, organizational assignment (company, department, cost center), employment dates, and salary structure. ERPNext attendance and leave records migrate as historical attendance data if the destination Infor edition supports HR analytics. ERPNext's salary slip history (pay period, gross, deductions, net) maps to Infor's payroll history records if payroll is in scope.

ERPNext's Custom Field DocType registry (parent DocType, fieldtype, options, mandatory flags) is exported separately as a field-level inventory. We create Infor custom fields matching the ERPNext fieldtype to Salesforce-style field type mapping (varchar to Text, Int to Number, Date to Date, Check to Boolean). Custom field values are loaded after the base schema is validated. Any custom fields referencing ERPNext-specific picklist options require manual option value mapping in Infor.

ERPNext File DocType references blob storage (Frappe private files or S3-compatible). We export file metadata (filename, URL, doctype reference, creation date) and copy binary files to a staging location. File references in Infor link to the Document Management module attached to the relevant record (Customer, Item, Order, Project). We do not migrate the full ERPNext file storage structure; we deliver a file migration index mapping ERPNext document references to Infor document IDs for manual re-association by the customer admin.