Migrate from Inspection Files to Odoo CRM

Each Inspection Files inspection record maps to one Odoo crm.lead. The inspection title becomes crm.lead.name; inspection date maps to lead create_date; the assigned inspector resolves by email to Odoo res.users. Unmatched inspectors store as x_inspector_name custom field on the lead. Inspections without a location link create standalone leads; those with location links create leads with a partner_id pointing to the mapped res.partner.

Inspection Files templates define the checklist structure. Since Odoo crm.lead has no native template field, FlitStack creates an x_template_name char field on crm.lead and writes the source template name into it. The template's item list and scoring logic does not migrate — teams must rebuild checklist logic in Odoo Studio or as Python addon custom fields.

Inspection Files findings include severity, description, photo, and status. FlitStack writes the first 5 findings as comma-separated lines in x_findings_summary on crm.lead. Each finding with an attached photo creates a separate ir.attachment linked to the crm.lead via the XML-RPC create() call. Findings exceeding 5 attach as ir.attachment records only, with the lead description noting 'N additional findings stored as attachments.' Teams needing granular finding tracking should configure a custom crm.lead.findings model via Odoo Studio after migration.

Inspection Files locations (sites, facilities) map to Odoo res.partner records of type 'company'. The location name becomes res.partner.name; address fields map directly. Parent-child location hierarchies map via res.partner.parent_id. Locations without an associated company contact create res.partner records with no linked contacts — flagged for manual review post-migration.

Inspection Files equipment records linked to inspections can split two ways: the equipment ID stores in x_asset_ref on crm.lead as a reference string. If the Odoo Maintenance module is active, FlitStack also creates maintenance.equipment records for each unique asset, linking back to the location's res.partner as partner_id. Equipment without Odoo Maintenance installed remains as a custom field reference only — teams can activate the module post-migration to populate it.

Inspection Files user accounts match to Odoo res.users by email address. Matched inspectors populate x_inspector_id (many2one to res.users) on the crm.lead. Inspection Files users without an Odoo account (e.g., read-only viewers) are flagged — their historical inspection records migrate with x_inspector_name populated, but no Odoo user link is created. FlitStack delivers a user-unmatched report so the admin can either create Odoo accounts or accept the custom-field-only reference.

Inspection Files file attachments (photos, PDFs, signed forms) download from the source API and re-upload to Odoo ir.attachment, linked to the parent crm.lead via res_id and res_model='crm.lead'. Odoo's ir.attachment stores files in its filestore or on cloud storage (depending on Odoo configuration). Inline images in finding descriptions download and rehost as individual ir.attachment records. Attachment count per lead is flagged if it exceeds 25 — Odoo list views can degrade with large attachment sets.

Inspection Files status values (Draft, In Progress, Completed, Passed, Failed) map to Odoo crm.stage records. FlitStack creates stage records matching the source status names in the target Odoo pipeline. Stage transition timestamps from Inspection Files migrate as x_stage_changed custom datetime fields on crm.lead for reporting continuity. The pipeline stage color coding is preserved as stage color attributes.

Inspection Files organizations map to res.partner records of type 'company'. The organization name maps to res.partner.name; industry, employee count, and revenue fields map to their Odoo counterparts. Multi-location organizations get a parent res.partner with child records for each location. Contacts within the organization link via res.partner.contact_ids.

Inspection Files custom fields on inspections create x_ prefixed fields on crm.lead. Field types map as follows: text → char, number → float, date → date, yes/no → boolean, dropdown → selection. Validation rules and conditional visibility from Inspection Files do not carry over — Odoo Studio or Python addon code must reproduce that logic post-migration. FlitStack delivers a field-mapping manifest listing every source custom field and its destination x_ equivalent.

Inspection Files generates PDF inspection reports tied to each inspection record. These are downloadable files, not structured data. FlitStack can attach the source PDF to the corresponding crm.lead as ir.attachment with datas and res_model='crm.lead'. However, Odoo does not natively render or index PDF content in lead search — this is informational attachment only, not a searchable report. Teams needing report-level search should rebuild reports in Odoo Reporting or a BI addon.

Inspection Files recurring inspection schedules and auto-assignment rules are destination-side workflow logic and do not migrate. FlitStack exports the schedule configuration as a JSON manifest for reference. Teams must rebuild recurring inspection logic in Odoo using Calendar + Crm Automated Actions, or via a custom addon. The schedule manifest helps the Odoo admin understand the original cadence before rebuilding.