Migrate from ERP Mark 7 to Infor CloudSuite Corporate

ERP Mark 7 Customer records with address, contact details, and payment terms map to Infor CloudSuite Business Partner records with Role = Customer. We use the customer account number as the Business Partner ID or generate a mapping table. Payment terms, credit limits, and 1099 settings transfer to the corresponding CloudSuite fields. If the destination CloudSuite instance uses a shared Business Partner model (Customer and Vendor share one record with roles), we set both role flags and deduplicate by tax ID.

ERP Mark 7 Vendor records map to Infor CloudSuite Business Partner records with Role = Supplier. W-9 status, 1099 settings, and payment terms transfer to the corresponding CloudSuite fields. Vendor addresses may require splitting if CloudSuite distinguishes between Remit-To and Ship-From addresses, which are separate fields in Infor's address model.

ERP Mark 7 Items (products, raw materials, services) map to Infor CloudSuite Item records with the appropriate item type code. ERP Mark 7 custom properties per item type (inventory vs. non-inventory vs. service) map to CloudSuite user-defined fields or Infor OS extension attributes. We run a schema-audit sample export during discovery to identify all custom item properties before committing to a mapping list.

ERP Mark 7 BOM records associated with Work Orders map to Infor CloudSuite BOM structures. Multi-level BOMs (parent assemblies with sub-assemblies) require recursive traversal during migration. We map the ERP Mark 7 routing steps to CloudSuite operations, with machine-center assignments mapped to CloudSuite work center codes.

ERP Mark 7 Work Orders link Items to BOMs and routing steps. Custom fields on work orders (machine center, priority flags, work-in-process status) require explicit mapping to Infor CloudSuite user-defined fields or a supplemental import pass if the destination schema has no equivalent. We preserve the work order status, start date, and completion date to support WIP reconciliation in CloudSuite.

ERP Mark 7 COA account numbers and names map directly to Infor CloudSuite COA entries. Non-standard segment configurations (cost center, region, or department segments beyond the standard debit/credit account) require manual re-creation in CloudSuite because segment structure is destination-side configuration not driven by import. We flag any non-standard segments during scoping and document them for the customer's Infor administrator.

Open receivables migrate as Infor CloudSuite AR transactions with invoice date, due date, aging bucket, payment method, and paid status preserved. We chunk open AR records by invoice date and payment status to avoid duplicate invoice creation in CloudSuite. Partial payments require the original invoice and the payment record as separate line items with a payment application link.

Open payables migrate as Infor CloudSuite AP transactions with the same sequencing logic as Open AR. We preserve vendor invoice number, invoice date, due date, and aging bucket. Prepayments and credit memos migrate as separate AP document types with a netting reference to the original invoice.

Multi-year transaction history segments by fiscal-year close status. Closed fiscal year journal entries migrate as locked historical records with the original posting date and a closed-period flag. Current fiscal year transactions migrate as open-period entries for live reconciliation. We require the customer to confirm fiscal year boundaries and any special close procedures before we begin. Historical data that exceeds the cloud transactional database performance target may be routed to Infor Data Lake for reporting access.

ERP Mark 7 User records (name, email, role, department assignment) map to Infor CloudSuite User records. Role names do not map 1:1 to Infor's permission model, so we match by permission level and flag roles that require manual reassignment in the destination. Department assignments map to Infor CloudSuite cost center or location hierarchies, with nested ERP Mark 7 department structures flattened or preserved based on the destination's hierarchy depth capability.

ERP Mark 7 documents attached to transactions, items, or customers export in native format and re-attach to the corresponding Infor CloudSuite records via Infor IDM (Infor Document Management). Binary attachments are chunked by file size, with a mapping table linking the source document ID to the destination IDM document reference. Large file attachments (over 50 MB) require separate handling and may be archived with a link rather than inline-embedded.

ERP Mark 7 tax codes map to Infor CloudSuite tax codes by jurisdiction and product-category combination. Active tax codes transfer; deprecated or jurisdiction-specific codes that have no CloudSuite equivalent are flagged during scoping. We recommend the customer's Infor administrator review regional tax compliance settings post-migration since tax code logic is jurisdiction-sensitive.