Migrate from Inspection Files to Twenty CRM

Inspection records have no native destination equivalent — custom objects must be created first

Twenty CRM has no built-in inspection record object. Inspection Files stores inspections, findings, and schedules as structured records, but in Twenty these require custom objects created before any data can be imported. The Twenty documentation explicitly warns: 'Fields must exist before import — the CSV import creates records, not fields.' FlitStack creates the InspectionRecord and InspectionFinding custom objects in Twenty's Settings → Data Model before running any import, including all required fields, select options, and relation fields to link findings to parent records.

Twenty CSV import is capped at 2,000 rows per file in the web UI — larger inspection datasets need API-based import

Inspection Files exports can contain thousands of finding records per inspection. The Twenty web UI caps CSV imports at 2,000 rows per file. A single inspection with 500 findings quickly exceeds this for a team running hundreds of inspections monthly. FlitStack handles this by using Twenty's REST and GraphQL API directly (100 req/min on Pro, 200 req/min on Organization) to bulk-load inspection records and findings in batches, avoiding the web UI cap entirely. This requires workspace member invitations to be accepted before user-resolved fields can link correctly.

Inspection Files inspection workflows and scheduling automations do not migrate — they must be rebuilt

Inspection Files inspection workflows (auto-assignment, reminder triggers, recurring schedule logic) are a domain-specific automation layer. Twenty's workflow builder (Organization tier) can replicate these behaviors, but no workflow definitions export from Inspection Files. The Twenty documentation states: 'Views, workflows, and permissions must be recreated manually after migration.' FlitStack exports all workflow definitions as a configuration reference document so your Twenty admin can rebuild the logic in Twenty's workflow builder after data is live.

Inspector email resolution requires Twenty workspace members to exist before import

When Inspection Files stores an inspector's email on each inspection record, FlitStack uses that email to resolve the inspector to a Twenty People record and a workspace member account. If the inspector's email does not match an invited Twenty workspace member, the relation cannot be created at import time. The Twenty migration guide explicitly requires: 'Invite users BEFORE importing data — if your data includes user references, those users must exist in Twenty before import.' FlitStack flags unmatched inspector emails before migration and provides a list for your team to invite or create placeholder users.

Inspection Files attachments re-upload to Twenty but lose original metadata outside the migration window

Inspection Files attachments (photos, PDFs, signed forms) are stored on the source platform. Twenty has its own file storage model. FlitStack downloads all attachments from Inspection Files and re-uploads them to Twenty's file storage, linking each file to the parent InspectionRecord or InspectionFinding record. However, inline image metadata, EXIF data, and original upload timestamps are not preserved. Attachments modified in Inspection Files after the delta-pickup window closes are not re-captured. Teams should document any attachment that needs chain-of-custody metadata before migration.