Migrate from Infor CloudSuite Corporate to Epicor Prophet 21

Infor CloudSuite hierarchical COA with cost center and department rollups maps to Epicor GL Account records. Infor stores account segments and rollup structures in its SQL migration database; we extract the full segment hierarchy and flatten it into Epicor's COA structure with the appropriate segment delimiter (typically dash or colon). In multi-company scenarios, we preserve the source company code as an Epicor Company identifier and map account segments accordingly. Department rollup assignments from Infor become Financial Dimension sets in Epicor that are applied to the GL Account maintenance.

Infor CloudSuite Customer master and address book entries map to Epicor Customer, ShipTo, and BillTo records. Infor's address book structure (address, phone, contact, tax registration) splits into Epicor's three-tier model. Payment terms, credit limits, and customer-specific pricing from Infor become Epicor Customer Price Group or Customer Part Cross records. Customer address hierarchy in Infor (parent-child locations) resolves to multiple ShipTo records under a single Epicor Customer.

Infor CloudSuite Vendor records map to Epicor Supplier. Address book entries (contact, phone, email) transfer as Supplier Contact records. Tax registration codes, payment terms, and W-9 information from Infor map to Epicor Supplier Tax Exempt and SupplierPP fields. We flag any Infor vendor-specific pricing conditions as requiring manual setup in Epicor Supplier Price Breaks because line-level pricing conditions are not a direct field-to-field map.

Infor CloudSuite Item records map to Epicor Part. Unit of measure conversions, costing method (FIFO, LIFO, Standard, Average), and stocking class from Infor transfer as Epicor Part UOM classes, Cost ID, and PartClass. Infor's item status (active, inactive, discontinued) maps to Epicor Part Type and the TypeCode (make, buy, service). Item warehouse stocking data per site becomes Epicor PartWh records for each warehouse.

Infor CloudSuite BOM structures map to Epicor PartMtl records. The parent item in Infor becomes the PartMtl.ParentPart in Epicor; component items become PartMtl.MtlPartNum. BOM quantities and scrap percentages transfer directly. Infor multi-level BOMs (sub-assemblies) require iterative traversal of the BOM tree, with each level creating PartMtl records at the appropriate revision level in Epicor. We flag phantom BOMs and lead-time-offset relationships as requiring Epicor job BOM configuration post-migration.

Infor CloudSuite Work Orders map to Epicor Job records. Work order header (number, status, type, priority) maps to JobHead.JobNum, JobHead.JobEngineer, and JobHead.JobReleased. Component lines map to JobMtl; routing steps map to JobOper. Open work orders migrate as Released or Firm jobs; closed work orders migrate as JobHead records with JobEngineer = false for audit trail only. We preserve the Infor work order start and due dates as Epicor JobHead.StartDate and JobHead.DueDate, and we flag any Infor work order-specific scheduling constraints as requiring Epicor JobsFifoConfig review.

Infor CloudSuite open payables require precise balance verification at cutover before migration to Epicor APInvoice. We extract invoice headers, distribution lines, and payment terms, then load into Epicor with APLn lines attached to APHead records. Open versus partially paid AP in Infor determines whether Epicor receives a fully open or partially paid invoice. Prepayments and debit memos require separate mapping to Epicor PaymentApply work. AP must reconcile to the penny against the GL before the Epicor period closes.

Infor CloudSuite open receivables extract as AR invoice headers with line distributions and payment terms. We map to Epicor ARInvoice records and attach ARLn lines with tax and amounts. Customer invoice numbers from Infor become Epicor ARInvoice.InvoiceNum for reference. Credit memos and prepayments from Infor map to Epicor AR Credit Memo records. Open AR aging buckets in Infor do not transfer as aged data; Epicor computes aging at runtime from invoice dates and payment terms.

Infor CloudSuite user-defined alphanumeric and numeric custom fields map to Epicor UD tables (UD01-UD10). We extract the custom field group definitions per item group or supplier group, then pre-create matching UD columns in Epicor before data load. Date-type custom fields require a SQL-level workaround in Infor because date fields cannot be queried via Enterprise Search; we extract date fields directly from the Infor SQL migration database. Epicor UD columns populate via BPM logic after initial record insert, not via direct import; we provide a post-load BPM template that the customer's Epicor admin wires to the appropriate BO events.

Infor CloudSuite Purchase Agreement headers map to Epicor Quote records (type = Supplier). Vendor, terms, and expiration date transfer as Quote fields. Line-level pricing, quantities, and UOM become Epicor QuoteLine records. Effective date ranges from Infor become Quote.EffectiveDate and Quote.ExpirationDate. We flag quantity-based release contracts as requiring Epicor blanket order setup because blanket orders in Epicor handle scheduled releases differently from Infor's purchase agreement line structure.

Infor Document Management stores file references and metadata attached to customer orders, purchase orders, and work orders. We migrate the association metadata (source record type, record ID, document type, file name) as Epicor Attachment records linked to the corresponding Job, Part, or PO. Binary file content does not transfer because Infor stores attachments in Infor Document Management storage; we provide a reference path so the customer's admin can reconnect documents post-migration.

Infor CloudSuite user accounts and role assignments map to Epicor User, Employee, and UserSec records. Infor role profiles are extracted and mapped to Epicor Security IDs (SecurityGrp). Infor company-specific permission assignments require Epicor Company-level security scoping. We extract all Infor users as Epicor User records with a flag indicating active/inactive; provisioning new Epicor users is a separate step the customer's admin completes because Epicor licenses users independently of the migration.