Migrate from Finesse ERP to Epicor Prophet 21

Finesse Customer records (name, address, contact, payment terms, credit limits, tax IDs) map directly to Epicor Kinetic Customer. We preserve credit limits and tax IDs as native Customer fields. Multi-address Customer records in Finesse with distinct ship-to locations map to Epicor ShipTo records linked to the parent Customer by CustomerNum. Active versus inactive status carries over explicitly to prevent orphaned open AR at the destination.

Finesse Vendor master data (name, bank details, W-9 information, payment terms, multi-address records) migrates to Epicor Kinetic Vendor. Multi-address vendor records with distinct ship-from locations map to Epicor Vendors with multiple VendorPP records. Payment terms from Finesse map to Epicor Payment Terms by description match, with mismatches flagged for manual mapping before the AP module goes live.

Finesse GL account structure (account code, description, type, intercompany flags) migrates to Epicor Kinetic GL Account with full segment support preserved. Active versus inactive status is carried over explicitly to prevent post-migration posting errors. If Finesse uses a segment value that Epicor Kinetic reserves for natural account type, we flag it for the customer's Epicor administrator to resolve during configuration before any journal entry import.

Finesse Items map to Epicor Kinetic Part records. The Item number becomes PartNum; description, uom, and cost fields map directly. Finesse Item types (Mfg, Purch, Sales) map to Epicor PartType values. On-hand quantities migrate to PartWhse records linked to the Part and the warehouse code. Negative quantities or quantities below safety stock in Finesse are flagged for pre-migration reconciliation before Epicor inventory module activation.

Finesse BOM structures (multi-level, single-level, with or without operation steps) map to Epicor Kinetic BOM and BOM Revision records. We extract Finesse BOM headers, component lines, and quantity-per relationships and transform them into Epicor BOMs with revision management via the Item Engineering Workbench. If Finesse BOMs carry alternate components or yield factors, we map these to Epicor BOM alternatives and BOM reason codes. BOM revision dates from Finesse map to Epicor revision effective dates so that historical BOM states are recoverable.

Finesse routing data (work centers, labor rates, operation sequence, estimated hours) maps to Epicor Kinetic Job Operations. We extract routing headers and operation lines, then create Epicor Jobs with operations linked to the Part's routing definition. If Finesse stores operation-specific tooling or setup times, we map these to Epicor JobOper ToolKit and LaborDtl records. Work center codes from Finesse map to Epicor Resource Group or Resource definitions, with a reconciliation list for the customer's Epicor admin to assign actual resources.

Finesse Projects aggregate Jobs, costs, and milestones under a single project header. We extract project headers, status, and cost variance fields, then map them to Epicor Kinetic Project. Project phase structures from Finesse map to Epicor Project Phases. If Finesse stores WBS (Work Breakdown Structure) hierarchies, we map them to Epicor Project Task records with parent-task relationships preserved. Budget and forecast amounts map to Project Analysis codes for reporting.

Finesse Jobs represent the manufacturing execution unit and carry start dates, quantity, priority, and cost tracking. We extract job headers and line-level cost entries (labor, material, burden) and map them to Epicor Kinetic Job records with JobHead and JobOper tables populated. Job status from Finesse (Released, Complete, Closed) maps to Epicor Job status. If Finesse Jobs reference outside operations or subcontracted steps, these map to Epicor JobOper with Subcontract = true and the vendor reference carried in the JobOper VendorNum field.

Open invoices and credit memos in Finesse require vendor reference and payment term mapping to Epicor's AP Invoice and AP Payment tables. We export open AP as line-item detail rather than summary balances to preserve aging accuracy in Epicor. Invoice numbers, invoice dates, due dates, and amounts migrate to APInvHed and APInvDtl. Voucher numbers from Finesse map to Epicor APInvHed.VendorNum references resolved via the Vendor mapping. Unpaid credit memos migrate to APCreditMemo records linked to the same Vendor.

Open customer invoices and unapplied payments migrate to Epicor Kinetic AR Invoice and AR Payment with full aging detail. We flag any AR records with nested dispute or credit hold flags for manual review before destination activation. Invoice numbers, invoice dates, due dates, and amounts migrate to InvcHead and InvcDtl. CustomerNum references resolve via the Customer mapping. Unapplied customer payments migrate to CashReceipt records linked to the customer.

Finesse user-defined fields on master and transaction records export with their data types and values. We map Finesse UDF definitions to Epicor Kinetic UD fields (UD columns on UD tables) or BAQ (Business Activity Query) calculated fields depending on whether the field is transactional or analytical. Finesse date, numeric, and text UDF types map to Epicor data types (Date, Decimal, Character). Finesse dropdown UDFs with specific value lists map to Epicor combo boxes or list fields with the same allowed values.

Documents stored in Finesse (drawings, specs, photos, PDFs) migrate via file reference export or direct file copy depending on the storage backend. Engineering drawings linked to Items migrate to Epicor Part Attachments. Project documents migrate to Epicor Project Attachments. We flag any document older than the customer's retention window for manual review before migration. Linked versus embedded document storage is preserved in the metadata so that document hyperlinks in Epicor reference the correct path.

Finesse User records include roles, department assignments, and security permissions. We map active users to Epicor Kinetic User records by email match, preserving role names and team assignments. Department codes from Finesse map to Epicor UserCodes or a custom department field. Inactive Finesse users are exported with their last-active date and archived as inactive Epicor users. If Finesse stores employee records distinct from user accounts, those migrate to Epicor HR Employee records.

On-hand quantities by location and lot number migrate to Epicor Kinetic PartWhse records linked to Part and Warehouse. Lot numbers from Finesse map to PartLot records with the lot number and expiration date preserved. If Finesse tracks bin or location-level detail, we map these to Epicor PartBin records. Any negative quantities or quantities below safety stock are flagged in the reconciliation report for pre-migration resolution.