Migrate from Farvision ERP to Odoo ERP

Farvision's Project records span six lifecycle phases (Land Acquisition, Legal, Pre-Sales, Post-Sales, Budgeting, Execution) stored as phase flags or sub-records on a single project object. We migrate the project master record with phase metadata preserved as custom fields, and link Odoo Project tasks or sub-projects for each active phase. If Odoo Enterprise Real Estate module is installed, projects map to Real Estate Property records. Phase sequencing is preserved for project timeline reporting in the destination.

Farvision Customer records map to Odoo Partner records. We resolve the schema distinction: if Farvision stores organizational accounts (companies) separately from individual contacts, we create Odoo Company partners with Contact sub-records linked via the parent_id relationship. Custom fields on Customer (buyer classification, source channel, property interest type) migrate as Odoo custom fields on res.partner.

Farvision Property records represent sellable units tied to a specific project. We map these to Odoo Product records with storable type if using the standard inventory model, or to the Odoo Real Estate module's property/unit object if that module is installed in the destination. Project-to-property associations migrate as product_categories or tags on the Odoo Product, preserving the original project linkage for inventory and sales reporting.

Farvision Sales Orders and Booking Records (generated when a buyer reserves a property unit) map to Odoo Sale Order. The booking status field (e.g., Registered, Confirmed, Cancelled) maps to Odoo's sale_order_state workflow, and payment schedule milestones migrate as sale.order.line records with their respective amounts and due dates. We preserve the property-unit linkage via the Odoo Product reference on each order line.

Farvision Client Billing records and installment tracking migrate to Odoo Account Moves in the account module. Payment milestones, installment amounts, and remaining balances map to Odoo invoice lines with payment term references. We preserve the project-wise financial segregation by mapping Farvision's project-reference field to an Odoo analytic account on each invoice line, enabling project-wise P&L reporting post-migration.

Farvision inventory management covering materials, procurement, and stock tracking maps to Odoo Product (stockable type) with current_quant and warehouse location preserved via Odoo stock.quant and stock.location records. Unit-of-measure conventions from Farvision require explicit mapping to Odoo's uom.uom table. If Farvision stores stock transaction history, we migrate opening inventory balances rather than full transaction history to avoid the overhead of reconstructing Odoo stock.move records.

Farvision HR and Payroll employee records map to Odoo hr.employee. Compensation history and effective-dated payroll records migrate as a single snapshot at migration time; we flag effective-dated payroll records for manual verification by the customer's HR team post-migration because Odoo Payroll requires separate configuration and is not included in standard Odoo ERP migration scope unless specifically contracted.

Farvision Activity records and Activity Groups (documented via YouTube training import/export content) map to Odoo Mail Activity records linked to the corresponding res.partner, project, or sale.order. Activity Groups migrate as tags or categories on the Odoo activity record. Date sequencing and owner assignments are preserved from the Farvision activity records for project activity timeline reconstruction.

Farvision's configurable Payment Types Master entity maps to Odoo account.journal records with the journal_type set to bank or cash depending on the payment type classification. Each configured payment type from Farvision creates a corresponding journal in Odoo, with the payment_flow mapping preserved (e.g., incoming vs outgoing, online vs offline) in the journal's active configuration settings.

Farvision Places Management stores location data with country and state hierarchies. We preserve the full location tree structure and map it to Odoo's res.country, res.country.state, and city tables. The location hierarchy (project site, tower, floor, unit) migrates as structured address fields on the related Partner or Project record, with the highest-level project location stored as the primary address for reference.

Farvision Engineering module covers Quantity Surveying and contractor billing records with industry-specific data structures. These map partially to Odoo Project Task records for QS tracking and to Odoo mrp.bom if the engineering records contain material take-off or bill of materials data. Complex engineering-specific fields (rate analysis, work measurement, cost codes) require field-level mapping to custom fields on the Odoo task or product, as Odoo does not have a native QS object.

Farvision custom field definitions and their values migrate to Odoo custom fields created via Settings > Technical > Custom Fields or via XML data migration. MongoDB-typed data (nested objects, arrays) is flattened during the transform step by unwrapping nested key-value pairs into Odoo-compatible scalar fields. Field type mapping from Farvision types to Odoo field types (char, float, selection, many2one, etc.) is defined during discovery and validated in the sandbox migration before production.