CRM migration
Field-level mapping, validation, and rollback between Jobsite Mobile and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Jobsite Mobile
Source
Nutshell
Destination
Compatibility
12 of 12
objects map 1:1 between Jobsite Mobile and Nutshell.
Complexity
BStandard
Timeline
24–72 hours
Overview
Jobsite Mobile is built around job-site operations — work orders, field-worker scheduling, equipment tracking, and site-level project management are its core objects. Nutshell is a traditional sales CRM organized around People, Companies, Leads, and Deals with pipeline-stage tracking and activity logging. The migration carries Jobsite Mobile's contact records, company records, project-linked deal records, tasks, and notes into Nutshell's equivalent objects, while custom fields on People and Companies are recreated in Nutshell's field editor before data lands. Jobsite Mobile workflows, field-worker schedules, equipment records, and site-level configurations have no Nutshell equivalent and cannot migrate — FlitStack AI exports workflow definitions as a PDF reference for your team to rebuild in Nutshell's automation tools. The migration runs via Jobsite Mobile's export API and Nutshell's JSON-RPC API, sequenced so foreign keys (company on a person, deal on a company) resolve in the correct order. A 24–48-hour delta-pickup window captures any records modified during the cutover window so Nutshell reflects Jobsite Mobile's final state at go-live.
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 Jobsite Mobile 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.
Jobsite Mobile
Person / Contact
Nutshell
Person
1:1Jobsite Mobile person records map 1:1 to Nutshell People. The person's name, email, phone, and address fields transfer directly. Custom fields on the person record (trade certification, site assignment) migrate to Nutshell custom fields created before migration. The Jobsite Mobile contact ID is preserved as a string custom field for traceability.
Jobsite Mobile
Company / Account
Nutshell
Company
1:1Jobsite Mobile company records map to Nutshell Companies. Company name, address, industry, website, employee count, and annual revenue transfer directly. Jobsite Mobile's company-level custom fields (client tier, contract status) migrate as Nutshell custom fields on the Company object. Parent-company hierarchies are preserved as a custom parent-company text field since Nutshell does not have a native company hierarchy object.
Jobsite Mobile
Job / Work Order
Nutshell
Deal
1:1Jobsite Mobile jobs represent billable work at a site. Each open or completed job migrates as a Nutshell Deal. The job name becomes the Deal name, the estimated value or billed amount becomes the Deal value, and the job status (open, completed, invoiced) maps to a Nutshell pipeline stage. Job-level custom fields (work order type, trade category, site location) transfer as Deal-level custom fields if the target Nutshell plan supports them; otherwise they are appended to the Deal description field.
Jobsite Mobile
Job Status / Stage
Nutshell
Pipeline Stage
1:1Jobsite Mobile job statuses (Quoted, In Progress, On Hold, Completed, Invoiced, Cancelled) map value-by-value to Nutshell pipeline stages. We match status labels to Nutshell stage names during the mapping phase; if a Nutshell pipeline does not exist yet, FlitStack creates one with stages aligned to the source statuses before data loads.
Jobsite Mobile
Worker / Technician
Nutshell
User (Owner)
1:1Jobsite Mobile worker records represent the people assigned to jobs, not CRM owners. Each worker with an email address is matched by email to a Nutshell User — that Nutshell user becomes the Owner of the Deals and People that were assigned to the worker in Jobsite Mobile. Workers without an email are flagged and assigned to a fallback Nutshell user or left unassigned pending team configuration.
Jobsite Mobile
Task / To-Do
Nutshell
Task
1:1Jobsite Mobile tasks linked to jobs or people migrate as Nutshell Tasks attached to the corresponding Person or Deal. Task name, due date, completion status, and owner transfer directly. Completed-on date maps to the Nutshell task's completed timestamp field. Assignee resolution uses email matching to link the task to a Nutshell User; tasks with unmatched assignees are flagged in the pre-migration report for manual owner assignment before migration runs.
Jobsite Mobile
Note / Site Note
Nutshell
Note
1:1Notes attached to Jobsite Mobile people or jobs migrate as Nutshell Notes. Rich-text formatting in Jobsite Mobile notes is preserved as plain text in Nutshell Notes. Inline images referenced in site notes are downloaded and re-attached as file uploads to the Nutshell record.
Jobsite Mobile
Attachment / File
Nutshell
File
1:1Jobsite Mobile file attachments on jobs or people are downloaded and re-uploaded to the corresponding Nutshell Person or Deal record. File size limits are respected (Nutshell's standard per-file limit applies); files exceeding the limit are flagged for manual retrieval or alternative storage.
Jobsite Mobile
Custom Field (Person)
Nutshell
Custom Field (Person)
1:1Any Jobsite Mobile custom field on a person record (e.g., trade certification, client rating, safety training status) requires a corresponding custom field to be created in Nutshell's field editor under People before migration. FlitStack delivers a custom field creation plan specifying the field name, type (text, pick-list, date, number), and any value-mapping required for pick-list fields.
Jobsite Mobile
Custom Field (Company)
Nutshell
Custom Field (Company)
1:1Jobsite Mobile company-level custom fields (e.g., client tier, contract expiry date, preferred trade categories) are created as Nutshell Company custom fields before migration. FlitStack maps each field's type and validates pick-list values against Nutshell's allowed values for choice-type fields. If a pick-list value has no matching Nutshell option, FlitStack flags it for review and either creates a new Nutshell choice or maps to an existing close-match value.
Jobsite Mobile
Workflow / Automation Rule
Nutshell
No Equivalent
1:1Jobsite Mobile workflows — dispatch automations, job-status triggers, worker notifications, and approval chains — exist only within Jobsite Mobile's field-service engine and have no Nutshell equivalent. FlitStack exports workflow definitions as a structured PDF and JSON reference file so your team can recreate logic in Nutshell's automation rules (Pro and above) or in an external automation tool.
Jobsite Mobile
Equipment Record
Nutshell
No Equivalent
1:1Jobsite Mobile equipment records track tools, vehicles, and assets assigned to jobs or workers. Nutshell has no native asset or equipment object. Equipment records can be preserved as a custom object in Nutshell Enterprise, or exported as a CSV reference file — FlitStack identifies which option applies based on your Nutshell plan.
| Jobsite Mobile | Nutshell | Compatibility | |
|---|---|---|---|
| Person / Contact | Person1:1 | Fully supported | |
| Company / Account | Company1:1 | Fully supported | |
| Job / Work Order | Deal1:1 | Fully supported | |
| Job Status / Stage | Pipeline Stage1:1 | Fully supported | |
| Worker / Technician | User (Owner)1:1 | Fully supported | |
| Task / To-Do | Task1:1 | Fully supported | |
| Note / Site Note | Note1:1 | Fully supported | |
| Attachment / File | File1:1 | Fully supported | |
| Custom Field (Person) | Custom Field (Person)1:1 | Fully supported | |
| Custom Field (Company) | Custom Field (Company)1:1 | Fully supported | |
| Workflow / Automation Rule | No Equivalent1:1 | Fully supported | |
| Equipment Record | 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.
Jobsite Mobile gotchas
No documented public API for bulk data export
Per-user licensing inflates cost for large or seasonal crews
Custom fields limited to 100 per Work Order object
Historical Work Orders become read-only after 90 days
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
Pre-flight: export data model audit and field creation
FlitStack connects to Jobsite Mobile via API and extracts the full data model — object list, field list, pick-list values, and workflow definitions. We cross-reference this against Nutshell's API to identify missing objects, unsupported field types, and value-mismatch points. For every Jobsite Mobile custom field that has no Nutshell equivalent on the same object, we deliver a custom field creation plan specifying the field name, Nutshell field type, and any pick-list value mapping required. Your Nutshell admin creates the fields before we proceed. We also create the target Nutshell pipeline with stages matching Jobsite Mobile job statuses at this stage.
Owner resolution and user matching
We pull the full user and worker list from Jobsite Mobile and match each record against Nutshell Users by email address. Workers with a matching Nutshell user become the owner of their assigned Deals and People in Nutshell. Workers without a Nutshell email are flagged in a pre-migration report with two resolution options: invite the worker to Nutshell first, or assign their records to a fallback Nutshell user. No record is migrated without a resolved owner or a documented fallback decision.
Migrate companies and people before deals
Nutshell requires Company records to exist before a Person can link to one via the company_id lookup. Similarly, Deals must reference a Company to attach cleanly to the Nutshell data model. We sequence the migration so Companies load first, then People with their company lookups, then Deals with their company lookups and owner assignments, then Tasks and Notes. This ordering prevents foreign-key resolution failures that would otherwise require a second pass to backfill missing links.
Sample migration run with field-level diff
Before committing the full dataset, FlitStack runs a sample migration using a representative slice — typically 100–500 records spanning People, Companies, Deals, and Tasks across multiple job statuses and owner assignments. We generate a field-level diff showing every source field value, the mapped destination field, and any transformation applied. You review the diff to verify that job-status to pipeline-stage mapping is correct, custom field values transferred as expected, and owner resolution worked for flagged workers. No full run commits until you approve the sample.
Full migration run with delta-pickup window
FlitStack executes the full migration against your Nutshell account. A delta-pickup window of 24–48 hours after the full run captures any records created or modified in Jobsite Mobile during the cutover. Every operation is logged in an audit trail. One-click rollback is available if reconciliation fails — the rollback reverts Nutshell to its pre-migration state so the team can investigate and re-run without data loss. After the delta window closes and reconciliation passes, your team is free to begin using Nutshell.
Platform deep dives
Jobsite Mobile
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 Jobsite Mobile 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
Jobsite Mobile: Not applicable..
Data volume sensitivity
Jobsite Mobile 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 Jobsite Mobile to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your Jobsite Mobile 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 Jobsite Mobile
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.