CRM migration
Field-level mapping, validation, and rollback between Assured JobCheck and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Assured JobCheck
Source
Nutshell
Destination
Compatibility
11 of 12
objects map 1:1 between Assured JobCheck and Nutshell.
Complexity
BStandard
Timeline
48–72 hours
Overview
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.
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 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)
Nutshell
Person
1:1Assured 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)
Nutshell
Company
1:1Assured 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
Nutshell
Lead
1:1Prospective 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
Nutshell
Deal
1:1Each 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
Nutshell
Task
1:1Assured 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)
Nutshell
File attachment on Deal
1:1Assured 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)
Nutshell
Note or Line Item on Deal
1:manyAssured 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
Nutshell
Custom field on Deal
1:1Assured 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)
Nutshell
Activity on Deal
1:1Assured 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
Nutshell
User
1:1Assured 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)
Nutshell
Custom Field on Deal
1:1Assured 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
Nutshell
No equivalent
1:1Assured 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.
| Assured JobCheck | Nutshell | Compatibility | |
|---|---|---|---|
| Contact (Person) | Person1:1 | Fully supported | |
| Company (Account) | Company1:1 | Fully supported | |
| Lead | Lead1:1 | Fully supported | |
| Job__c | Deal1:1 | Fully supported | |
| Job__c.task_assignments | Task1:1 | Fully supported | |
| ContentDocument (Photos) | File attachment on Deal1:1 | Fully supported | |
| PackOut_Item__c (Inventory) | Note or Line Item on Deal1:many | Fully supported | |
| Insurance_Claim__c | Custom field on Deal1:1 | Fully supported | |
| Job_Feeds__c (Activity Log) | Activity on Deal1:1 | Fully supported | |
| User / Owner | User1:1 | Fully supported | |
| Custom Field (Job__c) | Custom Field on Deal1:1 | Fully supported | |
| Assured JobCheck Workflow | 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.
Assured JobCheck gotchas
PackOut contents data is tightly coupled to JobCheck
Restoration-specific custom fields lack standard equivalents
Salesforce org edition may gate API access
Job workflows and automation rules are not data records
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
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.
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.
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.
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.
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
Assured JobCheck
Source
Strengths
Weaknesses
Nutshell
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 1 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 Assured JobCheck and Nutshell.
Object compatibility
1 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
Assured JobCheck: Not publicly documented — Salesforce API limits vary by org edition and license type.
Data volume sensitivity
Assured JobCheck exposes a bulk API — large-volume migrations stream efficiently.
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 Assured JobCheck to Nutshell migration scoping. Not seeing yours? Book a call.
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 consultationAdjacent paths
Other ways to leave Assured JobCheck
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.