Migrate from Jobsite Mobile to Odoo CRM

Jobsite Mobile job records map 1:1 to Odoo crm.lead. The job name becomes crm.lead name, client company links to res.partner via partner_id, and job status maps to Odoo stage_id using a value-mapping table defined per pipeline. All original timestamps and creator IDs are preserved in custom fields to maintain audit trails.

For jobs with multiple sub-tasks (phases, work items), FlitStack creates Odoo project.task records linked to the crm.lead. A project.project record acts as the container when job sub-tasks span multiple workers. Odoo Project app must be installed on the destination instance.

Jobsite Mobile client records map to Odoo res.partner with type='contact'. Client name maps to partner name, billing address maps to partner address fields, and phone/email map directly. Parent-company hierarchies in Jobsite Mobile map to Odoo's commercial partner link. If a client has multiple contacts, each contact is created as a child partner linked to the parent company.

Workers are not Odoo users by default — FlitStack resolves each Jobsite Mobile worker by email match against Odoo hr.employee records. Workers without a matching Odoo employee get a placeholder hr.employee record created with a custom field flagging the original source. User licenses (portal vs. regular) are a separate Odoo configuration step.

Jobsite Mobile worker-to-job assignments map to project.task user_id field in Odoo Project. When multiple workers are assigned to one job task, FlitStack creates multiple project.task records or uses Odoo's Resource Allocation feature to represent the full crew. The mapping also records the original assignment date to preserve scheduling history.

Each Jobsite Mobile time entry (worker + job + start/end/duration) becomes an Odoo project.timesheet.line record. The hr.employee field links to the resolved Odoo employee, and the project_id links to the project.container for the job. Duration in hours converts to Odoo's internal unit-of-measure (hours).

Jobsite Mobile estimates map to Odoo sale.order in quotation state. Line items map to sale.order.line with product_id resolution. When estimates have been accepted in Jobsite Mobile, the corresponding sale.order is confirmed during migration. Odoo requires sale_timesheet or project app active for time-and-materials tracking.

Jobsite Mobile custom properties on job records require Odoo custom fields created via Studio or programmatically via ir.model.field. FlitStack creates these fields on crm.lead before migration runs and maps each property value. Field types (text, number, date, selection) are inferred from Jobsite Mobile property types.

Jobsite Mobile file attachments on jobs and clients re-upload to Odoo ir.attachment linked to the corresponding res.partner or crm.lead record. Odoo's filestore handles the file storage; inline images in notes are extracted and rehosted as separate attachments. File metadata such as original filename and upload date are stored in ir.attachment's res_field and create_date for reference.

Jobsite Mobile job templates (pre-built job structures with default line items and workers) have no direct Odoo equivalent. Odoo's sale.order.template handles quotation templates but not job-structure templates. These must be rebuilt manually or via Odoo Studio before go-live. FlitStack provides a detailed template inventory export to guide the reconstruction process.

Jobsite Mobile availability and scheduling rules cannot migrate to Odoo because Odoo resource calendars work differently — they define working hours and leaves, not job-to-worker matching logic. The team should map these manually in Odoo Project's resource calendar after migration.

Jobsite Mobile logged calls, site visits, and notes map to Odoo mail.message records attached to the crm.lead. Original timestamps, authors, and subject lines are preserved. Odoo's mail tracking must be enabled to receive these on the crm.lead form. If mail tracking is not active, FlitStack stores the activity data in custom fields on the lead record.