Migrate from Workiz to Odoo CRM

Workiz Clients map directly to Odoo res.partner records. The partner's type field (customer, vendor, both) is set based on Workiz's client classification. Phone, email, address, and tags migrate as res.partner fields. Multi-location clients with multiple addresses require res.partner records with distinct address records linked by parent_id. For multi-site clients, each location appears as a separate child partner under the parent.

Workiz Leads map to Odoo crm.lead records in the 'lead' type state. Lead source, status, and custom scoring fields from Workiz migrate to crm.lead source, stage_id, and x_studio_score fields respectively. Unconverted leads from Workiz land in Odoo's Pipeline kanban view at the New stage.

Workiz Jobs are field service work orders that do not have a direct Odoo CRM equivalent. We map them to crm.lead records with type='opportunity', using the job title as the opportunity name, job description as the description field, and job status as the stage. Workiz job-type pick-list values map to Odoo's crm.stage name values. Completed jobs become Closed Won or Closed Lost based on Workiz status.

If the migration scope includes Workiz job scheduling data (assigned technician, scheduled date, route), those records split into Odoo project.project (one project per Workiz job type or customer) and project.task (one task per individual job booking). This requires the Odoo Project module to be installed and adds custom field mapping for technician assignment and GPS data.

Workiz Estimates map to Odoo sale.order records with state='draft'. Each estimate's line items map to sale.order.line records with product_id, description, quantity, and price_unit. Workiz tax rates are preserved as Odoo account.tax records linked by tax_name match. Estimate status (sent, accepted, rejected) maps to sale.order state transitions (sent, sale, cancel).

Workiz Invoices map to Odoo account.move records of type='out_invoice'. Line items become account.move.line entries with matching product, quantity, and unit price. Payment status in Workiz (paid, overdue, void) translates to Odoo's state and payment_state fields. Outstanding balances are preserved as residual amounts on each invoice line.

Workiz Items (parts, materials, services) map to Odoo product.product records. Item type (service vs. consumable) sets the product.type field. Unit of measure from Workiz maps to uom.uom by name match. Price from Workiz becomes product.product.list_price and standard_price depending on whether it represents a sell or cost price.

Workiz custom fields added to clients are created as custom ir.model.fields on the res.partner model before the migration runs. Field type mapping: text → char, number → float, date → date, pick-list → selection. The custom field must exist in Odoo before records load so values write on first insert.

Workiz custom fields on Jobs map to custom ir.model.fields on crm.lead. If the Workiz custom field holds JSON or multi-value data, it migrates as a char field in Odoo with the JSON serialized as a string — manual unpacking is recommended post-migration if Odoo Studio is available.

Workiz Automations (trigger-action rules with conditions) have no equivalent in Odoo CRM without Odoo Studio or custom server-action development. We export automation definitions as a JSON schema document for your Odoo consultant to reference during the manual rebuild phase.

Workiz GPS location history attached to jobs (technician location at time of arrival/departure) has no native Odoo CRM equivalent. We preserve the last-known coordinates as a note or custom char field for reference. Full route history requires the Odoo Field Service app and separate GIS configuration.

Workiz call recordings are binary files attached to jobs or clients. We download each recording and re-upload as ir.attachment linked to the corresponding crm.lead or res.partner record. Call metadata (duration, timestamp, direction) is written to a custom note on the same record.