Migrate your Infor CloudSuite Corporate data

Infor CloudSuite uses a hierarchical COA structure with cost center and department rollups. We map source accounts to destination account codes directly, preserving department assignments and currency assignment per company. Validation runs against Infor's account type rules before final load.

Customer and Vendor master records are separate objects in Infor CloudSuite. We extract address books, payment terms, credit limits, and tax registration codes, then load via the migration database using Infor's validation checks. Deduplication against existing records requires a pre-merge audit.

Items in Infor CloudSuite carry unit of measure conversions, costing method, BOM linkages, and warehouse-specific stocking data. We map the core item record 1:1, but UOM conversion tables and warehouse stocking levels require separate row-level mapping since source systems vary widely in how they represent these.

Open payables and receivables require precise balance verification at cutover. We extract open invoice headers and lines, then apply payment terms and aging buckets. Infor's distribution records (invoice distributions to accounts and cost centers) must be mapped field-by-field since the column names differ across Infor editions.

Purchase Agreements include both header fields (vendor, terms, expiration) and line-level pricing, quantities, and UOM. We map the header 1:1 but flag line-level pricing conditions as requiring customer review since pricing formulas in Infor can reference custom fields and cost models.

Work orders carry routing steps, material allocations, and status. We preserve the work order header, component lines, and routing sequences. Open versus closed status determines whether the order is included in the cutover or archived separately. Completed work order history can be migrated as reference records.

Infor CloudSuite allows user-defined alphanumeric, numeric, and date fields attached to items, suppliers, and purchase agreements. Custom field groups are defined per item group or supplier group. We extract custom field definitions as part of the schema map and apply the same group assignments in the destination environment. Date-type custom fields have a documented query limitation in Infor Enterprise Search.

Infor Document Management stores attachments against customer orders, purchase orders, and work orders as configurable widgets. We migrate the association metadata and file references, but binary file transfer depends on the customer's document storage backend. We flag any documents that reference external storage paths for manual recovery.

Audit logs and background task definitions are Infor OS infrastructure records that are environment-specific and not meaningful in a destination system. We do not migrate these. Transaction-level audit trails from financial periods are migrated as part of journal entry history.

User accounts, role assignments, and permission groups require mapping to the destination system's user directory. We extract the Infor role profiles and map them to equivalent destination permissions. Owner assignments on records (e.g., sales reps, buyers) are mapped via a cross-reference table built during the discovery phase.