Migrate from Agility ERP to Infor CloudSuite Corporate

Agility ERP customer records map to Infor CloudSuite Customer Master (PartBrw). Address, contact name, and payment terms transfer as standard fields. We use the Agility ERP customer code as the dedupe key and validate against Infor CloudSuite's 16-character code limit. Free-form address entries in Agility ERP may require normalisation before import into Infor CloudSuite's structured address schema.

Agility ERP vendor records map to Infor CloudSuite Supplier Master (SuppCode). Remit-to addresses, tax IDs, and payment terms transfer 1:1. We check for duplicate supplier names across the import set to prevent double-creation in Infor CloudSuite. Agility ERP's vendor code must be validated against Infor CloudSuite's 16-character Supplier Code limit before import.

Open sales orders transfer as line items with quantity remaining and order date preserved. Agility ERP's proprietary order status vocabulary (Open, Released, Backordered) requires a customer-specific status lookup table built during discovery, because Infor CloudSuite uses its own configurable status code tables. We align Agility's Open status to Infor CloudSuite Released, and flag any Agility-specific statuses that have no Infor equivalent for manual resolution before import.

Open purchase orders follow the same status vocabulary mapping logic as sales orders. Supplier reference fields transfer for audit trail continuity. Line-level PO data migrates to Infor CloudSuite PoHead and PoDetail records with quantity-open recalculated against received and invoiced quantities in Agility ERP at cutover time.

Inventory items carry cost layer data (average, FIFO, or lot cost) that requires explicit mapping to Infor CloudSuite's costing method configuration. Stock on hand and reorder point values transfer but may require re-evaluation in Infor CloudSuite's multi-warehouse context. We map Agility ERP warehouse or location codes to Infor CloudSuite warehouse codes, and flag any Agility-specific cost layers that do not map cleanly to Infor's standard costing setup.

Account codes, descriptions, and classification (asset, liability, expense, revenue) transfer to Infor CloudSuite Account Master (COA). Agility ERP account codes exceeding Infor CloudSuite's 36-character limit are flagged and renumbered during scoping. We deliver a GL code mapping table alongside the migrated chart of accounts so that all downstream journal entries reference the correct new account codes.

Fixed asset records are not accessible via the Agility ERP standard export layer. Customers with a non-zero fixed asset balance require a custom database extract from Agility ERP support, which adds lead time and may require a separate professional services engagement. We flag any customer with active depreciation schedules during scoping, coordinate the custom extract before the migration window, and map the asset register and depreciation schedules to Infor CloudSuite FixedAsset module after the COA is established.

Historical journal entries transfer as Infor CloudSuite GBL_JournalEntry records with line detail. Entries containing embedded account IDs from Agility ERP's legacy chart of accounts are flagged and remapped to the new COA before loading. Journal entry dates and amounts transfer; entry descriptions map to the memo field. We do not migrate audit history attachments stored outside the journal record.

Agility ERP stores custom fields in a non-standard extension table. Each custom field requires field-by-field review to identify the destination in Infor CloudSuite, either as a user-defined field on the target form or as a user table column. We inventory all custom fields during scoping, document the mapping, and provision the Infor CloudSuite schema with matching user-defined fields before the import phase begins. Any Agility-specific picklist values require equivalent code table entries in Infor CloudSuite.

Agility ERP users referenced on orders, quotes, and inventory records are matched by email address against Infor CloudSuite User records. Inactive or terminated Agility ERP users are mapped to inactive Infor CloudSuite Users to preserve assignment history without creating orphaned records. User provisioning in Infor CloudSuite is a prerequisite that the customer's admin completes before record migration begins.