CRM migration

Migrate from Assured JobCheck to Nutshell

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

Assured JobCheck logo

Assured JobCheck

Source

Nutshell

Destination

Nutshell logo

Compatibility

92%

11 of 12

objects map 1:1 between Assured JobCheck and Nutshell.

Complexity

BStandard

Timeline

48–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Assured JobCheck is a Salesforce-native restoration job management platform that handles job files, task assignments, photo documentation, and contents inventory (via Assured PackOut) for property-loss companies. Nutshell CRM is a lightweight sales CRM built for small-to-mid-market teams with standard contact, company, lead, and deal objects plus custom fields on each entity. The migration carries everything Assured JobCheck stores natively — contacts, companies, jobs-as-deals, activity history, custom fields, and attachments — into Nutshell's simpler object model. The harder problems are translating Assured JobCheck's job-status workflow states into Nutshell pipeline stages, preserving PackOut inventory items as line items or notes on Nutshell deals, handling the multi-object job-file structure (parent job + child tasks + photo folders) in a flat CRM model, and mapping Assured JobCheck's Salesforce-built custom fields to Nutshell's per-entity custom field system. We use Assured JobCheck's Salesforce API export endpoint to extract source data, transform it to Nutshell's JSON-RPC API format, and load via Nutshell's bulk import endpoint with owner resolution by email match. Automations, workflows, and the Assured PackOut barcode-scanning logic do not migrate — we export definitions for your team to rebuild in Nutshell's automation tools.

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

Assured JobCheck logo

Assured JobCheck

What's pushing teams away

  • Lack of public pricing transparency beyond the $35 entry tier makes budget planning difficult and suggests expensive enterprise pricing for larger franchises, deterring cost-sensitive buyers.
  • Limited market footprint as a niche restoration-industry tool means fewer third-party integrations, community resources, and peer reviews compared to horizontal job management platforms.
  • Smaller user base compared to platforms like Jobber or Buildertrend reduces confidence in long-term product development and vendor stability for franchise operators.
  • Absence of visible API documentation or developer community makes custom integrations with billing, accounting, or vertical-specific tools difficult to evaluate before purchase.
  • No transparent per-seat or unlimited pricing tiers beyond entry level creates uncertainty about total cost of ownership as teams grow.

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 Assured JobCheck objects map to Nutshell

Each row shows how a Assured JobCheck 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.

Assured JobCheck

Contact (Person)

maps to

Nutshell

Person

1:1
Fully supported

Assured JobCheck stores contact records for policyholders, adjusters, and crew leads as standard Salesforce Contacts. These map directly to Nutshell Persons. Owner resolution by email match against Nutshell users. Records without an assigned owner attach to a fallback user flagged before migration.

Assured JobCheck

Company (Account)

maps to

Nutshell

Company

1:1
Fully supported

Assured JobCheck's insurance carrier, subcontractor, and property‑owner company records (Salesforce Accounts) map 1:1 to Nutshell Companies. Parent‑company hierarchies in Salesforce map to Nutshell's parent‑company field. Multi‑contact companies collapse to one primary Nutshell Company with contact roles on related deals. During migration we match the company name and address fields to avoid duplicates, and we preserve the primary contact's role on each deal for future reference.

Assured JobCheck

Lead

maps to

Nutshell

Lead

1:1
Fully supported

Prospective clients and referrals captured in Assured JobCheck's Salesforce Lead object migrate to Nutshell Leads. Lead status pick-list values map value‑by‑value to Nutshell's lead‑status taxonomy. Unconverted Salesforce Leads from before the migration date land as Nutshell Leads. We also preserve the original lead source and any custom fields so that your sales team can continue nurturing them without re‑entering data.

Assured JobCheck

Job__c

maps to

Nutshell

Deal

1:1
Fully supported

Each Assured JobCheck job record (Job__c) becomes a Nutshell Deal. Job name maps to Deal name. Job status pick-list values (e.g., 'Site Inspection Scheduled', 'Contents Listed', 'Work In Progress', 'Closed') map to Nutshell pipeline stage values. The job's estimated amount or insurance estimate maps to Deal value. Nutshell's single pipeline per account model means multi-property jobs under one account may split into separate Deals.

Assured JobCheck

Job__c.task_assignments

maps to

Nutshell

Task

1:1
Fully supported

Assured JobCheck task records (Task__c) associated with a Job__c migrate as Nutshell Tasks. The task subject becomes the Task name. Assigned-to resolves by email to Nutshell user. Due date and status map directly. Tasks that were marked complete in Assured JobCheck carry a completed status into Nutshell. Tasks without a due date receive a default date flagged for review.

Assured JobCheck

ContentDocument (Photos)

maps to

Nutshell

File attachment on Deal

1:1
Fully supported

Assured JobCheck photo folders (Salesforce ContentDocument linked to Job__c) download from Salesforce and re-upload as file attachments on the corresponding Nutshell Deal. Photo folder names become descriptive labels. Nutshell's 25MB per-file limit applies — large photo files may need compression. Inline photos embedded in notes extract and re-attach separately.

Assured JobCheck

PackOut_Item__c (Inventory)

maps to

Nutshell

Note or Line Item on Deal

1:many
Fully supported

Assured PackOut barcode-tagged inventory items (PackOut_Item__c custom object) split across two Nutshell targets: item name, room, condition grade, and replacement estimate migrate as line items on the Nutshell Deal. Item-level photos migrate as file attachments on the Deal. Barcode tag IDs preserve as a custom text field on the note for traceability.

Assured JobCheck

Insurance_Claim__c

maps to

Nutshell

Custom field on Deal

1:1
Fully supported

Assured JobCheck's insurance claim reference object (claim number, adjuster name, carrier, policy number) has no native Nutshell equivalent. Migrates as a custom field group on the Deal record — Insurance_Claim_Number__c, Adjuster_Name__c, Insurance_Carrier__c, Policy_Number__c. Your Nutshell admin pre-creates these custom fields before migration.

Assured JobCheck

Job_Feeds__c (Activity Log)

maps to

Nutshell

Activity on Deal

1:1
Fully supported

Assured JobCheck's real‑time team feed entries (comments, status‑change log entries) migrate as Nutshell Activities on the related Deal. Original timestamp and posting user resolve by email match. Feed entries without a linked Deal attach to the primary Person record. Each activity retains the full comment text, and any @mentions are preserved as plain text for future reference.

Assured JobCheck

User / Owner

maps to

Nutshell

User

1:1
Fully supported

Assured JobCheck's Salesforce users (estimators, project managers, crew leads) resolve against Nutshell users by email address. Active users with matching emails get their records assigned automatically. Users without a Nutshell counterpart are flagged — your team either creates the Nutshell user first or assigns their records to a fallback owner before the migration runs.

Assured JobCheck

Custom Field (Job__c)

maps to

Nutshell

Custom Field on Deal

1:1
Fully supported

Assured JobCheck's custom fields on Job__c (e.g., loss_type__c, room_count__c, water_class__c) require pre-created custom fields in Nutshell on the Deal object. Field type mapping: pick-list → dropdown, number → number, currency → currency, date → date. Text fields map directly. We deliver a custom-field creation checklist as part of the migration plan.

Assured JobCheck

Assured JobCheck Workflow

maps to

Nutshell

No equivalent

1:1
Fully supported

Assured JobCheck's custom workflow engine (automated job-stage transitions, task assignment rules, notification triggers) has no native equivalent in Nutshell. We export workflow definitions as a structured JSON reference. Rebuild using Nutshell's sales email sequences and task automation tools. Workflow rebuild is outside migration scope.

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.

Assured JobCheck logo

Assured JobCheck gotchas

Medium

PackOut contents data is tightly coupled to JobCheck

Medium

Restoration-specific custom fields lack standard equivalents

High

Salesforce org edition may gate API access

Low

Job workflows and automation rules are not data records

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

  • Multi-object job structure flattens into a single Nutshell Deal

    Assured JobCheck stores jobs as parent Salesforce records (Job__c) with child task assignments (Task__c), photo folders (ContentDocumentLink), and PackOut inventory items (PackOut_Item__c) — a deeply nested structure. Nutshell Deals are flat records with tasks, notes, and file attachments as related sub-records. We preserve the relationship by attaching all child tasks, notes, and files to the migrated Deal, but the job's internal folder hierarchy (e.g., 'Pre-Existing Damage Photos' vs. 'Claim Related Damage Photos') collapses into a flat file list on the Nutshell Deal. Photo-folder organization must be rebuilt manually in Nutshell or encoded into file naming conventions.

  • Assured JobCheck custom fields require pre-created Nutshell custom fields

    Assured JobCheck extends the Salesforce Job__c object with custom fields (loss_type__c, water_class__c, room_count__c, insurance_carrier__c, etc.) that have no native Nutshell equivalent. Nutshell supports custom fields per entity, but they must be created manually in Nutshell before migration — Nutshell's API can then populate them during the import. We deliver a custom-field creation checklist specifying field name, type, and pick-list values that your Nutshell admin creates in advance. Fields not pre-created land in a catch-all 'source_data__c' text field for post-migration cleanup.

  • PackOut inventory item volume can triple migration record counts

    Restoration jobs with extensive PackOut inventories — hundreds of tagged items across multiple rooms — generate a PackOut_Item__c record per item. Each item becomes a Nutshell Note with custom fields, multiplying the total record count significantly. A single large job with 800 PackOut items generates 800 additional Note records on top of the base Deal, Contact, Company, and Task records. This affects both migration pricing and Nutshell's per-record storage calculations. We surface the PackOut item count during scoping and separate it from the core CRM record count.

  • Nutshell has no workflow engine for job-stage automation

    Assured JobCheck's custom workflow engine automatically advances job stages (e.g., Site Inspection → Contents Listed → Work In Progress → Closed) based on trigger conditions and sends task notifications to assigned crew members. Nutshell's automation is limited to sales email sequences and task creation triggers — there is no job-status workflow engine. The migration cannot replicate Assured JobCheck's workflow logic in Nutshell. We export the workflow definitions as a structured JSON reference so your Nutshell admin can manually configure equivalent email sequences and task rules, but any automatic stage progression logic must be rebuilt or handled manually.

  • Salesforce API rate limits apply to Assured JobCheck export

    Assured JobCheck runs on the Salesforce platform, so all source data is extracted via the Salesforce REST API. Salesforce API calls are subject to daily limits that vary by org license type. Large Assured JobCheck instances with extensive historical job data (multiple years of records, thousands of ContentDocument versions) may encounter API governor limits during the extraction phase. We mitigate this by using Salesforce Bulk API 2.0 for large object exports and staging incremental batch retrievals. If your org has already consumed significant API capacity, extraction may need to run outside business hours.

Migration approach

Six steps for a successful Assured JobCheck to Nutshell data migration

  1. Extract source data via Salesforce Bulk API 2.0

    FlitStack AI authenticates to Assured JobCheck via a Salesforce connected app using OAuth 2.0 client credentials. We query Job__c, Task__c, Contact, Account, Lead, ContentDocument, ContentVersion, and PackOut_Item__c using Bulk API 2.0 for large objects to stay within Salesforce API governor limits. Custom field metadata (field labels, types, pick-list values) is retrieved via the Salesforce Tooling API to build the field mapping plan. All records export with their original CreatedDate, LastModifiedDate, and owner ID for timestamp preservation and owner resolution.

  2. Build Nutshell custom fields before migration

    Before data lands in Nutshell, your admin creates the custom fields we identified during scoping — loss_type__c dropdown, insurance_claim_number__c text, adjuster_name__c text, room_count__c number, and any PackOut-related custom fields on Notes. We deliver a field creation checklist with exact Nutshell field names, types, and pick-list options. This step must complete before the test migration runs so field-level validation can confirm data lands in the right places.

  3. Resolve owners and users by email match

    Salesforce owner IDs from Assured JobCheck resolve against Nutshell users by email address. Active users with matching emails get records assigned automatically. Users without a Nutshell counterpart are flagged in a pre-migration owner report — your team either creates the Nutshell user first or designates a fallback owner. No record migrates without a resolved owner. Nutshell's API requires an owning user for every Deal, Person, Company, and Lead record.

  4. Run sample migration with field-level diff

    A representative slice migrates first — typically 100–300 records spanning contacts, companies, deals (jobs), tasks, and a sample of PackOut items with photos. We generate a field-level diff showing every mapped value, any transformation applied, and any record that failed to migrate. You review the diff in Nutshell against the source Assured JobCheck records. This step validates job-stage mapping, custom field population, and owner resolution before the full run commits.

  5. Execute full migration with delta-pickup window

    The full migration runs against Nutshell's API, processing all records in dependency order: Companies first (required for Person linking), then Persons, then Leads, then Deals (jobs) with tasks and file attachments, then PackOut items as Notes. A delta-pickup window (typically 24–48 hours) captures any records created or modified in Assured JobCheck during the cutover. Audit log captures every API operation. One-click rollback is available if reconciliation against the pre-migration record count fails.

Platform deep dives

Context on both ends of the pair

Assured JobCheck logo

Assured JobCheck

Source

Strengths

  • Salesforce foundation delivers enterprise reliability, SOC 2 compliance, and global data centers with no customer-managed infrastructure.
  • PackOut iPad app provides field-first contents listing with barcode scanning, automatic room organization, and photo attachment in a standardized workflow.
  • Real-time Job Feed and mobile notifications keep field crews and office staff synchronized without relying on phone calls or email.
  • Unlimited jobs and uploads on all plans means restoration companies do not hit arbitrary limits during peak claim seasons.
  • CRM capabilities built in let restoration companies track insurer relationships, adjuster contacts, and referral sources alongside job records.

Weaknesses

  • No publicly documented API rate limits, endpoints, or developer documentation makes third-party integrations and data extraction opaque.
  • Restoration-industry specificity means exported data requires significant field mapping when moving to horizontal project management tools.
  • Small market presence and limited independent reviews make competitive evaluation against Jobber, Buildertrend, or Encircle difficult.
  • Pricing beyond the $35 entry tier is not publicly published, introducing risk of unexpected costs for growing restoration franchises.
  • Assured PackOut is a separate iPad purchase and integration, meaning contents data may reside in a partially coupled system that complicates single-pass migration.
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. 1 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 Assured JobCheck and Nutshell.

  • Object compatibility

    B

    1 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

    Assured JobCheck: Not publicly documented — Salesforce API limits vary by org edition and license type.

  • Data volume sensitivity

    A

    Assured JobCheck exposes a bulk API — large-volume migrations stream efficiently.

Estimator

Estimate your Assured JobCheck 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 Assured JobCheck to Nutshell data migrations

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

Can't find your answer?

Walk through your Assured JobCheck to Nutshell migration with a real engineer — 30 minutes, free, written quote within 24 hours.

Book a free 30 minute consultation

Most Assured JobCheck to Nutshell migrations complete in 48–72 hours of clock time for under 25,000 records. Larger setups with 200,000+ records or heavy PackOut inventory (thousands of tagged items) extend to 5–8 days. The longest planning step is creating Nutshell custom fields to match Assured JobCheck's Salesforce schema before the migration runs. We recommend completing custom field creation during scoping so it does not block the test migration.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Assured JobCheck.
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