CRM migration

Migrate from Jobsite Mobile to Nutshell

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

Jobsite Mobile logo

Jobsite Mobile

Source

Nutshell

Destination

Nutshell logo

Compatibility

100%

12 of 12

objects map 1:1 between Jobsite Mobile and Nutshell.

Complexity

BStandard

Timeline

24–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

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

Jobsite Mobile logo

Jobsite Mobile

What's pushing teams away

  • Per-user pricing scales poorly for large field teams — companies with many part-time or seasonal technicians report being priced out as headcount grows.
  • The platform lacks a public API documentation or developer portal, making integrations with accounting software or custom dashboards difficult to maintain.
  • Reporting capabilities are limited to basic summaries; advanced analytics, custom dashboards, and data exports require workarounds or third-party add-ons.
  • Some users report that the web interface is significantly slower than the mobile app, making office-side administration cumbersome.

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 Jobsite Mobile objects map to Nutshell

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

maps to

Nutshell

Person

1:1
Fully supported

Jobsite 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

maps to

Nutshell

Company

1:1
Fully supported

Jobsite 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

maps to

Nutshell

Deal

1:1
Fully supported

Jobsite 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

maps to

Nutshell

Pipeline Stage

1:1
Fully supported

Jobsite 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

maps to

Nutshell

User (Owner)

1:1
Fully supported

Jobsite 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

maps to

Nutshell

Task

1:1
Fully supported

Jobsite 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

maps to

Nutshell

Note

1:1
Fully supported

Notes 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

maps to

Nutshell

File

1:1
Fully supported

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

maps to

Nutshell

Custom Field (Person)

1:1
Fully supported

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

maps to

Nutshell

Custom Field (Company)

1:1
Fully supported

Jobsite 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

maps to

Nutshell

No Equivalent

1:1
Fully supported

Jobsite 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

maps to

Nutshell

No Equivalent

1:1
Fully supported

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

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.

Jobsite Mobile logo

Jobsite Mobile gotchas

High

No documented public API for bulk data export

Medium

Per-user licensing inflates cost for large or seasonal crews

Medium

Custom fields limited to 100 per Work Order object

Low

Historical Work Orders become read-only after 90 days

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

  • Custom fields on Deals are not supported in Nutshell's standard schema

    Nutshell allows custom fields on Companies, People, and Leads, but Deal-level custom fields are not available in Nutshell's standard object model. Jobsite Mobile jobs frequently carry site-level metadata in custom fields — trade category, work order type, permit number, inspection status. When this metadata lands in Nutshell, it cannot map to a Deal custom field. FlitStack surfaces every job-level custom field during scoping and either creates a Nutshell custom field under the associated Company or Person record, or appends the metadata to the Deal's description field as structured text. Your team chooses the approach before migration runs.

  • Jobsite Mobile workflows and dispatch automations have no Nutshell equivalent

    Jobsite Mobile workflows trigger field dispatch, job-status notifications, worker assignment rules, and approval chains based on job data. Nutshell's automation engine handles lead routing and email sequences tied to People and Deals, but it does not replicate Jobsite Mobile's field-dispatch logic. Any automation that routes work to field workers or triggers based on job-site conditions cannot migrate. FlitStack exports every active Jobsite Mobile workflow definition as a structured JSON and PDF document so your team has a rebuild reference for Nutshell's automation rules or a dedicated field-service tool.

  • Multi-site person-to-company associations collapse to a single primary company

    Jobsite Mobile allows a single contact to be associated with multiple job sites, each potentially linked to a different company entity. Nutshell Person records link to one primary Company record. A person with three site associations in Jobsite Mobile must choose one primary company in Nutshell. FlitStack identifies multi-company person records during the scoping scan, flags them in the migration plan, and migrates the most recently active site association as the primary company — secondary associations are preserved as a custom multi-value text field on the Nutshell Person record.

  • Equipment and asset records have no native destination object

    Jobsite Mobile maintains equipment records — vehicles, tools, and assets assigned to jobs or workers — as first-class objects with service history and assignment tracking. Nutshell has no native asset or equipment object. Equipment records cannot migrate as structured records into a non-existent object. FlitStack exports the full equipment roster as a CSV file and, for Nutshell Enterprise plans, can create a custom object to house equipment records with a lookup to the associated Deal or Company. Teams on Foundation or Pro plans receive the CSV export as a reference file for downstream inventory management.

  • Job-stage to pipeline-stage value mapping requires manual definition before migration

    Nutshell's pipeline stages are defined per pipeline and scoped to that pipeline's stage pick-list. Jobsite Mobile job statuses (Quoted, In Progress, On Hold, Completed, Invoiced, Cancelled) must map to specific Nutshell stage names that exist in your target pipeline. If your Nutshell account does not yet have a pipeline with matching stage names, the migration cannot resolve stage IDs at runtime. FlitStack creates the target pipeline with matching stage definitions during the pre-flight setup step before any data loads, ensuring the value mapping resolves cleanly during the migration run.

Migration approach

Six steps for a successful Jobsite Mobile to Nutshell data migration

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

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

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

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

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

Context on both ends of the pair

Jobsite Mobile logo

Jobsite Mobile

Source

Strengths

  • Native Android and iOS apps with offline mode for connectivity-challenged job sites.
  • Integrated scheduling, dispatch board, and customer management in one platform.
  • 24/7 phone and live chat support available on all tiers.
  • Time entry capture from the mobile app links directly to work orders.
  • Knowledge base, webinars, and documentation for onboarding new technicians.

Weaknesses

  • No publicly documented API or developer portal, limiting programmatic data access.
  • Per-user pricing model inflates costs for large or seasonal workforces.
  • Reporting is basic; no native export to BI tools or custom analytics.
  • Attachment storage is not accessible via a standard API export endpoint.
  • Web interface performance lags behind the mobile app experience.
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 Jobsite Mobile 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

    Jobsite Mobile: Not applicable..

  • Data volume sensitivity

    B

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

Estimator

Estimate your Jobsite Mobile 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 Jobsite Mobile to Nutshell data migrations

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

Can't find your answer?

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 consultation

Most Jobsite Mobile to Nutshell migrations complete in 24–72 hours of clock time for datasets under 25,000 records. Setup complexity is the main variable — if Jobsite Mobile has more than 20 custom fields, each requiring a separate Nutshell field creation step, the pre-flight phase extends to 2–3 days before migration runs. Datasets over 100,000 records or setups with complex multi-company person associations extend to 5–10 days. The delta-pickup window (24–48 hours) runs concurrently with the final cutover decision.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Jobsite Mobile.
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