Migrate from Inspection Files to monday CRM

Each Inspection Files inspection record becomes a monday CRM Deal (if using standard CRM entities) or a board Item on a custom Inspections board. The inspection name maps to Deal Name or Item Name, inspection date to Close Date or a custom Date column, and status to the Status column with value-by-value mapping from Inspection Files statuses to monday status groups.

Inspection Files site records map to monday CRM Organizations. Site name maps to Organization Name, address fields map to Address columns (street, city, state, zip), and site contact name/email map to the Primary Contact person column. Sites with no associated contact land as Organizations with no linked Person column.

Inspector profiles from Inspection Files (name, email, phone, role) map to monday CRM Contacts. Email is the primary key for deduplication. If the inspector is also a monday CRM user, the Contact record links to the monday user via the Person column on Items assigned to them.

Inspection Files findings attached to an inspection can map two ways: as monday Sub-items on the inspection Item (preserving individual finding status, severity, and description) or as a set of custom columns on the parent Item (Severity, Finding Status, Corrective Action) aggregated per inspection. The mapping choice depends on how your team queries findings — sub-items enable per-finding reporting; columns enable at-a-glance board views.

Inspection Files severity levels (Critical, Major, Minor, Observation) map to monday Status labels or a Number column with 1–4 values. FlitStack preserves the exact label names if your monday Status column is configured with matching labels; otherwise a lookup table maps source values to the nearest available Status options.

Inspection Files file attachments (photos, PDFs, signed forms) re-upload to monday's File column on the inspection Item. monday stores files up to 250MB per file on Pro and Enterprise plans. Inline images embedded in finding descriptions are extracted, downloaded, and re-uploaded as separate File column entries.

Inspection Files templates define the inspection form structure (fields, required flags, finding types). monday has no template-import mechanism from external systems. We export the template schema as JSON including field names, types, and conditional logic — your monday admin rebuilds the board columns and sub-item structure from this reference.

Inspection Files automated assignment rules and escalation workflows do not transfer to monday. FlitStack exports the rule definitions (trigger conditions, assignee logic, notification steps) as a structured document. Your monday admin rebuilds these as Automation recipes using monday's When-Then recipe builder or via the monday API for more complex branching logic.

Inspection Files audit logs (who changed a finding status, when an inspection was completed) preserve as custom Update-type columns on the inspection Item or as a separate Activity board linked by Item Name. Original timestamps and user emails are preserved as text strings in these columns for reference.

Signed inspection certificates or electronic signatures stored in Inspection Files migrate as File attachments in monday's File column. If the source stores a simple yes/no confirmation, this maps to a monday Checkbox column with the inspector's sign-off date preserved as a Date column.