Migrate from AFAS to Epicor Prophet 21

AFAS stores the Dutch chart of accounts with statutory account codes, cost-center mappings, and BTW tax control accounts in its financial ledger tables. We extract the full account structure and map each AFAS account code to an Epicor GLAccount with the matching Segment values. Dutch statutory account codes are preserved as a custom GLAccount field for audit compliance. Account type (Asset, Liability, Equity, Revenue, Expense) maps to Epicor GLAccount Type.

AFAS CRM module customers with contact details, addresses, payment terms, and Dutch VAT registration numbers map to Epicor Customer. The BTW registration number (KvK/BTW) migrates to the Tax ID field. We preserve the AFAS customer classification codes and map them to Epicor Customer Group for reporting segmentation. Open AR balances migrate as Epicor AR Invoice records with aging preserved against the correct Customer and Terms of Payment.

AFAS procurement module suppliers map to Epicor Vendor records. Dutch BTW registration numbers on suppliers migrate to the Vendor Tax ID. Payment terms, bank details, and purchase address records transfer to Epicor Vendor with TermsCode and RemitTo mapping. Open AP balances from AFAS become Epicor AP Invoice records linked to the correct Vendor.

AFAS invoices with line items, BTW tax codes, and payment references map to Epicor AR Invoice (CustomerInvoice) and AP Invoice (VendorInvoice). Each line carries the Dutch BTW rate from AFAS, which we map to the corresponding Epicor Tax connectivity: Epicor Tax Service or a manual tax code table if the customer uses local Dutch VAT configuration. Invoice status (Open, Paid, Void) is preserved for reconciliation against the general ledger.

AFAS credit notes map to Epicor AR CreditMemo and AP CreditMemo records. The linked original invoice reference is preserved as a custom field for traceability. BTW reversal codes (verlegd or intracommunautair) transfer to Epicor's tax treatment fields to maintain correct Dutch VAT reporting.

AFAS inventory Items with stock levels, warehouse locations, and pricing tiers map to Epicor Part records. We map AFAS Item classes to Epicor Part Unit of Measure classes, stock levels to PartBin quantities per warehouse, and reorder thresholds to Epicor PartRpl records. Active and inactive status from AFAS carries forward as Part InActive flag. Parts with BOM structures map to Epicor PartBill records with multi-level explosion.

AFAS BOM structures with parent-part and component relationships map to Epicor PartBill (one record per BOM per revision) and PartMtl (one record per component). We preserve Phantom BOM flags, scrap percentages, and material burden rates. Operation routing from AFAS (where present) maps to Epicor PartOpDtl and JobOper records for manufacturing operations. BOM revision dates from AFAS carry into Epicor's revision tracking.

AFAS project management records with project codes, descriptions, start and end dates, and budget allocations map to Epicor Project. We map AFAS project type (internal, customer-facing, time-and-materials, fixed-price) to Epicor ProjectType and ProjectPhase codes. AFAS project custom fields (which are common in established AFAS installations) map to Epicor Project UDF fields pre-created during schema design.

AFAS time entries linked to Projects map to Epicor LaborDtl records. Employee, project, phase, date, hours, and labor type transfer to Epicor with the JobNum reference resolved at migration time. AFAS overtime flags and cost-center assignments map to LaborDtl overtime and expense code fields. Time entries without a project reference migrate as direct labor against the default work center.

AFAS employee records with personal details, contract type, department, and employment status map to Epicor Employee. We map AFAS personnel number to Epicor EmployeeNum, employment type (vast, tijdelijk, oproep) to Employee records, and department codes to Epicor ShopFloor Labor records. Active employment status determines whether the employee record is created as active or inactive in Epicor.

AFAS payroll journal entries for the last 3-7 years (agreed scope with the customer) map either to Epicor Payroll records if the Epicor Payroll module is licensed, or to GL JournalEntry records if payroll is managed outside Epicor. Dutch payroll tax codes (loonheffing, sociale verzekeringen) are preserved as memo fields to satisfy Dutch tax authority documentation requirements. We scope payroll history with the customer to balance compliance obligations against migration data volume.

AFAS bank account configurations with account numbers, current balances, and reconciliation data map to Epicor cash management records. We preserve bank account numbers and current period balances from AFAS. Open bank reconciliation entries from AFAS map to Epicor CashFlow or BankRec records to maintain audit trail continuity into the first Epicor close period.

AFAS documents linked to transactional records (invoices, projects, employees) are extracted from AFAS's internal document storage and loaded into Epicor's document management system or as Epicor Attachment records linked to the corresponding Part, Customer, Vendor, Project, or Employee record. Some AFAS document formats require conversion (PDF preferred for Epicor attachment compatibility). Document metadata (date, author, type) transfers as Epicor DocField values.