Migrate from Inspection Files to Freshsales

Freshsales requires Pro or Enterprise plan for Custom Objects

Inspection Records and Checklist Items map to Freshsales custom objects, but custom objects are only available on the Pro plan ($39/user/month) and above. Growth plan accounts cannot create custom objects via the UI, and custom objects created via API on Growth are not fully accessible through the UI. We confirm the destination plan tier during scoping and recommend a plan upgrade to Pro before migration if the account is on Growth. If upgrading is not feasible, we can flatten the inspection hierarchy into Tasks with extended custom fields on the Account object — we document this trade-off in the pre-migration plan.

Inspection Files workflows and approval chains do not migrate

Inspection Files inspection submission approvals, escalation triggers, and auto-assignment rules have no equivalent in Freshsales Automation Rules — the trigger models are structurally different. We export every Inspection Files workflow definition (trigger conditions, assigned roles, escalation paths) as a Workflow_Rebuild_Reference.json file. Your Freshsales admin uses this to configure Automation Rules in Freshsales that approximate the original logic. The inspection history (approval timestamps, sign-off users) does migrate as custom datetime fields on the Inspection_Record__c object, so the audit trail is preserved even if the automation is rebuilt.

Freshsales API rate limits affect bulk migration throughput

Freshsales enforces a rate limit of 100 API calls per minute per app integration. For large inspection datasets with many findings and attachments, this means bulk inserts must be batched and throttled. We implement queue-based batched insertion with exponential backoff on 429 responses, and we run migration batches during off-peak hours to minimize impact on live users. The migration tool logs every rate-limit hit and retries automatically — no manual intervention is required. If your Freshsales account is on a lower API tier, we surface this during scoping and adjust the batch size.

Inspection Files template structure requires pre-migration Freshsales schema setup

Inspection Files templates define which fields and checklist items appear per inspection type. Because Freshsales has no native template concept, each template's field set must be pre-configured as custom fields on the Inspection_Record__c and Inspection_Item__c custom objects before data lands. We deliver a Schema_Preparation_Plan.csv listing every template, its fields, and the corresponding Freshsales custom field API names and types. This plan is generated during the scoping phase so your Freshsales admin can create the schema before the migration run — data lands into a pre-validated schema rather than requiring post-migration field creation.

Photo attachments must be re-hosted in Freshsales Files

Inspection Files stores photos and documents on their own cloud storage; these URLs do not resolve after account deactivation. We download all attachment blobs during the migration extraction phase, re-upload them as Freshsales Files, and link them to the parent record (Inspection_Record__c or Task). The original filename and a Source_Attachment_ID__c field are preserved in the Freshsales File metadata for traceability. For large volumes of high-resolution photos, the attachment re-hosting step is the longest part of the migration clock time — we estimate this separately during scoping based on total attachment volume.