Migrate from daftra to Epicor Prophet 21

Daftra's Chart of Accounts is exported as a flat table with account type (asset, liability, revenue, expense) but without an explicit parent_id column. We reconstruct the hierarchical posting tree during discovery by parsing account codes (Daftra uses dot-notation like 1000.100.01 to indicate parent-child relationships). Accounts load into Epicor GL Account in account-code order to satisfy posting hierarchy requirements. Sub-account parent references are resolved at migration time against the reconstructed tree. Cost Centers from Daftra map to Epicor GL Account Category Codes or a dedicated Cost Center custom field depending on the destination Epicor company's chart configuration.

Daftra Client records map to Epicor Customer. We extract contact details, follow-up history, memberships, points, and insurance references as supplementary fields on the Customer record or in related tables. Client Follow-Up activity logs migrate as CRM Activity records (Task or ToDo) linked to the Customer. Membership points, insurance records, and sales commission settings (Daftra Advanced and Comprehensive plans) have no native Epicor equivalent — we preserve these as custom fields on Customer or as Notes attached to the Customer record for the customer's Epicor admin to allocate to the appropriate module.

Daftra Products and Services export includes pricing tiers, SKU, stock levels, and supplier links. Products map to Epicor Part (with PartType = Stock or Non-Stock), Services map to Epicor Service. Custom fields on Products migrate to UD fields on Part. We extract the supplier links as VendorPart records in Epicor's Supplier cross-reference table. SKU maps to Part Number; stock levels map to PartWhse (Part Warehouse) records.

Daftra Invoices carry line items, taxes, installment schedules, and sales commission assignments. We map to Epicor AR Invoice (or the equivalent in Epicor's financial module). The invoice balance and installment schedule are preserved as separate fields or as linked Payment records in Epicor's Payment Entry. Custom fields on Invoices (Daftra field-builder) are enumerated per object during discovery and mapped to UD fields on the Epicor Invoice header or line. Closed invoices with zero balance migrate as historical records; open invoices migrate with their outstanding balance.

Daftra Expenses map to Epicor AP Invoice (for vendor-linked expenses) or GL Journal Entry (for non-vendor expenses). We extract expense category, date, amount, and attachment references. Recurring expense patterns are preserved as a flag on the migrated record. Expenses link to the Chart of Accounts (GL Account mapping already resolved in order 1) and to Cost Centers where applicable.

Daftra Cost Centers are used for expense attribution across departments or projects. The linking between Cost Centers and individual transactions requires field-level extraction since Daftra's export does not include the full transaction-CostCenter join in a single table. We build this join during discovery and map Cost Centers to either Epicor GL Account Category Codes (if the Epicor company uses category-level reporting) or to a UD field on the GL Journal Entry or AP/AR Invoice depending on the destination company's reporting structure.

Daftra Employee records include Organizational Structure placement, Contracts, Attendance, and Payroll. Compensation history is stored as a time-series within the employee record — we extract each payroll entry as a separate labor record or HR record in Epicor's HRM module (Demand Worker or Employee depending on Epicor edition). Contracts migrate as LaborRate records or HR records with start/end dates and compensation terms. Custom fields on Employees are enumerated and mapped to UD fields on the Epicor Employee record.

Daftra Fixed Assets include custom fields added per-asset and separate depreciation schedule records. We map to Epicor Asset Management (Asset register). Asset depreciation schedules are extracted separately from the asset master record and loaded as Depreciation Detail records in Epicor. Custom fields on Assets are enumerated during discovery and mapped to UD fields on the Asset record. Asset category maps to Epicor Asset Class.

Daftra Work Orders link to Clients, Employees, and Products and include full workflow stage history and attached files. These map to Epicor Job (for manufacturing work orders) or FSM Service Order (for field service work orders) depending on the customer's operational model in Epicor. The workflow stage history migrates as Job Operation records or Service Order status change records. Files and notes attach to the Job or Service Order via Epicor's Document Management.

Daftra Reservation Files with PNR-style file management, status tracking, and appointment scheduling map to Epicor Appointments (FSM module) or Job Operations (manufacturing). The activity log migrates as a series of Appointment records or Operation notes. Booking status values map to Epicor Appointment or Job status fields. Files attach to the Appointment or Job record.

Daftra's Cheque Cycle tracks cheques through issue, deposit, and return stages tied to both the Chart of Accounts and specific invoice/payment records. Epicor ERP does not have a native cheque cycle object. We preserve the full cycle history (issue date, bank account, payee/receiver, amount, deposit date, return date, return reason) as a UD field group on the AP Payment record or as a linked Notes record for the customer's Epicor admin to reference. The GL impact of each cheque stage (post-dated cheque asset, bank clearing entries) is reconstructed against the GL Account mapping already loaded.

Daftra custom fields on Invoices, Assets, and Workflows are object-scoped and must be enumerated per object via the Daftra UI during discovery. We read field type, required flag, and options list, then pre-create equivalent UD (User Defined) fields on the corresponding Epicor business object before any data import. Custom field values are then written to these UD fields during the import phase. We flag any Daftra field types (e.g., multi-select picklists, date-only fields) that require explicit type mapping to Epicor's UD field schema.