Migrate from Kafinea to Epicor Prophet 21

Kafinea Customers map to Epicor Customer records. We extract contact details, addresses, and payment terms via the Kafinea REST API and map them to Epicor's Customer table with associated ShipTo and Con用水 (contact person) records. Customer type (individual vs company) maps to CustType in Epicor, and payment terms map to the Epicor Terms table. Primary contact relationships are preserved as Con用水 linked to the Customer record.

Kafinea's three invoice types require pre-import configuration of Epicor's invoice form set. Classic invoices map directly to Epicor ARInvcHead + ARInvcDtl records. Progress invoices (milestone-based billing) map to Epicor Mixed billing with billing line types configured per milestone. Recurring invoices map to Epicor Recurring Invoice templates with frequency and next-run date preserved. Invoice-to-payment links migrate as ARPayment records linked to the Invoice. Tax code and VAT treatment flagged for manual adjustment in Epicor's tax engine configuration.

Kafinea Credit Notes map to Epicor ARCreditMemo records. The credit note chain (linked to the original invoice) is preserved via the InvoiceNum field in Epicor, and the reason code migrates as a custom field if the Kafinea reason is non-standard. Credit notes with open balances are imported before invoices with zero-balance credit notes imported last to avoid reconciliation conflicts.

Kafinea journal entries with multi-line debits and credits are sequenced by posting date during import to respect Epicor's fiscal period controls. We extract GLJrnGrp (header) and GLJrnGrpDtl (detail) records via the Kafinea REST API, map account codes to Epicor's COA, and validate each entry against the open fiscal period in Epicor. Entries with posting dates outside an open period are held in a staging queue for the customer's Epicor admin to open the period or post-date the entry.

Kafinea accounts with account type, currency, and optional cost center export via REST API and map to Epicor GLAccount records. We flag any non-standard or custom account codes not found in the default Epicor COA template, as these require pre-creation in Epicor's account master before journal import. Cost center references map to Epicor's Site or Project dimension depending on the customer's use of Epicor's multi-entity or project accounting modules.

Kafinea Sales Orders map to Epicor OrderHed (header) and OrderDtl (detail). OrderHed fields include CustomerNum, ShipToNum, OrderDate, and POReference. OrderDtl maps product lines with quantity, unit price, and the Kafinea Price Book tier reference to Epicor PriceLst records. Kafinea Price Books with tiered pricing tiers (quantity-based pricing at different price points) are recreated as Epicor PriceLst records with quantity breaks mapped to the PriceLstQty table before order import.

Kafinea CRM Contacts and Companies are separate objects with a link between them. We map Kafinea Companies to Epicor Customer records and Kafinea Contacts to Epicor Con用水 (contact person) records linked to the Customer via ConNum. Lifecycle stage from Kafinea CRM maps to a custom field on Con用水 if the customer requires this for segmentation. Con用水 email addresses are validated for format before import to prevent Epicor email validation errors.

Kafinea Service Contracts define recurring billing and SLA terms that map to Epicor Field Service FSContHead (contract header) and FSContDtl (contract lines). Contract start and end dates, billing frequency, and SLA tier migrate directly. We flag any SLA terms that reference Kafinea-specific service levels that must be re-established as Epicor FSL field service levels post-migration.

Kafinea Interventions (time or task records logged against service contracts) map to Epicor LaborDtl records for time tracking, linked to the corresponding FSContDtl contract line. Effective-dated intervention records are imported in date sequence to preserve labor history against the correct service contract and technician. Standalone Interventions without a contract link import as standalone LaborDtl records.

Kafinea time entries linked to users and projects map to Epicor LaborDtl records. Absences with accrual balances require sequential import by effective date to preserve accrual calculations in Epicor's HR module if the customer activates HR at the destination. Absence type codes from Kafinea map to Epicor AbsenceType codes; any non-standard types are flagged for HR admin configuration.

Kafinea custom fields across Customers, Invoices, Orders, and Service Contracts are mapped to Epicor UD fields (UD01-UD30 tables) or native custom fields where Epicor supports typed custom fields. We handle picklist values, date fields, and numeric fields with explicit type casting at load time. Epicor UD field creation requires configuration via the Kinetic UI or ICE tools before data import; we flag this as a prerequisite step in the migration sequence.

Kafinea EDM documents exported as file references or direct downloads are mapped to Epicor EDMDocMaster and EDMDocType records. We preserve folder structure from Kafinea as a metadata field on the Epicor document revision and attach documents to the corresponding Customer, Order, or Invoice record via LinkTable entries. Binary attachments are uploaded via Epicor's document management API and linked to the parent record.