Migrate from Falcon ERP to Dolibarr ERP

Falcon ERP hierarchical COA with account codes, names, and types exports to CSV. We map each Falcon ERP account to a Dolibarr Account (type Tier for balance sheet and income accounts) with the account code preserved as the dolibarr account_number field. GCC currency assignments on Falcon ERP accounts become Dolibarr currency tags on each account. We validate total debit and credit balance from the Falcon ERP trial balance against the sum of imported Dolibarr journal lines before finalizing.

Falcon ERP customer records (billing address, credit limit, AR terms) map to Dolibarr Third-party records of type Customer. Address, phone, email, and credit limit transfer to Dolibarr fields; Falcon ERP AR payment terms become Dolibarr payment term IDs created during the setup phase. We deduplicate by customer code as the dolibarr ref_customer field.

Falcon ERP vendor records with AP terms and WHT codes map to Dolibarr Third-party records of type Supplier. WHT (Withholding Tax) codes required for GCC compliance are stored as custom fields on the Dolibarr supplier record since standard Dolibarr does not include WHT natively. Falcon ERP vendor payment terms map to Dolibarr payment term IDs.

Falcon ERP items (product/service classification, cost, price, inventory tracking flags) map to Dolibarr Product records with type set to Product (for inventory-tracked) or Service. Stock levels by Falcon ERP location transfer to Dolibarr warehouse stock entries via the stock module. Item codes from Falcon ERP become Dolibarr ref_supplier or ref_customer fields for cross-reference.

Outstanding customer invoices, credit notes, and payment schedules from Falcon ERP export per customer. We map open AR to Dolibarr Facture (Customer Invoice) records with status set to Draft or Unbilled depending on payment state. Aging buckets and due dates are preserved in invoice line notes and payment term fields. Each invoice is tagged with the Falcon ERP company code for multi-entity traceability.

Outstanding vendor invoices, credit notes, and payment schedules from Falcon ERP export per vendor. We map open AP to Dolibarr Facture (Supplier Invoice) records with status set to Draft or Unbilled. Due dates and aging information are preserved in invoice notes and payment term associations. WHT deductions from Falcon ERP are recorded as separate line items on the corresponding Dolibarr supplier invoice.

Falcon ERP 2-3 years of invoice, payment, receipt, and credit note history export as line-item spreadsheets. We split each Falcon ERP transaction into multiple Dolibarr accounting entries: invoice header becomes a Facture, each invoice line generates a journal entry in the selected Dolibarr journal (Customer Invoice journal or Supplier Invoice journal), and payments generate corresponding bank journal entries. ZATCA e-invoice UUIDs are preserved in a Dolibarr extrafield text field on each invoice record for audit continuity.

Falcon ERP manual and recurring journal entries export with account references and amounts. We map posted journals to Dolibarr Écritures Comptables (accounting lines) in a dedicated Miscellaneous Operations journal. Debit/credit amounts, account codes, and transaction dates transfer directly. Falcon ERP journal descriptions become Dolibarr piece_ref and label fields.

Falcon ERP fixed asset records (acquisition cost, depreciation method, accumulated depreciation) map to Dolibarr Asset records. Acquisition date, cost, and useful life transfer directly. Depreciation method from Falcon ERP (straight-line, declining balance) is mapped to the corresponding Dolibarr amortization type. We recalculate the depreciation schedule in Dolibarr from the Falcon ERP accumulated depreciation balance at the migration date, creating the first amortization entry on day one of the new system.

Falcon ERP employee records (personal details, department, job title, employment status) map to Dolibarr Users with the Employee flag enabled. Effective-dated changes (hires, promotions, terminations) transfer as historical records in the Dolibarr HR module. Falcon ERP department codes map to Dolibarr expense categories for reporting. Active and inactive status transfers directly.

Falcon ERP payroll registers (salary, deductions, allowances, tax deductions per pay period) map to Dolibarr Payroll module entries. Pay components (basic salary, housing allowance, transport allowance, commissions) transfer as line items; WHT deductions map to the custom WHT fields on the employee record. Pay period dates and employer/employee contribution amounts are preserved. Note: GCC-specific WHT configuration in Dolibarr requires manual setup beyond the migration scope; we document the required WHT rate table during handoff.

Falcon ERP VAT transactions and ZATCA Phase 2 e-invoice records contain GCC-specific tax codes and e-invoice UUIDs. We map VAT rates (5% standard, 0% exempt, reverse charge) to corresponding Dolibarr VAT rates pre-created during the setup phase using a VAT mapping table built from the Falcon ERP tax code list. ZATCA UUIDs and QR code references are stored in a Dolibarr extrafield text field on each invoice record. This is a configuration-intensive step because Dolibarr does not ship ZATCA-native e-invoicing; the extrafield approach maintains audit continuity without requiring a third-party ZATCA module.

Falcon ERP Bill of Materials and work orders define product recipes and production steps. Dolibarr includes a BOM module, but it requires manual configuration for each product recipe. We export Falcon ERP BOM structures (component items, quantities, unit of measure, routing steps) to a structured CSV and deliver it as a BOM rebuild worksheet. The customer's Dolibarr administrator uses the worksheet to create each BOM in Dolibarr's BOM module. This is a documented rebuild scope, not a direct data migration, because Dolibarr's BOM schema differs structurally from Falcon ERP's work order model.

Open Falcon ERP work orders (in-progress production) are exported with status, component allocations, and completion percentage. We map open work orders to Dolibarr Production Orders. Since Dolibarr's production module requires BOMs to be configured first (see BOM mapping), open work orders are loaded after BOMs are rebuilt. Status and completion percentage transfer as notes on the Dolibarr production order for manual resolution by the production team.