Migrate from Assured JobCheck to Odoo CRM

JobCheck contacts map directly to Odoo res.partner records. The Salesforce ContactId is stored in a custom field x_source_id for traceability. Primary company assignment uses the partner_id lookup; contacts that lack a parent Account are linked to a default 'Unassigned' partner record, ensuring no orphan contacts remain in the Odoo database.

JobCheck companies are imported as Odoo res.partner records with is_company=True. Parent‑company hierarchies in JobCheck (represented by parent AccountId) translate to the parent_id field on the partner, preserving multi‑branch structures. Multi‑company contacts are consolidated under one primary partner, with related contacts created as child records linked via parent_id, maintaining the original relationship topology.

JobCheck job files constitute the core migration payload. Each job file is transformed into an Odoo crm.lead record, preserving the original job name, stage, and create timestamp in a custom x_original_create_date field. The current workflow stage is mapped to Odoo's crm.stage by name, ensuring the Kanban board reflects the exact progression of the restoration job.

JobCheck loss-type classifications (water, fire, mold, etc.) have no native Odoo equivalent, so we create a custom pick‑list field Loss_Type__c on crm.lead. As an optional secondary view, Odoo tags are generated per loss type, enabling quick filtering on the Kanban board and supporting reporting by loss category.

JobCheck's custom Salesforce fields for insurance policy numbers and adjuster details are migrated as Odoo custom Char fields on crm.lead: x_policy_number and x_adjuster_info. Prior to the migration run, the Odoo administrator creates these fields in Odoo Studio, confirming the field names and data types to match the source values.

JobCheck's PackOut contents module stores room-by-room inventory with item conditions and barcode references. No Odoo equivalent exists. We create a custom x_contents_line model with Many2one to crm.lead, plus fields for room, item_name, condition, and barcode. Odoo admin configures the UI view.

JobCheck task assignments per crew member map to Odoo project.task. If no Odoo project exists for a job, we create a one per crm.lead. Task stage (Not Started, In Progress, Done) maps to Odoo stage_id. Owner resolved by email match to Odoo res.users.

JobCheck notes attached to job files and contacts are imported as Odoo mail.message records with message_type set to 'comment'. Each message is linked to the appropriate res.partner or crm.lead via res_id and model, preserving the original rich‑text HTML content in the body field so that formatting such as bold or bullet lists remains intact after migration.

JobCheck files such as photos, PDFs, and inspection reports are downloaded from Salesforce Files and re‑uploaded to Odoo as ir.attachment records linked to the target res.partner or crm.lead. Files exceeding Odoo's default 25 MB limit are flagged, compressed where lossless compression is possible, or referenced via a custom Char field storing the original file URL.

JobCheck owner assignments are resolved by matching the Salesforce Owner email to an Odoo res.users email address. Unmatched owners are reported before the migration run, allowing your team to either create corresponding Odoo user accounts or assign records to a designated fallback owner, guaranteeing every migrated record has an active Odoo user.

JobCheck workflows built with Salesforce Flow and Process Builder have no direct Odoo counterpart, so they cannot be imported automatically. We export the workflow definitions as a structured PDF mapping document that lists each trigger, condition, and action. Your Odoo administrator can use this reference to recreate equivalent automation logic using Odoo Studio server actions and workflow rules.

JobCheck integrations such as QuickBooks sync, Xactimate links, and insurer portal OAuth connections are external services that live in the Salesforce configuration. Since Odoo does not host these connections, each must be re‑established as a new Odoo integration after migration. We provide a Connected Systems Inventory that enumerates every active integration, including endpoints and authentication details, so your admin can rebuild them in Odoo.