Migrate from ERPAG to Infor CloudSuite Corporate

ERPAG Items map to Infor CloudSuite Item master records (MITM/MITB tables). We extract SKU, description, unit cost, unit price, stock levels by warehouse, barcode, and UOM from the ERPAG Get Item endpoints. Multi-level BOM associations are resolved separately via the BOM export and imported after the base Item records. ERPAG's Advanced-plan custom fields on Items require plan verification before export; if the source account is on Basic or Professional, these fields do not exist in the data export.

ERPAG Customer records map to Infor CloudSuite Customer records. We extract contact info, billing address, shipping address, financial overview fields, and any B2B portal assignment. The customer-specific price list linkage (from ERPAG's multi-warehouse pricelist model) translates to Infor's Price Group (TPI) assignment on the Customer record. ERPAG B2B portal configuration does not migrate; we document the portal price tiers and access rules separately for Infor OS or B2B portal rebuild.

ERPAG Supplier records map to Infor CloudSuite Supplier records. The critical mapping is ERPAG's double-SKU layer: each Supplier record in ERPAG carries both the supplier's own SKU and ERPAG's internal SKU for the same item. We preserve this cross-SKU mapping in a supplier-item cross-reference table during migration so that Infor's Purchase Order generation references the correct supplier part number. Purchasing terms (payment days, lead time) map to Infor's Supplier Terms fields.

ERPAG Sales Orders map to Infor CloudSuite Customer Order. We export via Get Sales Order / Get Sales Order IDs and include the payment_status column. Line items map to Order Lines with resolved Item numbers (from the Item master), quantities, pricing, and discount rates. Open Sales Orders migrate first; closed orders migrate as historical records with status preserved. ERPAG's packing list associations are mapped to Infor's Shipment and Delivery records.

ERPAG Invoices generated from Sales Orders map to Infor CloudSuite Customer Invoice. Status, total amount, tax amount, and payment information are preserved. Credit Notes in ERPAG map to Infor's Credit Memo records. Tax codes and currency from ERPAG's document-level settings migrate to Infor's Tax Handling and Multi-Currency setup. Note: ERPAG's localization settings (currency, tax code) are set at company initialization and do not retroactively rewrite existing documents; we flag this during scoping and separate historical tax-currency reporting from go-live configuration.

ERPAG Purchase Orders map to Infor CloudSuite Purchase Order. The double-SKU entry (supplier SKU + ERPAG SKU) is resolved using the supplier cross-reference table to populate Infor's PO Line with the correct supplier part number. Goods-received state from ERPAG (automatic fulfillment logic) translates to Infor's Receipt and Inventory Update status. Purchase Order approvals and holds do not migrate as automation; we document the approval workflow for Infor's document approval rebuild.

ERPAG Quotations (estimates) with validity dates and custom fields map to Infor CloudSuite Quote. We export via Get Quotation endpoints and map to the destination quote or estimate object. Custom fields on Quotations (Advanced-plan only) require plan verification. Quotations convertible to Sales Orders in ERPAG map to Quotes with a status that Infor uses to trigger the SO generation workflow post-migration.

ERPAG Work Orders with BOM references, production status, and estimated vs. actual cost fields map to Infor CloudSuite Manufacturing Order. Multi-level BOM nesting (BOM referencing sub-assemblies that are themselves BOMs) must be fully expanded during export so that the complete routing and component structure is available in Infor's SFC tables. We export Work Order records via the Cube Data export and resolve estimated vs. actual cost fields into Infor's Cost Category entries.

ERPAG BOMs defining multi-level product structures for manufacturing map to Infor CloudSuite BOM (ICBO for standard BOMs, ICM for configurator/engineering BOMs). Multi-level BOM nesting is preserved; sub-assemblies that are themselves BOMs are migrated first, then parent BOMs are linked. ERPAG's BOM cost rollup data (estimated material and labor costs per level) migrates to Infor's Cost Structure. BOMs without active Items are flagged during scoping for customer review before migration.

ERPAG Warehouses with independent tax settings, currency, and price lists map to Infor CloudSuite Site (CMSM). Each ERPAG warehouse's geo-location data, tax configuration, and associated pricelist migrate to Infor's Site-level settings. Multi-warehouse pricelists in ERPAG (where the same Item has different prices per warehouse) denormalize into Infor's Price Group and Site-specific pricing rules. Warehouse-level stock balances migrate to Infor's Inventory balances by Site.

ERPAG Custom fields on Items, Customers, Suppliers, Sales Orders, and other objects are Advanced-plan only and must be verified against the source account's plan tier before scoping. If Advanced-plan is confirmed, we enumerate all custom field definitions during scoping, map their data types to Infor's extended field types (string, number, date, checkbox, dropdown), and include them in the destination schema pre-creation step. Custom fields that are linked-document references (pointing to external files) are flagged separately for manual reattachment post-migration.

ERPAG Users carry role-based permissions that gate access to documents and modules. We export user records and role assignments, but permission sets are destination-specific and must be rebuilt in Infor's role and authorization framework. Active vs. inactive user status migrates; inactive users are created as Inactive Users to preserve historical assignment references. ERPAG's plan-gated module access (Basic vs. Professional vs. Advanced) does not translate directly; we document the module access matrix for Infor admin rebuild.