Migrate from MERCI to Infor CloudSuite Corporate

MERCI Customer records map to Infor CloudSuite Customer (or Account depending on the Infor edition deployed). We flatten billing and shipping addresses into separate address fields in the destination, and we resolve any MERCI custom customer type codes against Infor's customer type taxonomy during the preliminary data transfer phase. The customer name and unique identifier become the primary dedupe key, and any MERCI lifecycle or status flags map to corresponding Infor customer status values with a migration-context custom field preserving the original MERCI status code for audit.

MERCI Sales Order headers and line items map to Infor CloudSuite Sales Order (or the equivalent in Infor LN Industrial or Infor M3). We separate order headers and line items into distinct import sequences so that a partial failure on a line item does not block the entire order. Order dates, expiration logic, and pricing structures migrate with value-level translation for any picklist-coded discount or freight terms. The original MERCI order number is preserved as a custom field for cross-reference.

MERCI Invoices referencing orders carry payment terms and open versus closed status that must translate to Infor CloudSuite's invoice lifecycle. We embed the source MERCI order ID as a custom field in the destination invoice record so that the order-to-invoice linkage survives cutover. Open invoices and closed invoices migrate with their respective statuses; Infor's migration utility handles the AR/AP split based on document type at import time.

MERCI Items (products and services with pricing tiers) map to Infor CloudSuite Item or Material records depending on the Infor edition. Bundle and kit compositions in MERCI must be expanded into Infor's BOM and routing structure if the destination is Infor LN Industrial. We flag bundle expansion as a separate configuration step during scoping because it requires the customer's engineering team to validate BOM levels in the destination system. Item pricing schedules migrate to Infor's price list structure with the original MERCI SKU preserved in a custom field.

MERCI account codes and names map directly to Infor CloudSuite account records, but MERCI uses a simplified five-type classification (asset, liability, equity, revenue, expense) that must be verified against Infor's account type taxonomy during profiling. If MERCI uses a non-standard account type code, we create an import rule in Infor's migration utility to translate the source value to the target value before commit. Account segment structures (if MERCI uses multi-segment account codes) map to Infor's account code dimension configuration.

MERCI Vendor records parallel Customer records in structure. We apply the same address-flattening logic and apply the customer-type mapping pattern to vendor contacts and payment terms. Bank account details migrate as payment bank records in Infor. If MERCI vendors are linked to purchase orders, we ensure the vendor import sequence runs before any PO import sequence so that the vendor reference is satisfied at import time.

MERCI Employee records carry department, job title, and compensation fields that map to Infor CloudSuite Employee objects. Effective-dated compensation history is preserved as a set of compensation records in Infor rather than a single snapshot field. We flag any MERCI custom employee fields during profiling and map them to Infor extended data structures or custom fields as appropriate. The employee import sequence runs after department and cost center master data to satisfy organizational hierarchy references.

MERCI departments and cost centers are referenced by Employee, Sales Order, and Invoice records. We extract these as a standalone import sequence that runs before any transactional record import. Infor CloudSuite requires departments to be committed before employee assignments can reference them, so this sequence is the earliest data load after master data profiling is complete.

MERCI deployments commonly use custom picklist codes for order status, customer type, payment terms, and item categories that diverge from any notional baseline. We discover these during data profiling, create translation rules in Infor's Import Rule Definition form, and test them during the preliminary data transfer phase. Any picklist code with no direct Infor equivalent is escalated to the customer's admin for a manual mapping decision before final data transfer.

MERCI stores binary attachments in a proprietary blob store with no public export endpoint. We cannot retrieve order documents, images, PDFs, or other file attachments through any documented API or standard CSV export. Attachments are flagged as unsupported scope during scoping. Customers must independently download files from the MERCI UI or request a full blob export from their MERCI account manager. For Infor CloudSuite, we can link imported documents to records via Infor ION once they are present in Infor OS document management, but the ingestion into Infor OS is a separate manual or third-party step.