CRM migration
Field-level mapping, validation, and rollback between Inspection Files and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Inspection Files
Source
Nutshell
Destination
Compatibility
11 of 12
objects map 1:1 between Inspection Files and Nutshell.
Complexity
BStandard
Timeline
48–72 hours
Overview
Inspection Files stores a field-inspection data model: Sites (facilities/locations), Assets (equipment under inspection), Inspections (audit events tied to a site or asset), and Inspectors (people who conduct the work). Timestamps, compliance statuses, and findings live on inspection records. Nutshell is a sales-focused CRM with People, Companies, Leads, and Deals as primary objects, plus Tasks, Notes, and Activities for relationship history. There is no native inspection or compliance object in Nutshell — inspection records, site hierarchies, and compliance data require custom fields on Nutshell Companies or a custom Inspection object. FlitStack AI maps Inspection Files Sites to Nutshell Companies, Assets to custom fields on those company records, and Inspection records to either custom fields or a custom Inspection object depending on data volume. Inspector assignments route to Nutshell People with a custom inspector-type flag. We preserve original inspection dates as custom datetime fields since Nutshell's created timestamp reflects the import moment. All API-based extraction from Inspection Files uses scoped read access; the Nutshell side loads via Nutshell's JSON-RPC API with rate-limit awareness.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a Inspection Files object lands in Nutshell, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
Inspection Files
Site / Location
Nutshell
Company
1:1Inspection Files Sites (facilities, properties, locations under inspection) map to Nutshell Companies. Site address, name, and type migrate as Company fields. Nutshell does not support hierarchical sites natively — if Inspection Files uses parent-child site relationships, the parent maps as Company and children attach via a custom Parent_Site__c field.
Inspection Files
Asset / Equipment
Nutshell
Custom field on Company
1:1Inspection Files Assets (equipment, systems, or sub-locations tied to a Site) do not have a native Nutshell equivalent. We map assets to custom fields on the corresponding Nutshell Company record — asset name, type, and status become text or pick-list custom fields. High-volume asset lists may warrant a Nutshell custom object instead.
Inspection Files
Inspection Record
Nutshell
Custom Inspection object or custom fields
1:1Inspection Records are the core data entity in Inspection Files. Nutshell has no native inspection object. FlitStack creates a custom Inspection object in Nutshell with fields mirroring the source record: inspection date, type, status, findings, compliance result, and links to the parent Company and Person (inspector). If volume is low, records may instead attach as custom fields on the Company.
Inspection Files
Inspector
Nutshell
Person (with type flag)
1:1Inspectors from Inspection Files map to Nutshell People. A custom pick-list field Inspector_Type__c is added to distinguish inspectors from regular contacts. If the inspector also has a client relationship, they appear as a Person record with the flag set. Nutshell does not support a dedicated inspector role object.
Inspection Files
Inspection Finding
Nutshell
Note / Task on Inspection
many:1Inspection Files findings (individual observations, violations, or notes within an inspection) are too granular for a single Nutshell field. We merge findings into a Nutshell Note attached to the Inspection record, preserving each finding's description, severity, and resolution status. If findings need individual tracking, each becomes a Task.
Inspection Files
Compliance Certificate
Nutshell
Custom Date field on Company
1:1Compliance certificates and expiry dates from Inspection Files migrate to custom date fields on the corresponding Nutshell Company record (e.g., Compliance_Expires__c). Nutshell's native date fields accept the ISO date format from Inspection Files directly. Multiple certificate types become separate custom date fields.
Inspection Files
Inspection Photo / Attachment
Nutshell
Nutshell Attachment
1:1Photos and attachments from inspection records are re-uploaded to Nutshell and linked to the corresponding Inspection record or Company. Nutshell's attachment limit per record applies (standard file storage limits per account tier). We preserve original file names and capture the inspection date as the attachment description.
Inspection Files
Inspection Schedule / Due Date
Nutshell
Task on Company
1:1Scheduled inspection due dates from Inspection Files become Nutshell Tasks linked to the Company record. Task subject carries the inspection type; due date maps from the source schedule field. Recurring schedules are represented as a recurring task pattern in Nutshell if the workflow supports it, or as individual tasks for each occurrence.
Inspection Files
Inspection Type / Category
Nutshell
Custom pick-list field
1:1Inspection type labels (e.g., safety audit, environmental review, equipment check) from Inspection Files map to a custom pick-list field on the Nutshell Inspection object. We map each value by name — values with no exact Nutshell equivalent are added as new pick-list options before migration runs.
Inspection Files
User / Owner (Inspector or Admin)
Nutshell
Nutshell Person (owner resolution)
1:1Nutshell does not have a dedicated inspector owner object. Inspection Files users are resolved by email match against existing Nutshell People. Unmatched users are flagged and can be invited to Nutshell before the migration, or their records are assigned to a fallback Person record designated as the migration owner.
Inspection Files
Custom Inspection Field
Nutshell
Custom field on Inspection
1:1Inspection Files custom fields (fields added by the admin beyond standard inspection fields) are created as Nutshell custom fields on the Inspection object. Field types are preserved: text to text, date to date, pick-list to pick-list. Nutshell's custom field UI allows creation before migration; we coordinate the field creation step as part of the schema setup phase.
Inspection Files
Workflow / Alert Rule
Nutshell
No equivalent
1:1Inspection Files scheduling triggers, due-date alerts, and re-inspection reminders are workflow constructs that do not migrate. Nutshell's workflow rules and email sequences (Pro+) can replicate some scheduling logic but require a rebuild. FlitStack exports the rule definitions from Inspection Files as a structured reference document for the Nutshell admin.
| Inspection Files | Nutshell | Compatibility | |
|---|---|---|---|
| Site / Location | Company1:1 | Fully supported | |
| Asset / Equipment | Custom field on Company1:1 | Fully supported | |
| Inspection Record | Custom Inspection object or custom fields1:1 | Fully supported | |
| Inspector | Person (with type flag)1:1 | Fully supported | |
| Inspection Finding | Note / Task on Inspectionmany:1 | Fully supported | |
| Compliance Certificate | Custom Date field on Company1:1 | Fully supported | |
| Inspection Photo / Attachment | Nutshell Attachment1:1 | Fully supported | |
| Inspection Schedule / Due Date | Task on Company1:1 | Fully supported | |
| Inspection Type / Category | Custom pick-list field1:1 | Fully supported | |
| User / Owner (Inspector or Admin) | Nutshell Person (owner resolution)1:1 | Fully supported | |
| Custom Inspection Field | Custom field on Inspection1:1 | Fully supported | |
| Workflow / Alert Rule | No equivalent1:1 | Fully supported |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
Inspection Files gotchas
No public API reference means export relies on UI-based data extraction
Custom fields and template logic are not visible until after account review
Archived inspection records may require a separate export pass
Nutshell gotchas
Contact tier limits enforced on import
No bulk API endpoint requires paginated extraction
Email sequences not exportable via API
Foundation plan disables key sales features
Pair-specific challenges
Migration approach
Inventory Inspection Files data model and export capabilities
FlitStack reviews the Inspection Files account — object list, custom fields, file attachments, and export or API access method. If Inspection Files provides a bulk export, we parse the output; if only per-record API access is available, we coordinate extraction rate limits and pagination. We produce a data inventory document listing every object, field, and attachment volume before writing a single record to Nutshell.
Design Nutshell custom schema for inspection data
Before data moves, FlitStack creates the custom Inspection object and all required custom fields in Nutshell — Inspection_Type__c, Status__c, Compliance_Result__c, Site lookup, Inspector lookup, Original_Inspection_Date__c, and any source custom fields. We also create custom fields on the Nutshell Company record for asset data, compliance dates, and parent-site references. This schema setup plan is delivered to the Nutshell admin for review before we proceed to extraction.
Match inspectors to Nutshell People by email
Inspection Files inspector records are matched against existing Nutshell People by email address. Inspectors who have no Nutshell account are flagged and assigned to a fallback Person record; the team can choose to invite them to Nutshell before migration so their records land correctly. No Inspection record inserts without a resolved inspector reference — unmatched assignments are reported and resolved in the sample phase.
Sequence migration: Sites → Inspectors → Inspections
Inspection records reference Sites (which map to Companies) and Inspectors (which map to People). Nutshell requires foreign keys to resolve on insert. We migrate in strict sequence: Sites become Companies first, then Inspectors become People, then Inspection records insert with Company and Person lookups resolved. The sequence is automated; circular or missing references are flagged and surfaced in the pre-migration validation report.
Run sample migration with field-level diff
A representative slice — typically 50–200 records across Sites, Inspectors, and Inspections — migrates first. FlitStack generates a field-level diff showing source values against the Nutshell destination fields so the team can verify date formatting, pick-list mapping, compliance result values, and inspector assignment before the full run commits. Adjustments to mapping logic are documented and validated during this phase before proceeding to the full migration run.
Execute full migration with delta pickup and rollback readiness
The full migration runs against Nutshell's JSON-RPC API. A delta-pickup window (typically 24–48 hours) captures any inspection records created or updated in Inspection Files during cutover. All operations are logged to an audit trail. If reconciliation identifies discrepancies — missing records, incorrect inspector assignments, or attachment failures — one-click rollback reverts the Nutshell account to its pre-migration state for a clean retry.
Platform deep dives
Inspection Files
Source
Strengths
Weaknesses
Nutshell
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 2 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Inspection Files and Nutshell.
Object compatibility
2 of 8 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
Inspection Files: Not publicly documented..
Data volume sensitivity
Inspection Files doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during Inspection Files to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your Inspection Files to Nutshell migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave Inspection Files
Other ways to arrive at Nutshell
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.