Migrate from Farvision ERP to Dolibarr ERP

Farvision Projects cover the full lifecycle: Land Acquisition, Legal and Liaison, Pre-Sales, Post-Sales, Budgeting, and Execution phases. These map to Dolibarr Project records with phase tracked as a project status or custom extra field. Milestones migrate as Dolibarr ProjectTask records with planned dates preserved. We extract project identifiers and phase associations during the discovery extract so the hierarchical structure is preserved in Dolibarr's project hierarchy.

Farvision customer records map to Dolibarr ThirdParty entities with the Customer category flag set. Contact details (name, email, phone, address) migrate directly. Farvision's customer custom fields map to Dolibarr extra fields (champs extra) stored on the ThirdParty record. We use the third-party email as the dedupe key during import and set the Role field to Customer for all converted records.

Farvision property records tied to specific projects represent sellable inventory units (tower floors, apartments, plots). These map to Dolibarr Product records with type = 1 (stockable) and with project linkage preserved as an extra field project_id__c referencing the Dolibarr Project. Unit-specific attributes (floor number, area, facing, status) migrate as product extra fields.

Farvision generates sales orders and contracting records tied to specific properties and buyers. These map to Dolibarr Proposal (for quotation stage) and Order (for confirmed stage) records. Booking status values from Farvision map to Dolibarr ProposalStatus or OrderStatus integer codes. Contract records map to Dolibarr Contract (if the Contracts module is activated). The customer ThirdParty and linked Product references resolve at migration time via lookup.

Farvision Client Billing records including payment milestones and installment tracking require schema mapping to Dolibarr Facture (Customer Invoice). Payment milestone status values map to Dolibarr invoice status codes (DRAFT, VALIDATED, PAID, CANCELLED). We preserve the billing history but flag that Farvision's project-wise accounting entries require a separate accounting reconciliation because Dolibarr's accounting module may not be activated, depending on the customer's Dolibarr module selection.

Farvision Stores and Procurement covers materials, procurement, and stock tracking. These map to Dolibarr Product records (type 0 = service or 1 = stockable) and associated Stock Movement records. Unit-of-measure conventions in Farvision require explicit mapping to Dolibarr unit-of-measure codes (UoM). Multi-warehouse support in Dolibarr requires activation of the Stock module with warehouse records created before stock import.

Farvision HR and Payroll covers the full Employee Life Cycle. Employee records map to Dolibarrhrm_employee records (if the HRM module is activated). Compensation history, designation, department, and joining date migrate as typed fields. Effective-dated payroll records are flagged for manual verification post-migration because payroll periods and tax configurations differ by jurisdiction and Farvision's payroll engine has no documented export path.

Farvision Activity records and Activity Groups map to Dolibarr Agenda events and Tasks. Group associations migrate as event categories or tags in Dolibarr. Farvision's documented import/export paths for activities guide our extraction approach. Activity dates and descriptions migrate directly; owner assignment resolves via email lookup against Dolibarr User records.

Farvision Payment Types Master is a configurable entity defining accepted payment methods (cheque, bank transfer, cash, EMI). These map to Dolibarr Payment Terms (cond_reglement) and Bank Account records with the payment method type preserved in the label or as an extra field. Payment schedule templates from Farvision sales orders map to Dolibarr payment term lines.

Farvision Places Management stores location data with country and state hierarchies used across customer addresses, property locations, and site addresses. These map to Dolibarr's c_country, c_departments (state/province), and c_ziptown tables. The location tree structure in Farvision flattens to a relational address model in Dolibarr, with hierarchy levels preserved as separate address component fields.

Farvision's Engineering module covers Quantity Surveying and construction billing with industry-specific data structures. These records map to Dolibarr ProjectTask entries with budget amount tracked as a custom monetary extra field. Because Dolibarr does not have a native quantity surveying module, we map the QS cost categories to Dolibarr Project extra fields and note which records require post-migration manual entry to complete the construction-cost breakdown.

Farvision custom fields generated across objects map to Dolibarr extra fields (ExtraFields) stored as typed columns on the target entity. We migrate custom field definitions (label, type, options) and values per record. Unsupported field types (Farvision-specific picklist values, nested arrays) are flagged and migrated as text fields with a remediation note for the customer's admin to refine post-migration.