Migrate from Odoo Field Service to HighLevel

Odoo's field.service.task maps directly to HighLevel's Task object. Task name, description, scheduled date, assigned user, priority, stage, and tags transfer as-is. Original create_date and write_date are preserved in custom datetime fields since HighLevel's created_at reflects migration time. Task type (one2many to field.service.type) maps to a custom pick-list field in HighLevel.

Odoo res.partner records with partner_type = 'contact' migrate to HighLevel Contact. Name, email, phone, mobile, street, city, state, country, and zip transfer as direct field maps. Partner tags (res.partner.category) map to HighLevel Contact tags. Odoo's function/title field maps to HighLevel's jobTitle custom field.

Odoo res.partner records with partner_type = 'company' migrate to HighLevel Company. Company name, website, street, city, state, country, and industry fields map directly. Employee count and revenue from Odoo (if populated) migrate as custom Number fields in HighLevel. Parent-company relationships (res.partner.parent_id) map to HighLevel's Company hierarchy via the parentId field.

Odoo's many2one relationship from res.partner to its parent company maps to HighLevel's Contact.companyId lookup field. Because the Contact–Company link is required, we create HighLevel Company records first during the migration run. Contacts are loaded after Companies so that the lookup resolves automatically; any Contact that references a missing Company is flagged for pre‑migration resolution.

Product data moves from Odoo product.product (and product.template) into HighLevel Products. We map product name, list_price, standard_price, default_code (SKU), and description directly. Odoo product categories become custom pick‑list values or tags in HighLevel. Each product can then be attached as a line item to Opportunities, allowing quote generation and revenue tracking within HighLevel pipelines.

Odoo project.project records do not have a native HighLevel equivalent. We map project.project.name as a tag on related field.service.task records and optionally create a HighLevel Custom Object named Project to hold project metadata (name, date, customer). This keeps the service context visible in HighLevel without forcing a project management module.

Odoo timesheet entries (account.analytic.line) linked to field.service.task have no direct HighLevel equivalent. We create custom Number fields on the Task object — Hours_Logged__c, Timesheet_Date__c, and Employee__c (text) — and populate them per timesheet line associated with each task. This preserves billable hour history for invoicing reference.

Odoo worksheet records (field.service.worksheet) capture field-level checklist data and e-signature. These migrate as JSON-encoded text in a custom long-text field (Worksheet_Data__c) on the HighLevel Task, preserving checklist responses and signature image URLs. Full worksheet recreation as a structured form requires a separate HighLevel form build.

Odoo stock.picking records for material deliveries linked to field service tasks have no HighLevel equivalent. We create a Custom Object named Material_Delivery__c in HighLevel, capturing picking date, state, origin (task link), and move lines as a JSON custom field. This maintains material tracking context without requiring Odoo's inventory module.

Odoo res.users records (technicians, dispatchers) are resolved by email match against HighLevel user accounts. Matched users are stored as the assigned owner on migrated Tasks and Contacts. Unmatched Odoo users are flagged before migration — teams either invite them to HighLevel first or reassign records to a designated fallback owner.

Odoo ir.attachment records linked to field.service.task are downloaded and re-uploaded to HighLevel's task attachments. File size limits in HighLevel apply — files exceeding the limit are flagged for manual handling. Inline images from Odoo notes are downloaded, re-hosted, and URLs updated in the task description.

Odoo chatter messages and tracking values on field.service.task records do not map to a HighLevel native equivalent. HighLevel has no full audit trail per Contact or Task record. We preserve Odoo chatter as a JSON-encoded custom long-text field (Odoo_Chatter_History__c) for reference, and deliver the full mail.message export as a separate CSV for compliance review.