Migrate from metasfresh to Infor CloudSuite Corporate

metasfresh Business Partners map to Infor CloudSuite Customer and Vendor records. The C_BPartner table stores address, contact, and financial relationship data including the IsCustomer and IsVendor flags that determine whether to create one or two records in Infor. We preserve the bp_value as an external reference code and map the C_BP_Group to an Infor Business Partner Type. Organization assignment in metasfresh maps to Infor's multi-company or multi-site org structure if the destination is multi-site.

metasfresh Products map to Infor CloudSuite Items. The M_Product table includes product type (Item vs Service vs Resource), the product category (M_Product_Category), and unit of measure. We preserve the product's value as Item Code and map the product category to Infor's item group. Product cost information from M_Product_Costing records maps to Infor's cost element structure. Discontinued products flagged with IsActive=false in metasfresh map to Infor's inactive item status.

metasfresh Sales Orders (C_Order with IsSOTrx=Y and DocStatus in Draft, In Progress, or Completed) map to Infor CloudSuite Sales Orders. We reconstruct the full document tree including C_OrderLine records for each line item, preserving the M_Product reference, quantity, prices, and discount amounts. The C_DocType determines document type mapping in Infor. Open orders migrate with full line detail; completed and closed orders migrate as historical records.

metasfresh Purchase Orders (IsSOTrx=N) map to Infor CloudSuite Purchase Orders. Line items from C_OrderLine preserve the vendor part number, quantity, unit price, and date-promised fields. PO headers carry the C_BPartner reference (mapped to the Vendor record), the PO date, and document status. We do not migrate draft purchase orders unless the customer explicitly scopes them; completed and closed POs migrate as historical records.

metasfresh AR invoices (IsSOTrx=Y) map to Infor CloudSuite AR invoices; AP invoices (IsSOTrx=N) map to Infor AP invoices. We separate invoice headers from invoice lines (C_InvoiceLine) and preserve the reference to the originating C_Order if one exists, mapping it to the Infor purchase or sales order reference. Payment terms (C_PaymentTerm) map to Infor's payment term code. Document status (Draft, In Progress, Completed, Closed, Voided) migrates as-is.

metasfresh pricing is organized into M_PricingSystem containing multiple M_PriceList versions with effective date ranges. We export the full pricing hierarchy and create corresponding Infor Price Lists and versioned price entries. Each M_PriceListLine maps to an Infor price rule tied to an Item and Business Partner Type. Effective dates from metasfresh pricing rules become validity periods in Infor's price maintenance UI. Price list assignment to Business Partners migrates as customer-specific price list overrides.

metasfresh BOM data stored in pp_product_bom and pp_order_bomrecord tables maps to Infor CloudSuite Industrial's bill of materials structure. The finished product reference from pp_product_bom becomes the BOM header in Infor, and each component line from pp_product_bomline (component product, quantity per, scrap percentage, issue method) becomes a BOM line. We inspect the PP_Product_BOM table during discovery and include BOM lines only when the PP tables are populated and the MRP module is enabled in the source metasfresh instance.

metasfresh Projects (C_Project) have a header plus project lines tracking time, costs, and deliverables. We map the project header including project status, responsible user, and contract dates, and we migrate project lines (C_ProjectLine) with their associated phase and milestone structure. The C_BPartner reference on the project header maps to the Infor Customer or Vendor. Projects without a defined status default to Infor's Active status.

Bank accounts stored per organization in metasfresh and linked to Business Partners map directly to Infor Bank Account records. We preserve the IBAN or account number, SWIFT/BIC code, bank name, and the C_BPartner association. Payment methods (C_PaymentTerm) map to Infor's payment term codes and are loaded as reference data before invoice migration.

metasfresh tax categories (C_TaxCategory) and tax rates (C_Tax) map to Infor CloudSuite Tax Codes with their corresponding rate percentages and effective date ranges. Geographic zone-based tax rates from metasfresh map to Infor's tax jurisdiction hierarchy. We preserve the tax category name as a reference and ensure that all taxes referenced on invoice lines have a corresponding tax code in Infor before invoice migration begins.

metasfresh custom fields added via the Table and Column system are stored as rows in AD_Column with a custom flag. These are not surfaced in the standard export format. We query AD_Column during the discovery phase to identify all custom fields per table and include them as additional columns in the export. In Infor CloudSuite, we create corresponding user-defined fields using Infor's extension framework and map the values during migration. Custom field type mapping (string to text, integer to number, date to date) is handled during the schema design phase.

metasfresh customer complaints and repair workflows create service project records linked to returned products. We map the complaint header and related repair project, preserving the link back to the original Sales Order and returned product. Infor CloudSuite Industrial includes a Service Management module for warranty, service contracts, and repair tracking; we map complaint data to Infor Service cases with a reference back to the related item and sales order.