Migrate from FieldAware by GPS Insight to Odoo CRM

FieldAware Customer maps to Odoo res.partner with partner_type set to 'company'. The customer name, primary address, phone, and email transfer directly. FieldAware's customer_id becomes the Odoo partner id. If the FieldAware customer has multiple locations, each location is imported as a child contact (address type) under the parent res.partner record.

FieldAware Contact maps to Odoo res.partner as a person-type partner linked to its parent customer (company) via type='contact'. The contact name, email, phone, mobilephone, and job title transfer directly. If the same person appears under multiple FieldAware customers, Odoo's contact-de-duplication wizard identifies duplicates by email before insertion.

FieldAware Location records carry GPS coordinates, address, and location-specific contact info. Odoo CRM has no native Location object. We map Location records as child res.partner address records under the parent Customer, preserving street, city, state, zip, and country. GPS latitude/longitude is stored in custom fields on the address partner since Odoo core lacks geolocation without the geoengine module.

FieldAware Job records have no direct Odoo CRM equivalent. We offer two migration paths: (1) Map Job to crm.lead as an Opportunity, capturing job_number as name, job status as stage_id, and scheduled date as date_deadline. (2) If Odoo Project is installed, map Job to project.task with the customer as project partner. The split is decided during the audit phase based on whether the customer uses Odoo Project and whether job records need to be tracked as billable project tasks or as closed historical records.

FieldAware job line items (parts, labor, services) carry item name, quantity, unit price, and tax. Odoo Opportunity has no line-item structure. If Odoo Sales is activated, we create a draft quotation (sale.order) linked to the Opportunity and populate line items from the Job record. If Sales is not activated, line items are preserved as a formatted text note on the Opportunity record for manual re-entry.

FieldAware Asset records store serial_number, make_model, location, and maintenance history. Odoo CRM has no Asset object. If the Odoo Maintenance module (maintenance.equipment) is installed, we map Asset to equipment records linked to the customer partner. If Maintenance is not installed, Asset data is preserved as a reference custom field on the customer res.partner record for manual re-entry into a future asset-tracking system.

FieldAware Invoice records map to Odoo account.move with move_type='out_invoice'. Invoice number, partner_id, invoice date, amount, and status transfer directly. If the FieldAware invoice references a Job, the job_number is stored in Odoo's invoice reference field. Line items from the FieldAware invoice are mapped to account.move.line records. Odoo Accounting must be installed and configured before this mapping runs.

FieldAware Quote records map to Odoo sale.order with state='draft'. Quote number, customer, line items, and total amount transfer directly. If the FieldAware Quote has a status of 'accepted', we set Odoo's sale.order to state='sent' to reflect that it has been delivered. Status 'expired' maps to Odoo's validity_date check.

FieldAware Tasks linked to Jobs map to project.task records under the corresponding Job-Project if Odoo Project is installed. Standalone FieldAware Tasks (not linked to a job) map to crm.lead activities (mail.message) on the related customer partner record, preserving the task name, description, and due date as a logged note.

FieldAware custom fields are declared per entity type and carry type (Text, Number, CheckBox, Dropdown, Date, Time). Odoo defines custom fields via ir.model.fields globally. We map FieldAware's custom fields to Odoo ir.model.fields on the equivalent model: custom fields on FieldAware Customer become fields on res.partner; custom fields on Job become fields on crm.lead or project.task depending on job mapping choice. Dropdown-type custom fields require Odoo selection fields with value-by-value mapping.

FieldAware User records include name, email, role, and mobile. Odoo res.users records represent system login accounts. We map FieldAware users to Odoo res.users by email match. If the FieldAware user has no Odoo login yet, they are flagged as unassigned and routed to the customer for user provisioning. Technician-specific fields ( certifications, service areas) migrate as custom fields on the res.users record.

FieldAware Item records (part number, description, unit price) map to Odoo product.product. Item type (service vs. consumable) maps to Odoo's product.type field. If the FieldAware item has a custom barcode, we store it in product.product.barcode. The product is created as a 'can be sold' product template so it is available in Odoo Sales quotations.