Migrate from AFAS to Dolibarr ERP

AFAS GL accounts map to Dolibarr accounting accounts via the Accounting module, which must be activated before import. Dutch statutory account codes (VK accounts) migrate as account numbers with descriptions. Cost center mappings from AFAS require a separate cost-center classification in Dolibarr if the customer uses multi-dimensional reporting. We validate account code formats against Dolibarr's account numbering constraints and flag any accounts that exceed character limits.

AFAS debtor records map to Dolibarr Third Party records with type=Customer. Dutch VAT registration numbers (BTW-nummer) migrate as the tva_intra field, and customer payment terms map to the cond_reglement field. Addresses (billing and shipping) migrate as Dolibarr address records linked to the Third Party. AFAS debtor codes become Dolibarr customer codes for dedupe matching.

AFAS creditor records map to Dolibarr Third Party records with type=Supplier. Dutch supplier VAT registration numbers and payment terms migrate in the same manner as customer records. IBAN and bank account references from AFAS map to Dolibarr's Rib field. Supplier-specific AFAS fields (like preferred delivery warehouse) map to Dolibarr extrafields if configured during schema design.

AFAS sales invoices migrate to Dolibarr Customer invoices with line items, BTW tax codes, and payment references preserved. Each invoice line carries the AFAS BTW rate mapped to the applicable Dutch VAT code in Dolibarr (hoog, laag, nul, of exempt). Invoice status (open, paid, overdue) migrates as Dolibarr payment status. AFAS payment references and invoice numbers become Dolibarr invoice references for reconciliation.

AFAS purchase invoices map to Dolibarr Supplier invoices with the same line-level BTW code preservation. AFAS purchase invoice approval workflow status does not migrate; we document open purchase invoice approvals as a reconciliation list for the customer's accounts payable team to work through manually post-migration. Supplier remittance addresses map to Dolibarr address records on the supplier Third Party.

AFAS credit notes (creditfacturen) map to Dolibarr credit notes linked to the originating invoice if that invoice has been migrated. We preserve the link by matching AFAS invoice reference to Dolibarr invoice number during migration. If the original invoice is not migrated (historical archive), we import the credit note as a standalone document with the customer reference preserved.

AFAS inventory items map to Dolibarr Products with stock levels, warehouse assignments, and pricing tiers preserved. Item types (stockable, service, assembly) map to the appropriate Dolibarr type field. AFAS BOM (bill of materials) structures require the Dolibarr MRP module; if not activated, we import components as separate products and document the BOM as a reference list for manual assembly tracking. Reorder thresholds and supplier references migrate as product extrafields.

AFAS stock levels per warehouse migrate to Dolibarr stock locations. The Dolibarr Warehouse module must be activated before stock import. AFAS stock valuation (fifo, average cost) does not automatically set Dolibarr's costing method; the customer selects the costing approach during schema design. We extract current stock levels at a point-in-time snapshot and import them as an opening stock entry rather than a transaction history.

AFAS project records map to Dolibarr Project objects with project codes, names, status, and budgets preserved. AFAS custom fields on projects (common in established AFAS installations) migrate as Dolibarr extrafields if the extrafields are configured before migration. Project status mapping: AFAS Actief maps to Dolibarr Open status. Time entries linked to projects migrate as Dolibarr Project tasks with time recorded against the task.

AFAS employee records map to Dolibarr User records when the HR module is activated. Employment details (department, job title, employment type) migrate as User profile fields. AFAS effective-dated employment history (start date, contract changes) maps to Dolibarr User properties. If Dolibarr HR is not activated, we import employees as Third Party records with type=Contact and flag them for the customer to reclassify once HR is enabled.

AFAS payroll journal entries map to Dolibarr accounting entries via the Accounting module. Individual earning and deduction line items (brutoloon, netto, loonheffing, pensioen, etc.) become journal entry lines against the appropriate salary expense accounts. AFAS payroll runs per period become Dolibarr accounting document batches. We scope payroll history to the last 3-5 years based on customer compliance requirements to balance data volume against migration complexity.

AFAS custom fields on standard objects map to Dolibarr extrafields, which require activation per object after the base module is enabled. AFAS user-defined tables (common in established AFAS installations with years of customization) do not have a direct Dolibarr equivalent; we either import the data as a custom Dolibarr table with a dedicated module (requires a developer or third-party module) or normalize it into existing Dolibarr structures. We inventory every AFAS custom field and user-defined table during discovery and propose a target structure before migration begins.

AFAS documents linked to records migrate as Dolibarr documents attached via the ContentDocument model. PDF attachments to invoices, employee records, and projects transfer as binary files with the original filename and MIME type preserved. Dolibarr's document storage path is configurable; we set the target directory during installation. Documents stored in AFAS external storage systems (if configured) may require a separate retrieval step during discovery.

AFAS cash management bank account records map to Dolibarr bank account configurations. Account numbers, bank names, and current balances migrate. AFAS bank reconciliation data (matched transactions) does not have a direct Dolibarr equivalent; we import the reconciled balance as an opening position and leave reconciliation work to the customer's accounting team post-migration.