Migrate from AFAS to Odoo ERP

AFAS Profit stores the Dutch chart of accounts in its financial ledger tables including cost-center mappings and statutory account codes (grootboekrekeningen). We extract the full account structure and map to Odoo Accounting Accounts with the correct account_type (asset, liability, equity, revenue, expense) and code preserved. Dutch BTW account mappings migrate to Odoo tax accounts so that BTW reconciliation reports function correctly post-migration.

AFAS CRM and procurement modules hold Customer and Supplier records with contact details, addresses, payment terms, and Dutch BTW/VAT registration numbers (BTW-identificatienummer). We split AFAS customers and suppliers into Odoo Contact records (for persons) and Company records (for organizations), preserving VAT numbers, KVK numbers, and payment terms. Odoo's commercial entity model means the Company is the billing party and Contacts under it are the individuals.

AFAS generates sales invoices, purchase invoices, and credit notes within its financial modules. We extract open and historical invoices with line items, BTW tax codes, and payment references. Each invoice migrates as an Odoo account.move record with the correct journal (Sales Journal for customer invoices, Purchase Journal for vendor bills), preserving invoice dates, due dates, and the original AFAS invoice number in the reference field. BTW codes are mapped to the nearest Odoo tax template; accounting team sign-off is required for any BTW remapping.

AFAS inventory stores Items with stock levels, warehouse locations, pricing tiers, and BOM structures. We extract full item records including active/inactive status, reorder thresholds, and unit of measure. Items migrate to Odoo Product records with the appropriate product_type (storable, consumable, service). BOM structures map to Odoo Bills of Materials if the manufacturing module is activated at the destination. Warehouse locations map to Odoo Inventory Locations.

AFAS project management module holds Project records and associated time entries. We extract projects with their cost-center assignments and time entries linked to the correct employee. Projects migrate to Odoo Project with timesheets enabled. AFAS custom fields on projects and non-standard rate structures require field-level mapping during extraction and are documented in the field inventory deliverable.

AFAS maintains employee records with contract details, department assignments, and employment status. We extract employees and their HR registry entries and map them to Odoo HR Employee records. Dutch-specific fields (BSN, contract type, CAO affiliation, pension provider) migrate to Odoo HR custom fields or contract fields as available. Employees must be migrated before payroll records because Odoo HR uses employee as the parent record for contracts.

AFAS stores payroll runs, salary history, and payroll journal entries for each pay period. We extract effective-dated compensation records and journal entries. Dutch-specific payroll components (bruto/netto calculation, loonheffing, werknemersverzekeringen, pensioenpremie) migrate as Odoo Payroll line entries against the employee's contract. Historical payroll migrates as closed periods; current-year open payroll is migrated as open entries for the customer's accounting team to close in Odoo.

We extract bank account configurations and current balances from AFAS cash management. Each AFAS bank account becomes an Odoo Bank journal with the account number preserved and an opening balance entry posted on the migration date. Reconciliation data from AFAS does not migrate as reconciled transactions in Odoo; we deliver an opening-balance report so the customer's accountant can reconcile manually in Odoo post-go-live.

AFAS links documents to records across modules. We extract attachments associated with transactional records (invoices, projects, employees) as binary files. Odoo stores attachments on the ir.attachment model linked to the target record via res_model and res_id. The AFAS internal document storage format may require format conversion for some file types; we flag any non-standard formats during discovery.

AFAS allows extensive custom fields on standard objects and user-defined tables unique to each installation. Every AFAS deployment we have migrated has between 10 and 80 custom fields and 2-15 user-defined tables that have no standard Odoo equivalent. We inventory every custom field during discovery, classify each as a 1:1 map, a transform required, or a custom field to create in Odoo Studio, and deliver a written custom-field migration plan. User-defined tables with complex relationships may require a custom Odoo module to reproduce the data model.

AFAS workflows define approval chains, conditional routing, and automated actions across HR, finance, and operations. We extract workflow configurations as process maps and deliver a written inventory identifying each AFAS workflow, its trigger, conditions, and actions with a recommended Odoo Automated Action or Server Action equivalent. Workflows are not migrated as executable code. The customer's Odoo partner or admin rebuilds them in Odoo Studio post-migration.