Migrate from PILOT:Suite to Infor CloudSuite Corporate

PILOT:Suite Vendors map to Infor CloudSuite Business Partner records with Role set to Supplier. The external application database vendor table columns (vendor code, name, address, tax ID, payment terms) map to the corresponding Business Partner form fields. Business Partner is created before any Purchase Order import so that the supplier reference is satisfied. Vendors without a valid tax ID or payment terms in PILOT:Suite are flagged in a reconciliation report for the customer's AP team to validate before migration.

PILOT:Suite Customers map to Infor CloudSuite Business Partner records with Role set to Customer. Ship-to and bill-to addresses migrate as Business Partner Address records with address-type designations. Customer credit limits and payment terms are entered into the appropriate CloudSuite form; the Infor Migration Utility requires these to be present before Sales Order import. Any PILOT:Suite customer record with a duplicate tax ID is flagged for the customer's admin to resolve.

PILOT:Suite Items map to Infor CloudSuite Products. The PILOT:Suite item code becomes the CloudSuite Product number, and the item description maps to Product Description. Unit of measure, standard cost, and standard price migrate to the Product's cost and price fields. Revision control (introduced in Infor CloudSuite) is initialized at revision 00 for all migrated items. If PILOT:Suite uses lot or serial tracking on specific items, the lot and serial tracking flags are enabled on the corresponding CloudSuite Product.

PILOT:Suite stores item-warehouse assignments as a separate table where one item can have multiple warehouse-specific records (bin location, reorder point, quantity on hand, quantity committed). We expand each PILOT:Suite item-warehouse record into a separate Infor CloudSuite Product-Warehouse row. The quantity-on-hand values from PILOT:Suite transfer as initial inventory balances. If PILOT:Suite has open work orders referencing specific warehouse locations, the Infor Manufacturing module must be initialized before this phase runs.

Open PILOT:Suite Purchase Orders (status not fully received) migrate to Infor CloudSuite Purchase Orders with the same PO number preserved as a reference. Line items map from PILOT:Suite POLine to CloudSuite POLine with vendor part number, ordered quantity, received quantity (as zero since orders are open), and unit cost. The Business Partner (Supplier) reference must exist before this phase, requiring the Vendor mapping to complete first. Closed and fully-received PILOT:Suite POs are not migrated as live orders; their historical data is preserved in the PILOT:Suite archive per the customer's data-retention policy.

Open PILOT:Suite Sales Orders migrate to Infor CloudSuite Sales Orders with order number, order date, promised ship date, and all line items preserved. Line items map from PILOT:Suite SOLine to CloudSuite SOLine with product reference, ordered quantity, allocated quantity, unit price, and discount. The Customer Business Partner reference must exist before this phase. Any PILOT:Suite Sales Order referencing a discontinued Item is flagged for the customer's sales team to update before migration.

PILOT:Suite GL Accounts map to Infor CloudSuite financial structure accounts within the configured company and fiscal year. Account code, account description, account type (asset, liability, equity, revenue, expense), and the current period balance transfer. Year-end retained earnings balances from PILOT:Suite are entered manually in Infor CloudSuite's financial close forms as the migration does not carry historical fiscal year P&L history. PILOT:Suite custom account segments require pre-mapping to Infor's dimensional chart of accounts structure.

Unpaid PILOT:Suite AP vouchers, invoices, and checks are migrated as open AP in Infor CloudSuite. The voucher number, vendor reference, invoice date, due date, and open amount transfer. The vendor Business Partner must already exist, requiring Vendor migration to complete before AP. PILOT:Suite check registers that are unpaid at migration time are recreated as Infor payment documents. Any AP record with a mismatch between the PILOT:Suite vendor code and the new CloudSuite Business Partner code is flagged in the reconciliation report.

Unpaid PILOT:Suite AR invoices and credit memos migrate as open AR in Infor CloudSuite. Invoice number, customer reference, invoice date, due date, and open amount transfer. The customer Business Partner must already exist. PILOT:Suite payment history attached to open AR invoices is preserved as AR payment records in CloudSuite. AR records with disputed or partially-credited amounts are flagged for the customer's AR team to verify before migration.

PILOT:Suite custom fields defined on Items, Vendors, Customers, Purchase Orders, and Sales Orders are cataloged during discovery. Infor CloudSuite supports user-defined fields (UDFs) on most master and transactional forms. We pre-create these UDFs in CloudSuite before data migration, matching the PILOT:Suite data type (character, numeric, date, dropdown) to the Infor field type. Any PILOT:Suite custom field that has no CloudSuite UDF equivalent is documented in the scope for the customer's admin to address post-migration.