Migrate from Falcon ERP to Odoo ERP

Falcon ERP stores a hierarchical Chart of Accounts with account codes, names, and types (Asset, Liability, Equity, Revenue, Expense). We export the COA to CSV, preserve the full hierarchy via parent_id references, and map Falcon account types to Odoo's account type options (receivable, payable, asset, liability, equity, revenue, expense). For multi-entity Falcon deployments, each company code's COA is exported separately and tagged with its Odoo company_id during import so that account scoping remains entity-correct in Odoo's multi-company configuration.

Falcon ERP customer records include billing address, AR terms, credit limit, and WHT codes required for GCC compliance. We export all customer fields to CSV, map to Odoo res.partner with the customer flag set, and store any Falcon-specific credit or terms data in custom fields on the partner record. Deduplication uses company name and email as the match key. Customer addresses migrate as Odoo contact records with address_type set to invoice and delivery.

Falcon ERP vendor records mirror customer records with AP terms and WHT (Withholding Tax) codes required for UAE and Saudi GCC compliance. We export vendors and map to Odoo res.partner with the supplier flag set, preserving WHT tax codes in a custom partner field for Odoo's Withholding Tax configuration. Vendor addresses migrate as Odoo contact records. Deduplication uses vendor name and tax ID as the match key.

Falcon ERP items include product/service classification, standard cost, sale price, and inventory tracking flags by warehouse. We export items with stock levels per location and map to Odoo product.template (for product type and attributes) and product.product (for variants). Product categories from Falcon map to Odoo product.category for grouping. Stock quantities per warehouse migrate as Odoo quant records linked to the relevant stock.warehouse. Items with no inventory tracking flag migrate as consumable or service product types.

Outstanding invoices, credit notes, and payment schedules exported per customer from Falcon ERP map to Odoo account.move records of type out_invoice and out_refund. We preserve the original Falcon invoice number, invoice date, due date, and open balance. Odoo's reconciled field is left unchecked for open items so that the AR aging report reflects the true outstanding balance. Line items map to account.move.line entries with account references resolved from the migrated COA.

Outstanding vendor bills and credit notes exported per vendor from Falcon ERP map to Odoo account.move records of type in_invoice and in_refund. We preserve original vendor invoice number, invoice date, due date, and open balance. The reconciled flag is left unchecked for open items so that the AP aging report reflects true outstanding payables. Vendor references are resolved from the vendor Contact migration.

Past invoices, payment receipts, and credit notes from 2-3 years of Falcon ERP history are exported as line-item detail reports and mapped to Odoo account.move records with the date and journal preserved from the source. We batch historical transactions by fiscal year to align with Odoo's fiscal year lock dates. Payment records (bank receipts and cash payments) migrate as account.move records of type entry with the counterpart account resolved from the migrated COA. Falcon's payment method flags map to Odoo journal configuration.

Manual and recurring journal entries stored in Falcon ERP are exported with account references and debit/credit amounts. We map each journal entry to an Odoo account.move of type entry, preserving the original entry date, reference number, and memo. Line items are matched to Odoo account IDs via the account code mapping. Recurring journal entries are flagged in a custom field on the Odoo move so that the customer can rebuild the recurrence schedule in Odoo.

Falcon ERP fixed asset records include acquisition cost, acquisition date, depreciation method (straight-line or reducing balance), useful life in months, and accumulated depreciation to date. We export the asset register and map each asset to Odoo's account.asset.model, recalculating the depreciation schedule from the Odoo acquisition date forward. The accumulated depreciation balance at migration time is recorded as an initial depreciation entry in Odoo so that the net book value is preserved and the asset appears correctly in the balance sheet on day one.

Falcon ERP employee records include personal details, department, job title, employment status, and hire date. We export all employee data and map to Odoo hr.employee, preserving department as hr.department (created from Falcon's department list if not present), job title as the employee's job_id, and effective-dated status changes via Odoo's contract model (hr.contract) where applicable. Employee private contact details migrate as related res.partner records.

Payroll history from Falcon ERP includes salary components, allowances, deductions, and tax withholdings per pay period. We export payroll registers by employee and pay period and map to Odoo hr.payslip with wage, allowances, and deductions preserved as payslip line records. WHT codes from Falcon ERP are mapped to Odoo's tax configuration where applicable. Note that Odoo Payroll (Enterprise only) requires manual configuration of salary rules and payslip structures matching the customer's GCC payroll requirements before the migration data can be validated.

Falcon ERP's internal VAT rate codes (5% standard UAE/SA, 0% exempt, reverse charge) and ZATCA Phase 2 e-invoice UUIDs are preserved during migration. We create corresponding account.tax records in Odoo for each GCC VAT rate, mapping Falcon's internal tax codes to Odoo's tax scope (sale, purchase, none) and tax repartition lines. ZATCA UUIDs from Falcon invoice records are stored in a custom field (zakat_uuid__c) on the Odoo account.move record to maintain audit continuity for Saudi ZATCA compliance. Odoo's tax configuration requires manual setup post-migration to align with the customer's specific VAT filing jurisdiction.