Migrate from Field Squared to Odoo CRM

Field Squared contacts map directly to Odoo res.partner records. The company_id field on a Field Squared contact resolves to the parent res.partner with type='company'. Email, phone, and address fields migrate as-is; partner_latitude/longitude drop if no destination equivalent exists. We validate email formats against Odoo constraints before import.

Field Squared companies map to Odoo res.partner with type='contact' and is_company=True. Domain/website, industry, and employee count migrate to website, industry, and employee_count fields. Parent-company hierarchy in Field Squared maps to parent_id on res.partner — circular references flagged before migration. Industry values that lack an Odoo counterpart are migrated as custom selection options.

Field Squared tasks are the core work-order entity. They map to Odoo project.task records. The task.name becomes project.task.name. TaskType values (Delivery, Service) map to project.task tags or a custom stage category since Odoo has no native TaskType. ScheduledStart/ScheduledEnd migrate as date_deadline and planned_hours_start; these require the project module active in Odoo.

Field Squared task statuses (Not Started, In Progress, Completed) map to Odoo project.task.stage values. Each Field Squared status value maps one-to-one against a named Odoo stage. Stage probabilities are re-applied on the Odoo side based on the destination stage configuration.

Field Squared task owner_id resolves by email match against Odoo res.users. Unmatched owners are flagged as warnings before migration. The migration assigns their tasks to a fallback Odoo user or leaves user_id empty for manual reassignment — your team chooses the fallback rule during planning.

Field Squared custom fields on tasks (configured in App Builder) migrate to Odoo project.task custom fields. Each custom field requires a corresponding ir.model.fields entry in Odoo before migration. Field types map: text→char, number→float, date→date, checkbox→boolean, selection→selection. Pick-list values on selection fields map value-by-value.

Field Squared assets from the Asset Management tier map to Odoo maintenance.equipment records if the Odoo Maintenance module is activated. Asset name, serial number, and location migrate as equipment_name, serial_no, and location_id. If Maintenance is not active, assets migrate as product.product records with a custom asset_tag field for reference.

Field Squared document records (images, PDFs, files attached to tasks or assets) re-upload to Odoo's ir.attachment table linked to the corresponding project.task or maintenance.equipment record. File size limits apply: Odoo defaults to 25MB per file; larger files require Odoo configuration changes.

Field Squared engagement logs on tasks migrate as mail.message records on the corresponding project.task in Odoo. Call logs, emails, and meeting records preserve original timestamps and author_id. If Field Squared stores structured meeting data (start/end), these map to calendar.event with the project.task linked as activity_id.

Field Squared custom objects (built via App Builder) map to Odoo custom models. Odoo requires the custom model to be pre-created via Settings > Technical > Models before data lands. Relationships between custom objects translate to Odoo many2one, one2many, or many2many fields depending on the source cardinality.

Field Squared automation rules (routing logic, status-change triggers, notification rules) do not have an Odoo equivalent at the data level. These must be rebuilt in Odoo using Studio automation rules or base.automation. We export the Field Squared automation definitions as a JSON reference document for your Odoo admin.

Field Squared GPS tracking logs (technician locations, route history) are operational telemetry with no Odoo CRM equivalent. The raw coordinate data can be exported as a reference file but cannot be rendered inside Odoo without custom development. Odoo's geoengine module can display addresses but not live tracking history.

Field Squared integrations with QuickBooks, Salesforce, Oracle, Dropbox, Google Drive, Paycom, and Box do not migrate. Each integration must be re-established in Odoo using Odoo's connector framework or third-party middleware. We document the integration endpoints and authentication credentials from Field Squared for reference during rebuild.

Field Squared custom reports and dashboard widgets do not transfer to Odoo. The underlying data — work orders, tasks, contacts, assets — migrates fully, so Odoo reporting tools can reconstruct equivalent views. We export Field Squared report definitions as JSON for reference when rebuilding in Odoo Reports or custom SQL views.