Migrate from Priority ERP to Infor CloudSuite Corporate

Priority Customers (header records with price lists, credit limits, and multi-address hierarchies) map to Infor CloudSuite Customer records. We extract the customer name, billing and shipping addresses, payment terms, credit limit, and price list assignment via p-level procedures, then map to Infor's Customer table with address data decomposed into Infor's address structure. Multi-address hierarchies in Priority (bill-to, ship-to) become separate Infor Customer Address records linked by AddressCode.

Priority Vendors share a similar structure to Customers, with pay-to and ship-from address hierarchies and purchasing-specific fields. We extract the full vendor record including purchasing terms and tax registration, then map to Infor CloudSuite Supplier. Vendors require the same address decomposition as Customers, with multiple address codes preserved as Supplier Address records.

Priority Items carry part numbers, BOM links, stocking dimensions, and warehouse-specific quantities. We extract item headers and variant attributes including multi-unit-of-measure conversions, cost layers, and warehouse quantities. In Infor CloudSuite Industrial (SyteLine), items map to the Item Master with stocking UOM, cost method, and BOM structure preserved. Multi-warehouse quantity breakdowns in Priority map to Infor's warehouse-specific quantity records.

Priority Sales Orders include header fields (customer reference, terms, freight) and multi-line details with pricing, discounts, and tax allocation. We extract the full order structure and map to Infor CloudSuite Sales Order. Line-level pricing, discount percentages, and tax codes transfer to Infor's order line table. Open orders (not yet invoiced) migrate as open Sales Orders; completed orders migrate as historical records if the scope includes closed-transaction history.

Priority Purchase Orders mirror the Sales Order structure but belong to the Vendors dimension. We extract PO headers and lines, mapping them to Infor CloudSuite Purchase Order. Line-level quantities, costs, and delivery dates transfer. We resolve the Infor Supplier reference at migration time using the vendor mapping from the Vendor step.

Priority supports multi-segment account codes representing company, department, and cost center simultaneously (for example, 01-100-320). Infor CloudSuite expects flat account codes with separate dimension fields. We decompose each Priority segment during mapping and flag any accounts where segment semantics cannot be cleanly represented in Infor's dimension model, requiring explicit customer approval before finalizing the mapping. This is one of the highest-risk transformation steps in the migration and must be validated against the trial balance before proceeding.

Outstanding invoices and credit memos are tracked as open documents linked to Customers, Vendors, and GL accounts. We extract open document totals, due dates, and aging buckets from Priority's open invoice aging report. Infor CloudSuite receives these as open AP or AR transactions. Load sequencing is critical: we insert Customers and Vendors (steps 1-2) before open AP/AR documents so that aging calculations resolve correctly against the customer and vendor master records. We validate total open AR and total open AP against Priority's trial balance post-load.

Priority Projects track budgets, assignments, billing records, and milestones. We extract project headers and associated WBS rows, time entries, and billing details, mapping them to Infor CloudSuite Project. In SyteLine, Project is an optional module; we verify the customer's Infor license includes Project before attempting this mapping. Budget rows map to Infor Project Cost Budget, and milestone billing maps to Infor Project Invoice schedules.

Employee records include org unit assignments and role-based permissions. We extract the employee file noting that salary and benefits data require explicit customer sign-off due to data sensitivity and GDPR or equivalent privacy law requirements. Employee records migrate as Infor Employee with org unit assignments mapped to Infor's department and cost center structure. Owner (sales rep, purchaser) references in Priority map to Infor User via email matching.

Journal Entries consist of debit and credit lines linked to account codes, with support for reversing entries and recurring templates. We extract full entry details including posting date, period, and description. In Infor CloudSuite, journal entries load via the GL Journal Entry form or migration utility with account codes resolved to the flat account structure established in the Chart of Accounts mapping. Reversing entries and recurring templates are documented separately as they require manual recreation in Infor.