Migrate from PILOT:Suite to Epicor Prophet 21

PILOT:Suite Items map to Epicor Part records. The Item Number becomes PartNum, description migrates to the Description and ShortChar01 fields, and cost rolls forward into PartUnitCost. We resolve Part plant assignments by matching PILOT:Suite warehouse codes to Epicor Site codes during the Part insert phase. Stocking types (make, buy, service) map from PILOT:Suite item type flags to Epicor PartType values. Custom fields on Item (UDFs) map to Part CustomFields with type-matched Epicor field creation before import.

PILOT:Suite Warehouses map to Epicor Site records with a corresponding Warehouse record inside each Site. PILOT:Suite item-warehouse assignments become PartWhse records linking Part to Site-Warehouse. Bin locations in PILOT:Suite migrate to Epicor WhseBin records. Multi-company PILOT:Suite configurations map to separate Epicor Companies with inter-company AP/AR configured as separate legal entities.

PILOT:Suite Vendors map to Epicor Supplier records using the vendor code as the SupplierID. Address, contact, and payment terms migrate to the Supplier address book and PaymentTerms linkage. PILOT:Suite vendor-specific item pricing (vendor part numbers, lead times, minimum order quantities) migrates to Epicor SupplierPP records. Any inactive or duplicate vendors are flagged in a reconciliation report before import.

PILOT:Suite Customers map to Epicor Customer records using customer number as the CustID. Address, ship-to, contact, and credit hold status migrate to the Customer address book and CreditHold fields. PILOT:Suite customer-specific pricing and discount groups migrate to Epicor PriceLdisc records. Open AR aging from PILOT:Suite becomes Epicor AR invoices and credit memos with aging carried into the correct fiscal period.

PILOT:Suite Purchase Orders map to Epicor POHeader and POLine records. Header fields (PO number, vendor, date, terms) migrate to the POHeader; line items (part number, quantity, unit cost, due date) migrate to POLine with SupplierNum resolved from the Vendor-to-Supplier mapping. Open POs migrate with Release-level scheduling if PILOT:Suite carries release dates. Closed POs migrate as historical records with PODate in the past.

PILOT:Suite Sales Orders map to Epicor OrderHed and OrderDtl records. Header fields (order number, customer, ship date, terms) migrate to OrderHed with CustNum resolved from the Customer mapping; line items (part number, quantity, unit price, ship date) migrate to OrderDtl. PILOT:Suite multi-line sales orders become separate OrderDtl lines with lineType variants (make-to-order, stock, assemble-to-order) set from PILOT:Suite item type. Blanket POs and releases map to Epicor BlanketOrder equivalents.

PILOT:Suite GL Accounts map to Epicor GLAccount records within a Chart of Accounts structure. Account number, description, and type (asset, liability, equity, revenue, expense) migrate to GLAccount with NaturalAccount and USETaxType assigned. PILOT:Suite account segments (if any) map to Epicor COASegment values with the segment structure configured before migration. Active versus inactive status carries from PILOT:Suite to GLAccount InActive flag.

Open AP records from PILOT:Suite (invoices, debit memos, and credit memos with vendor and amount) migrate to Epicor APInvoice records with APLine entries. We carry forward invoice number, vendor reference, invoice date, due date, and open amount. PILOT:Suite payment applications migrate as APLink records. Historical AP aging is preserved for audit by storing the original PILOT:Suite aging bucket in a custom field on APInvoice.

Open AR records from PILOT:Suite (invoices, debit memos, and credit memos with customer and amount) migrate to Epicor ARInvoice records with ARLine entries. Invoice number, customer reference, invoice date, due date, and open amount carry forward. PILOT:Suite payment applications migrate as ARLink records. Customer credit status and payment terms resolve through the Customer mapping.

PILOT:Suite user-defined fields on Item, Vendor, Customer, PO, and SO map to Epicor UD fields (like ShortChar01, Number01, CheckBox01) or formal custom fields created before migration. We inventory every PILOT:Suite UDF during scoping, map the field type to the closest Epicor type, and create the Epicor schema before data migration. Fields without a direct Epicor equivalent are flagged with a type recommendation in the schema design document.

PILOT:Suite GL Account period balances (opening balances, current period activity) migrate to Epicor GLJrnDtl records for the target fiscal year. We align PILOT:Suite accounting periods to Epicor fiscal periods during scoping, and create GLJrnDtl batch entries for balance roll-forward with journal description referencing the PILOT:Suite migration source. Trial balance validation runs against Epicor's GL Report after import.

PILOT:Suite records item quantities and assignments per warehouse. These map to Epicor PartWhse records with PartNum and WarehouseCode resolved. Safety stock, reorder point, and ABC codes from PILOT:Suite migrate to the PartWhse fields. Quantity-on-hand carries from the PILOT:Suite inventory snapshot taken at migration date. We flag any PartWhse where the Part or Warehouse cannot be resolved due to inactive source records.