Migrate from Dolibarr ERP to Epicor Prophet 21

Dolibarr's llx_societe stores customers, suppliers, and prospects in a single table differentiated by Tiers type codes (0=customer, 1=supplier, 2=lead). llx_socpeople stores contacts linked to llx_societe by fk_soc. We split each Dolibarr Third Party into the equivalent Epicor Customer or Supplier entity plus a related Contact record. Address fields (street, zip, town, country) map to Epicor's Address table with addr fields; we create a Company record in Epicor first, then link all Contact records before any Order or Invoice import. The Dolibarr Tiers code maps to Epicor's Customer_Tye value and the Customer/Ty type classification.

Dolibarr llx_product with type=0 (product) maps to Epicor Part with Part.TypeCode=Part; type=1 (service) maps to Epicor Part with Part.TypeCode=Service. Price fields from llx_product require precision normalization because Dolibarr allows up to 5 decimal places on unit price by default while Epicor applies a decimal-separator configuration per company. We record Dolibarr's Setup > Limits accuracy settings during discovery and apply matching field-level formatting in Epicor. Stock levels in llx_product_stock map to PartWhse quantities in Epicor with the warehouse reference resolved from llx_entrepot.

Dolibarr Proposals map to Epicor QuoteHed (header) and QuoteDtl (line) records. Dolibarr's integer status codes (0=draft, 1=validated, 2=signed, 3=refused, 4=billed) map to Epicor's QuoteHed.QuoteStage values. Proposal lines reference llx_product IDs that we resolve to Epicor PartNum during import, and we create a QuoteCnt record for the linked third-party contact. Historical Proposals with status signed or billed are migrated with their original dates; draft proposals are migrated as open quotes requiring review in Epicor before use.

Dolibarr Customer Orders map to Epicor OrderHed (header) and OrderDtl (line). OrderHed.BTCustomer indicates whether the order was entered by the customer portal, which is set to false for all migrated orders. We resolve Dolibarr's fk_soc (third-party reference) to the Epicor Customer.CustNum and map fk_user_author (order owner) to Epicor's SalesRep.SalesRepCode. The Dolibarr order date maps to OrderHed.OrderDate and the payment terms reference maps to OrderHed.TermsCode via a lookup table derived during scoping.

Dolibarr invoice migration is the most complex object because it requires preserving three related tables simultaneously. llx_facture (header) maps to Epicor InvcHead; llx_facturedet (lines) maps to InvcDtl; llx_paiement (payments) maps to Epicor CashHead with the payment method resolved via the payment type mapping (DTYPE_CHQ to Check, DTYPE_VIR to ElectronicTransfer); and llx_paiement_facture links payments to invoices which maps to InvcHead应用中 with matching InvcHead.InvoiceNum and CashHead.Reference. We process invoices in two phases: first all InvcHead and InvcDtl records, then all CashHead records with their links. Open invoices and closed invoices migrate with their original dates and status flags preserved.

Dolibarr llx_bank records hold bank transaction rows linked to llx_bank_account. We map llx_bank rows to Epicor CashHead with the transaction date, amount, and label preserved. The reconciliation flag from Dolibarr (reconciled column) sets CashHead.LegalNumber status. We link CashHead to the corresponding Epicor BankAcct by matching the bank account reference or IBAN from Dolibarr. Epicor's full bank reconciliation workflow is configured post-migration by the customer's Epicor administrator.

Dolibarr Projects map to Epicor Project with Project.Workspace_Job closed flag set based on the project's active status. Task rows in llx_projet_task map to Epicor ProjectTask with work date, estimated hours, and task owner preserved. Time budgets stored in llx_projet_task_time migrate to ProjectTaskBudget entries in Epicor. Dolibarr project milestones (project milestone dates from the project record) map to Epicor ProjectPhase entries with Phase start and end dates carried over.

This is the most technically involved mapping step. Dolibarr's extrafields system serializes custom field definitions and values as JSON inside the extraoptions column on the parent table (llx_societe, llx_product, llx_proposal, llx_commande, llx_facture, llx_projet, llx_user). We parse each object's extraoptions JSON at migration time, deserialize every key-value pair, and map each to a typed Epicor UD field (UD01, UD05, or a named UD column on the parent table). We flag any Dolibarr file-path references stored as text fields that cannot map cleanly to Epicor's UD field types. The destination UD fields are pre-created during the schema design phase before any data migration begins.

Dolibarr llx_user records migrate as Epicor User records and corresponding SalesRep records. We map Dolibarr's login email to Epicor.UserName and preserve the user type (internal vs external), status, and permission group memberships. We do not migrate Dolibarr password hashes because they are salted bcrypt with no exportable format; users reset passwords through Epicor's standard invitation flow after migration. Active/inactive status is preserved; users marked inactive in Dolibarr are provisioned as inactive in Epicor to prevent inadvertent access.

Dolibarr calendar events in llx_actioncomm are migrated as a written inventory for the customer's Epicor administrator to rebuild in Epicor's Kinetic calendar module or a connected third-party scheduling tool. Dolibarr's recurring event rules and fullcal integration metadata do not have a direct Epicor equivalent; we document the event type, date range, owner, linked third-party, and linked project in a CSV export. Epicor's Kinetic UI includes a native calendar component that can be configured for similar scheduling purposes by the administrator.

Dolibarr attachments are stored as files on the filesystem with references in llx_document pointing to physical file paths. We do not migrate binary file attachments as part of the standard migration scope because Dolibarr stores files in a flat filesystem structure with no consistent relational reference that maps to Epicor's document management model. We export a manifest of all attachment file paths linked to their parent record (third party, product, invoice, project) and deliver it to the customer for manual re-upload to Epicor's SharePoint or Linked attachments module post-migration.

Dolibarr warehouses (llx_entrepot) map to Epicor Warehouse records. Stock levels in llx_product_stock map to PartWhse records with on-hand quantities and warehouse location references. Stock movement history in llx_stock_mouvement is migrated as PartTran records in Epicor with transaction type labeled as DMB-Transfer (Debit Memo Transfer) as the closest equivalent, with the original movement date, quantity, and warehouse from/to fields preserved. This migration requires Epicor's Inventory Management module to be licensed.