CRM migration

Migrate from Inspection Files to Nutshell

Field-level mapping, validation, and rollback between Inspection Files and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.

Inspection Files logo

Inspection Files

Source

Nutshell

Destination

Nutshell logo

Compatibility

92%

11 of 12

objects map 1:1 between Inspection Files and Nutshell.

Complexity

BStandard

Timeline

48–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

Field-level fidelity

Every standard and custom field arrives verified.

Schema-aware mapping

AI proposes the map; you confirm before any record moves.

Relationships preserved

Parent–child, lookups, and ownership stay linked.

Full activity history

Calls, emails, meetings — with original timestamps.

Attachments & notes

Documents, uploads, and inline notes move with the record.

Why teams make this switch

Two sides of the same decision

Leaving

Inspection Files logo

Inspection Files

What's pushing teams away

  • Public documentation is thin and no API spec is published, so teams that need to integrate inspection data with permitting, GIS, or 311 systems face manual export workflows.
  • Pricing is not published — sales-led quote model slows procurement for budget-constrained municipalities.
  • Mobile experience is built for tablet PCs rather than modern smartphones and BYOD-style workflows, limiting flexibility for inspectors using personal devices.
  • Reviewer footprint is small versus competing inspection platforms (e.g., GoCanvas, iAuditor, Accela), so hiring trained Inspection Files admins or finding community support takes longer.
  • Reporting and analytics surface activity metrics but lag behind general-purpose BI tools, so larger agencies often export to a separate analytics layer.

Choosing

Nutshell logo

Nutshell

What's pulling them in

  • Lowest cost entry point among mid-market CRMs—Foundation plan starts at $13/user/month, making it accessible for teams validating CRM fit before committing.
  • Integrated sales automation and email sequencing on Pro plans without requiring a separate email marketing platform, per verified Capterra reviews.
  • Consistently praised for intuitive interface and fast onboarding, with case studies reporting 100% team adoption rates within initial deployment periods.
  • Strong customer support responsiveness cited across G2 reviews, with dedicated support tiers available on Enterprise plans.
  • Native integrations with WhatsApp, Facebook Messenger, Instagram, and Slack reduce reliance on third-party middleware for common communication channels.

Object mapping

How Inspection Files objects map to Nutshell

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

maps to

Nutshell

Company

1:1
Fully supported

Inspection 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

maps to

Nutshell

Custom field on Company

1:1
Fully supported

Inspection 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

maps to

Nutshell

Custom Inspection object or custom fields

1:1
Fully supported

Inspection 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

maps to

Nutshell

Person (with type flag)

1:1
Fully supported

Inspectors 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

maps to

Nutshell

Note / Task on Inspection

many:1
Fully supported

Inspection 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

maps to

Nutshell

Custom Date field on Company

1:1
Fully supported

Compliance 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

maps to

Nutshell

Nutshell Attachment

1:1
Fully supported

Photos 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

maps to

Nutshell

Task on Company

1:1
Fully supported

Scheduled 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

maps to

Nutshell

Custom pick-list field

1:1
Fully supported

Inspection 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)

maps to

Nutshell

Nutshell Person (owner resolution)

1:1
Fully supported

Nutshell 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

maps to

Nutshell

Custom field on Inspection

1:1
Fully supported

Inspection 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

maps to

Nutshell

No equivalent

1:1
Fully supported

Inspection 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.

Gotchas + challenges

What specifically takes care here

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 logo

Inspection Files gotchas

High

No public API reference means export relies on UI-based data extraction

Medium

Custom fields and template logic are not visible until after account review

Low

Archived inspection records may require a separate export pass

Nutshell logo

Nutshell gotchas

High

Contact tier limits enforced on import

Medium

No bulk API endpoint requires paginated extraction

Medium

Email sequences not exportable via API

Medium

Foundation plan disables key sales features

Pair-specific challenges

  • Inspection Files has no native Nutshell equivalent for compliance records

    Nutshell is built for sales pipeline management, not compliance tracking. Inspection Files stores inspection results, compliance stamps, violation records, and certificate expiry dates natively. Nutshell has no inspection, compliance, or certificate object — these must be reconstructed as custom fields on Nutshell Companies or in a custom Inspection object. FlitStack creates the custom object and field schema before migration but cannot replicate Inspection Files' native compliance workflow UI. Teams expecting inspection alerts or due-date reminders in Nutshell will need to rebuild those rules using Nutshell's workflow engine.

  • Parent-child site hierarchies require custom self-referential mapping

    Inspection Files supports hierarchical site structures (parent site containing child locations or sub-facilities). Nutshell Companies do not natively support hierarchical relationships — there is no parent-company cascade for sites. We map hierarchical sites using a custom Parent_Company__c field on the Nutshell Company record. Circular parent references (A→B→A) are flagged during validation. Teams that rely on hierarchical site drill-down in Inspection Files will lose that UI navigation in Nutshell unless a custom app or tab is built.

  • Inspection Files export tooling is often vendor-specific and limited

    Unlike Salesforce or HubSpot, many inspection software platforms including Inspection Files do not expose a public REST API or bulk export endpoint. API access, data extraction method, and rate limits vary by the specific Inspection Files vendor or deployment. FlitStack inventories the source API or export capabilities during discovery. If only CSV export is available, field parsing and date format normalization add preparation time before mapping runs. We disclose the extraction method in the migration plan before committing to a timeline.

  • Nutshell's API uses JSON-RPC with basic auth — different from REST

    Nutshell's API is JSON-RPC over HTTPS with username:API_key basic auth, not OAuth 2.0 or REST conventions. Migration tooling must use the correct auth method and JSON-RPC request format for each operation. Nutshell's API supports companies, people, leads, deals, tasks, and notes — but custom object creation may require coordination with Nutshell support or the account admin. FlitStack uses Nutshell's documented JSON-RPC endpoints and handles the authentication setup as part of the destination configuration step.

  • Photo and file attachments add file-handling overhead not present in CRM-to-CRM migrations

    Inspection Files inspections carry photos, PDFs, and supporting documents as first-class attachments. Nutshell stores attachments per record with storage limits that vary by account plan. Large inspection programs with hundreds of photos per record can exceed straightforward migration timelines. FlitStack downloads source attachments, re-uploads them to Nutshell via the API, and links them to the corresponding Inspection or Company record. Attachments that exceed Nutshell's per-file limit are flagged and resolved as a separate step with the team.

Migration approach

Six steps for a successful Inspection Files to Nutshell data migration

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

  6. 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

Context on both ends of the pair

Inspection Files logo

Inspection Files

Source

Strengths

  • Targets field inspection workflows specifically with templated checklists and mobile capture
  • Positions as a focused tool rather than a full CMMS suite, reducing complexity for small teams
  • Supports photo and signature capture tied directly to inspection records
  • Allows scheduling and recurring inspection assignments
  • Provides basic reporting on inspection pass/fail rates

Weaknesses

  • Limited published API documentation makes programmatic extraction complex
  • Small platform with fewer third-party integrations than major CMMS tools
  • No publicly available developer portal or API reference
  • Limited information on user roles and permissions architecture
  • Unclear whether archived records are included in standard exports
Nutshell logo

Nutshell

Destination

Strengths

  • Simple, intuitive interface with minimal learning curve for sales teams new to CRM
  • Per-seat pricing is transparent and predictable, with annual billing reducing monthly cost
  • Full data export tool available for all account data including backups
  • Open JSON-RPC API allows programmatic access to all core objects
  • Native multichannel engagement (email, SMS, WhatsApp) without third-party add-ons for communication

Weaknesses

  • Reporting and analytics are considered weak, requiring manual Excel exports for detailed analysis
  • No bulk API endpoint—migration requires paginated API reads that must be rate-limited carefully
  • JSON-RPC API is less common than REST, requiring custom integration code compared to standard REST CRMs
  • Add-on costs (Forms, Nutshell IQ, Email Marketing) are per-company charges that stack on top of per-seat pricing
  • Feature restrictions on entry-level plans mean teams often need mid-tier to get basic automation

Complexity grading

How hard is this migration?

Standard CRM migration. 2 of 8 objects need a mapping; the rest are 1:1.

B

Overall complexity

Standard migration

Derived from compatibility, mapping clarity, API constraints, and data volume across Inspection Files and Nutshell.

  • Object compatibility

    B

    2 of 8 objects need a mapping; the rest are 1:1.

  • Field mapping clarity

    C

    Field mapping is derived from defaults — final spec confirmed during the sample migration.

  • Timeline complexity

    B

    8-object category — typical timelines run 2–7 days end-to-end.

  • API constraints

    B

    Inspection Files: Not publicly documented..

  • Data volume sensitivity

    B

    Inspection Files doesn't expose a bulk API — REST + parallelization used for high-volume runs.

Estimator

Estimate your Inspection Files to Nutshell migration cost

Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.

Step 1

What are you migrating?

Pick a category, then your source and destination platforms.

Category

FAQ

Frequently asked questions about Inspection Files to Nutshell data migrations

Answers to the questions buyers ask most during Inspection Files to Nutshell migration scoping. Not seeing yours? Book a call.

Can't find your answer?

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 consultation

Most Inspection Files to Nutshell migrations complete within 48–72 hours of clock time for datasets under 10,000 records. Complex setups with hierarchical site structures, high photo attachment volume, or multiple custom inspection fields extend to 5–10 days. The longest planning step is designing the Nutshell custom object and field schema before any data moves — that work runs in parallel with discovery and does not add to the migration clock.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Inspection Files.
Land in Nutshell, intact.

Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.

Accuracy guarantee Rollback included Quote in 1 business day