Migrate from Inspection Files to Pipedrive

Each Inspection Files inspection becomes a Pipedrive Deal. The inspection title maps to Deal name. Pipedrive's deal pipeline stages are configured to mirror inspection workflow stages. Original inspection ID preserved in source_system_id custom field for delta-run de-duplication. The deal's close_date maps from either scheduled_date or completed_date depending on inspection status.

Client organizations migrate to Pipedrive Organizations. Client contact persons link to the Organization as Persons. Pipedrive's person-organization relationship mirrors the client-inspection parent-child hierarchy. Client industry and website fields map to corresponding Organization fields.

Primary contact on an inspection becomes a Pipedrive Person linked to the Organization. Additional contacts are added as secondary Persons under the same Organization. Email-based matching identifies existing Persons to avoid duplicate records during migration.

Site address fields (street, city, state, postal_code, country) map to Pipedrive Organization address fields. Latitude/longitude coordinates from Inspection Files store in custom fields on the Organization since Pipedrive does not have native coordinate fields. Location metadata such as site type stores in custom text fields.

Findings do not have a direct Pipedrive equivalent. Finding count, severity distribution, and last finding date migrate as custom number/date fields on the Deal. Full finding descriptions merge into a Note attached to the Deal for audit trail. Multiple findings concatenate with timestamps in the Note body.

Inspector assigned to an inspection resolves by email match against Pipedrive users. Unmatched inspectors are flagged before migration. Their records are assigned to a fallback Pipedrive user and flagged in an inspector_unmatched custom field on the Deal for admin follow-up.

Inspection templates define the checklist structure and are a workflow/configuration concept. Template names are preserved as a custom field value on the Deal (Template_Name__c) but the template itself must be rebuilt in Pipedrive or documented for manual reference. Template definitions export as JSON for admin reference.

Scheduled inspection date migrates to Deal close_date. Recurrence rules (weekly, monthly) cannot be transferred as Pipedrive has no native recurrence model for deals. Scheduled recurrence is captured as a Note and a custom recurrence_description field on the Deal for manual scheduling setup.

Inspection Files attachments (photos, PDFs, checklists) re-upload to Pipedrive Files linked to the Deal. File size limits apply per Pipedrive's 100MB per-file limit. Inline images in finding notes are extracted and rehosted as separate file attachments.

Risk level values (Low, Medium, High, Critical) require a Pipedrive custom pick-list field created on the Deal object before migration. Values map one-to-one with any missing values flagged for admin review. Validation report lists all unmapped risk levels requiring Pipedrive admin action.

Regulatory standard references (ISO 9001, OSHA, FDA 21 CFR Part 11) migrate to a Pipedrive custom text or pick-list field on the Deal. Multi-select standards stored as comma-separated values in a text field. Admin confirms pick-list vs text format before migration.

Inspection status values (Scheduled, In Progress, Completed, Overdue, Closed) map to Pipedrive pipeline stage names. Each status maps to a corresponding stage in the target pipeline. Stage probability values are set per Pipedrive stage configuration. Status transitions preserve chronological order in pipeline view.