Migrate from Jobber to Odoo CRM

Jobber clients map directly to Odoo res.partner records. B2C clients (homeowners) and B2B clients (commercial accounts) both use the same partner model. Jobber client tags migrate as Odoo tags on the partner record. Primary contact details (name, email, phone) populate the partner fields directly.

Jobber properties are service-site records attached to a client. In Odoo, each property becomes a partner address record (type='contact' or 'other') linked to the same partner parent. Property-specific custom fields (e.g., system type, access instructions) require Odoo custom fields on res.partner before the mapping can resolve.

A Jobber quote maps to two Odoo records: a crm.lead in the Opportunity stage holding the client link, total value, and pipeline stage, plus a sale.order quotation holding the line items. The sale.order links back to the opportunity. This 1-to-2 expansion is necessary because Odoo stores quotation details (line items, taxes, terms) on sale.order, not on crm.lead.

Each Jobber quote line item (product, quantity, unit price, description) becomes a sale.order.line record attached to the migrated sale.order. If the line references a Jobber product, Odoo attempts to match by internal reference; unmatched products are created as Odoo product templates with the Jobber description as the product name.

Jobber jobs do not have a native Odoo CRM equivalent. The job record — assigned team member, scheduled date/time, job status, and internal instructions — migrates as a planned mail.activity on the related opportunity (or on the client partner if no opportunity exists). Job status is preserved in a custom Char field on the activity for reconciliation.

Job line items (materials, labor rates) that carry financial value migrate as sale.order.line records on the migrated quotation. If the job was invoiced separately via Jobber, those line items are preserved as invoice lines (account.move.line) with a link back to the original opportunity for audit continuity.

Jobber invoices (jobber_object: invoice) map directly to Odoo account.move records with type set to 'out_invoice'. The invoice_number from Jobber becomes the Odoo ref field for reference matching. Invoice status transitions (draft, sent, paid, void) correspond directly to Odoo account.move state values (draft, posted, paid, cancelled). Any partial payments recorded in Jobber attach to the account.move as reconciled payment lines, maintaining the full payment history in Odoo's account.payment model.

Jobber team members serve two roles: a login identity and a contact record for assignment. In Odoo, the team member becomes a res.users record (for login) with a linked res.partner contact record holding name, email, and phone. Role and permissions from Jobber are not directly translatable to Odoo's access-control groups — your Odoo admin sets those separately.

Jobber custom fields exist as key-value properties on clients, properties, quotes, jobs, invoices, and team members. Each Jobber custom field requires a corresponding custom field on the matching Odoo model (res.partner, sale.order, crm.lead, etc.) created in Odoo Settings > Technical > Custom Fields before the migration loads data. Field data type (text, number, date, picklist) must match the Odoo field definition.

Jobber file attachments on clients, properties, quotes, jobs, or invoices download and re-upload to Odoo as ir.attachment records linked to the matching Odoo model. File size limits and MIME types are preserved. Inline images in notes are extracted and rehosted as Odoo attachments.

Jobber automations (automated triggers on quote_sent, job_completed, payment_received) do not have a functional equivalent in Odoo CRM and are not migrated. They must be rebuilt as Odoo Automated Actions (Settings > Technical > Automation > Automated Actions) using the same trigger conditions and action logic. FlitStack exports the automation definitions as a reference document for your Odoo admin.

When a Jobber client has multiple properties (service sites), each property migrates as a separate address child record on the same parent partner in Odoo. The property label (e.g., 'Primary Site', 'Secondary Site') is stored in the address street3 or a custom field to preserve identification. Odoo treats these as address records, not separate contact records.