Migrate from Service Autopilot to Odoo CRM

Service Autopilot clients are primarily individual contact records with embedded property and billing data. We map them to Odoo res.partner records — splitting client name into firstname and lastname where a full name field exists, and preserving the primary email and phone as partner contact fields. Property address data migrates to res.partner's street, city, state, zip, and country fields. Where a client has no separate company record in Service Autopilot, we create a res.partner record with type='contact' and leave the parent_id field unset.

Service Autopilot clients flagged as commercial entities (e.g., property management companies, HOA accounts) map to Odoo res.company for the organization header and res.partner for the primary billing or contact person under that company. The company's billing address and tax ID become fields on the res.company record; individual contact details land on the linked res.partner.

Service Autopilot leads and prospects without a booked job map directly to Odoo's crm.lead object. The lead's name, email, phone, source campaign, and create date transfer as-is. Lead status in Service Autopilot (New, Contacted, Qualified) maps to Odoo's stage_id picklist via a value-mapping table — New maps to 'New', Contacted maps to 'Qualified', Qualified maps to 'Proposal Sent'. The original Service Autopilot lead score (if present) migrates to crm.lead x_studio_lead_score as a custom integer field.

Service Autopilot stores property details (address, measurements, chemicals used, GPS coordinates) as sub-records attached to the client. Since Odoo CRM has no native property object, we attach these as custom fields on res.partner — x_property_address, x_property_sqft, x_gps_latitude, x_gps_longitude, x_service_history_notes. Each client's property set becomes a block of custom fields so the property history is visible on the contact record in Odoo.

Service Autopilot completed jobs with invoiced line items map to Odoo sale.order.line records attached to a sale.order derived from the client estimate. If the Odoo accounting module is active, we generate corresponding account.move.line records for posted invoices. Job costing data (labor hours, material cost, technician) migrates as custom line description fields — x_technician_name, x_labor_hours, x_material_cost — since Odoo's native job-costing model lives in the Project module, not CRM.

Service Autopilot estimates convert to Odoo sale.order records in draft state. Estimate line items (service type, quantity, unit price) map to sale.order.line records. Estimate status in Service Autopilot (Draft, Sent, Accepted, Declined) maps to Odoo's state field — draft stays 'Draft', Sent maps to 'Sent', Accepted maps to 'Sale Order', Declined maps to 'Cancelled'. Original estimate number is preserved in the sale.order client_order_ref field.

Service Autopilot invoices migrate as Odoo account.move records when the account.account module is enabled — preserving invoice number, date, line items, tax amounts, and payment status. When only CRM is active without accounting, invoices land as sale.order records marked as locked for reference. Payment method recorded in Service Autopilot (credit card, ACH, cash) is preserved as a custom field x_payment_method on the account.move.

Service Autopilot scheduling data — dispatch board entries, route orders, assigned technicians, and GPS timestamps — has no Odoo CRM equivalent. Odoo Field Service module handles scheduling but is a separate installation beyond the base CRM. FlitStack AI exports the schedule history as a CSV attachment in the migration audit log so the data is preserved for manual reference or a future Odoo Field Service implementation.

Service Autopilot Automations (sequences of triggers, conditions, and timed email/SMS actions) cannot migrate to Odoo because they use a rule-engine model incompatible with Odoo's Automated Actions, Server Actions, and workflow triggers. We export the automation definition — triggers, conditions, action steps, and timing rules — as a structured JSON document your Odoo admin can use as a rebuild reference when configuring Odoo's automation layer.

Service Autopilot employee records (name, email, mobile, role, hourly labor rate) map to Odoo res.users for login access and hr.employee for HR and costing data. Owner resolution happens by email match — if a Service Autopilot employee email matches an existing Odoo res.users email, records are assigned to that user; otherwise they are flagged as unmatched for manual assignment before the full migration runs.

Service Autopilot custom fields at the client level become Odoo custom fields on res.partner via Settings > Technical > Custom Fields. Field types map as follows: text → char, number → float or integer depending on precision, date → date, dropdown → selection. Pick-list values from Service Autopilot custom dropdowns map to Odoo selection option labels verbatim. We pre-create the custom fields in your Odoo test instance before migration runs.

Service Autopilot files attached to client records, estimates, or invoices are downloaded from the source storage and re-uploaded to Odoo's ir.attachment table, linked to the corresponding res.partner, crm.lead, or sale.order record by res_id and res_model. File size limits on Odoo uploads apply (default 25MB per file; larger files require Odoo filesystem configuration). We preserve the original filename and MIME type in Odoo's ir.attachment fields.