Migrate from Field2Base to Odoo CRM

Field2Base users (admin portal users and mobile workers) map directly to Odoo res.partner records. Email addresses serve as the unique identifier for matching. Mobile worker role flags (is_mobile_worker__c) are stored as a boolean custom field on res.partner. Field2Base does not have a separate contact/company split, so every user lands as a partner record.

Field2Base form templates have no direct Odoo equivalent. We map each distinct form template to an Odoo crm.stage (pipeline stage) and store the original template name as Form_Template_Name__c on crm.lead. If there are more than 15 templates, we recommend grouping by category and creating one stage per category rather than one per template to avoid Odoo pipeline clutter.

Each Field2Base submitted form becomes one Odoo crm.lead record. The submission's JSON payload is parsed, and every region (form field) becomes a mapped field on crm.lead. Submissions are deduplicated by Field2Base submission ID stored as Source_Submission_ID__c on crm.lead. Submissions submitted by the same user that have identical region values within a 24-hour window are flagged as potential duplicates for manual review.

Single-line text regions from Field2Base map to Odoo custom char fields on crm.lead. Field naming follows Odoo's snake_case convention: a Field2Base region named 'Customer Notes' becomes customer_notes__c. Character limits are preserved from the Field2Base region definition — Odoo char fields have a configurable size limit that must match or exceed the source.

Numeric regions in Field2Base (integer or decimal) map to Odoo float or integer fields on crm.lead depending on the source region type. Units of measurement from the Field2Base region definition (e.g., 'gallons', ' PSI') are stored as a separate custom char field for display context.

Field2Base dropdown regions map to Odoo selection fields on crm.lead with value-by-value mapping of each pick-list option. The selection list in Odoo is defined as a static selection list; the source values from Field2Base are enumerated exactly as they appear in the form template. If values in Field2Base were changed after some submissions were made, the migration records the original value and flags mismatches.

Photos captured in Field2Base camera regions are downloaded from Field2Base blob storage and re-uploaded as Odoo ir.attachment records linked to the corresponding crm.lead via res_model='crm.lead' and res_id=<lead_id>. A custom char field Photo_Count__c on crm.lead tracks how many photos were attached for quick reference without loading attachments.

Signature fields captured in Field2Base are stored as PNG images. These are re-uploaded as Odoo ir.attachment records with the same parent linking to crm.lead. A boolean custom field Signature_Captured__c on crm.lead indicates whether a signature was present in the original submission.

GPS data captured by Field2Base (latitude and longitude) maps to two custom float fields on crm.lead: Submission_Latitude__c and Submission_Longitude__c. Odoo does not have a native geolocation field type, so this is handled as paired float fields. The original GPS capture timestamp from Field2Base is stored as Submission_GPS_Timestamp__c for audit continuity.

Field2Base Workflow approval status (pending, approved, rejected) maps to a combination of crm.stage and custom status fields on crm.lead. If the workflow has multi-step approvals, each approval step becomes a custom char field (Approval_Step_1__c, Approval_Step_2__c) storing the approver's name and timestamp. Odoo's native stage model does not support multi-step approvals natively without Odoo Studio, so the migration surfaces the full approval history as custom fields.

The Field2Base submission timestamp (when the form was originally submitted, not when it synced) maps to a custom datetime field Submission_Datetime__c on crm.lead. Odoo's native create_date is set at migration time; the original submission datetime is preserved separately for reporting continuity. If the submission was captured offline, the local device timestamp is preserved in Offline_Capture_Timestamp__c.

Field2Base Data Integration Module (DIM) and Enterprise Dispatch Module (EDM) connections — whether ODBC, OLEDB, CSV, XML, API, or Web Services — do not have an Odoo equivalent. FlitStack exports the DIM/EDM connection definitions and mapping configurations as a JSON reference document. Rebuilt Odoo integrations must use Odoo's External API (XML-RPC or jsonrpc) or a middleware connector; FlitStack does not migrate the live connection credentials.

Some Field2Base form submissions may not include an email address for the submitter — particularly for field inspection forms filled out by third parties. These submissions become Odoo crm.lead records with partner_id set to False (anonymous lead). A custom boolean field No_Email_Flag__c is set to True for these records, and a note is added to the lead description recommending manual partner linking if the contact's email becomes known.