CRM migration

Migrate from Salesforce Field Service to Nutshell

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

Salesforce Field Service logo

Salesforce Field Service

Source

Nutshell

Destination

Nutshell logo

Compatibility

100%

15 of 15

objects map 1:1 between Salesforce Field Service and Nutshell.

Complexity

BStandard

Timeline

48–96 hours of clock time

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Salesforce Field Service extends Salesforce's standard CRM with field-service-specific objects — WorkOrder, WorkOrderLineItem, ServiceAppointment, Skill, and Asset — that have no structural equivalent in Nutshell's People, Companies, Leads, Deals, Activities, and Tasks object model. FlitStack AI migrates every standard CRM object (Account, Contact, Lead, Opportunity) plus any custom fields on those objects, with Salesforce custom fields (which carry the __c suffix) imported as Nutshell custom fields per-object. Work Order headers and line items are migrated as structured custom fields on the parent Account or Contact, with original timestamps preserved as read-only reference fields so your team retains service history even without native scheduling tools. Nutshell's own migration import tool explicitly excludes Salesforce Files and attachments; we handle those by re-hosting linked files to Nutshell's attachment storage. The migration runs via Salesforce Bulk API for large record sets and REST API for real-time delta captures. All automations, flows, and assignment rules stay behind — we export your Flow definitions as a JSON reference package for your Nutshell admin to rebuild manually. Owner resolution happens by email match against Nutshell users before any records are written, so every record lands with a valid owner from day one.

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

Salesforce Field Service logo

Salesforce Field Service

What's pushing teams away

  • Pricing model accumulates hidden costs—storage overages at $125/GB, API throttling during high-volume periods, and $2 per Agentforce conversation add up beyond the base seat license.
  • Complexity of inherited implementations makes configuration tangles difficult to unwind, and lack of clear documentation makes it hard for new teams to understand what the system is actually doing.
  • Scheduling limits create friction at scale—250 records per Enhanced Scheduling optimization batch is insufficient for large service operations without additional tooling.
  • Integration depth becomes a dependency trap—organizations deeply embedded in Salesforce Field Service find switching costs prohibitively high even when frustrated with cost or complexity.

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 Salesforce Field Service objects map to Nutshell

Each row shows how a Salesforce Field Service 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.

Salesforce Field Service

Account

maps to

Nutshell

Company

1:1
Fully supported

Salesforce Account maps directly to Nutshell Company with all standard fields transferring cleanly. Account.Name populates the Company name field directly. Parent Account hierarchy relationships map to Nutshell's parent-company field for maintaining corporate structures. Multi-address accounts require consolidation — the primary address becomes the standard Company address in Nutshell, while secondary and shipping addresses are preserved as custom fields to retain all location data from the source system.

Salesforce Field Service

Contact

maps to

Nutshell

Person

1:1
Fully supported

Salesforce Contact maps to Nutshell Person with all standard Contact fields transferring directly including Name, Email, Phone, and Title. Contacts that lack an AccountId association in Salesforce are assigned to a designated placeholder Company in Nutshell to maintain referential integrity and prevent orphaned person records in the destination system.

Salesforce Field Service

Lead

maps to

Nutshell

Lead

1:1
Fully supported

Salesforce Lead maps to Nutshell Lead with direct field correspondence for Name, Company, Email, Phone, and Status. Lead source pick-list values require value-by-value mapping against Nutshell's available lead source options — custom source values are recreated as Nutshell custom fields.

Salesforce Field Service

Opportunity

maps to

Nutshell

Deal

1:1
Fully supported

Salesforce Opportunity maps to Nutshell Deal with Opportunity fields such as Name, Amount, CloseDate, and StageName corresponding to their Deal equivalents. Salesforce Opportunity StageName pick-list values map to Nutshell pipeline stage names via a comprehensive value-mapping table delivered as part of the migration plan documentation and validated during the sample migration phase.

Salesforce Field Service

WorkOrder

maps to

Nutshell

Company (custom fields)

1:1
Fully supported

Salesforce WorkOrder has no direct Nutshell equivalent, requiring a transformation approach. We flatten WorkOrder header fields including Status, Priority, Subject, Description, ScheduledStart, ScheduledEnd, and ActualDuration into structured custom fields on the parent Nutshell Company record. The original WorkOrderId is preserved as a read-only reference field for traceability and future audit purposes.

Salesforce Field Service

WorkOrderLineItem

maps to

Nutshell

Company (custom fields)

1:1
Fully supported

WorkOrderLineItem records are migrated as child custom-field rows on the parent Nutshell Company, keyed by the parent WorkOrder. Each line item's description, quantity, unit price, and line-status migrate as repeating custom-field groups — your Nutshell admin defines the exact field names in the schema plan before migration.

Salesforce Field Service

ServiceAppointment

maps to

Nutshell

Activity (custom fields)

1:1
Fully supported

Salesforce ServiceAppointment maps to Nutshell Activities with appointment-specific fields such as SchedStartTime, SchedEndTime, ActualStart, ActualEnd, Status, and TravelTime stored as Nutshell custom fields on the linked Person or Company record. Nutshell's standard Activity subject and description fields carry the appointment summary and primary details for quick reference.

Salesforce Field Service

Asset

maps to

Nutshell

Company (custom fields)

1:1
Fully supported

Salesforce Asset tracks installed products associated with each Account. Asset records migrate as structured custom fields on the corresponding Nutshell Company including Name, SerialNumber, Status, InstallDate, and Product2 reference fields mapped individually. When multiple assets exist per company, they become repeating custom-field groups with indexed naming conventions.

Salesforce Field Service

Skill

maps to

Nutshell

Person (custom fields)

1:1
Fully supported

Salesforce Skill records representing field service certifications map to Nutshell Person custom fields. Each Skill Name and ProficiencyLevel migrates as a text or pick-list custom field on the Person record — your team defines the exact labels during schema setup so the naming convention aligns with your internal taxonomy.

Salesforce Field Service

Product2

maps to

Nutshell

Company (custom fields)

1:1
Fully supported

Salesforce Product2 records representing service parts and products have no native Nutshell equivalent. Product names and codes migrate as read-only custom fields on a designated 'Products' placeholder Company record, preserving the complete product catalog for reference purposes without requiring a full product management module in the destination system.

Salesforce Field Service

Task

maps to

Nutshell

Task

1:1
Fully supported

Salesforce Task maps directly to Nutshell Task with Subject, Status, Priority, ActivityDate, and Description transferring cleanly. Tasks originally linked to a Salesforce Contact or Lead re-link to the corresponding Nutshell Person or Lead record via email-matched owner resolution and Salesforce record ID cross-references maintained throughout the migration.

Salesforce Field Service

Event

maps to

Nutshell

Activity

1:1
Fully supported

Salesforce Event maps to Nutshell Activity with StartDateTime, EndDateTime, Subject, and Description carrying over directly. All-day events are flagged using Nutshell's all-day activity indicator. Event attendees resolve to Nutshell Person records through email address matching to maintain attendee relationships in the destination platform.

Salesforce Field Service

Note

maps to

Nutshell

Note

1:1
Fully supported

Salesforce Notes using the legacy Note object migrate to Nutshell Notes with Note Title becoming the Note subject and Body carrying the full note content. Notes originally attached to Salesforce Contacts resolve to their corresponding Nutshell Person record through owner email matching and record ID cross-references during the migration process.

Salesforce Field Service

Custom Object (__c)

maps to

Nutshell

Custom Field (per object)

1:1
Fully supported

Every Salesforce custom object bearing the __c suffix undergoes review during discovery. Standard-object custom fields such as Account.Custom_Field__c become Nutshell custom fields on their corresponding object. Full custom objects require a custom migration plan — many collapse into structured custom fields on the parent object rather than existing as standalone entities in the destination system.

Salesforce Field Service

Entitlement

maps to

Nutshell

Company (custom fields)

1:1
Fully supported

Salesforce Entitlement records representing service contract terms migrate as structured custom fields on the associated Nutshell Company. Entitlement fields including Name, Status, StartDate, EndDate, and SlaProcess reference are mapped individually. The active or entitled status is encoded as a boolean custom field for straightforward reporting on contract standing in the destination system.

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.

Salesforce Field Service logo

Salesforce Field Service gotchas

High

250-record batch limit for Enhanced Scheduling optimization

High

Process Builder workflows do not migrate—must be rebuilt in Flow Builder

High

API rate limits vary by edition and are easy to exhaust during bulk migration

Medium

Storage overages at $125/GB inflate migration data costs

Medium

Custom fields and lookups require explicit field-level mapping

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

  • WorkOrder and ServiceAppointment have no Nutshell equivalent — service history must be flattened

    Salesforce Field Service is built around WorkOrder, WorkOrderLineItem, ServiceAppointment, and Skill objects that have no structural counterpart in Nutshell's CRM object model. Migrating these records requires flattening them into structured custom fields on Nutshell's Company and Person objects. Each WorkOrder becomes a set of custom fields (subject, status, priority, scheduled dates) on the linked Company record; each ServiceAppointment maps to an Activity with custom fields for appointment windows. This preserves the data but your Nutshell team will interact with service history through custom fields rather than native work-order screens. We deliver a schema plan before migration so your admin can name and organise these fields logically.

  • Nutshell's built-in Salesforce import excludes Files and attachments — they must be re-hosted

    Nutshell's own Salesforce migration import tool explicitly instructs users not to include Salesforce Files, CRM Content documents, or Chatter files in the export. The import UI disables these options by default. FlitStack AI handles this gap by downloading Salesforce Files and re-uploading them as Nutshell attachments linked to the correct Person, Company, or Deal record. File size limits differ between platforms — Salesforce's 25MB per file ceiling means no single attachment exceeds Nutshell's import threshold, but large volumes of files require a separate re-hosting step scheduled after the core data migration.

  • Salesforce FSL custom objects (SchedulingPolicy, Appointment Dependency, Territory) need individual migration plans

    Salesforce Field Service ships with custom managed-package objects — SchedulingPolicy, Appointment Dependency, Optimization Request, Territory, SLR Cache, and Gantt Filter — that exist within the FSL namespace and have no analogue in Nutshell. These cannot be migrated through a standard object-to-object mapping. We document each object during discovery, assess which contain operational data versus platform configuration, and build a per-object migration plan. Scheduling rules and territory definitions are exported as JSON reference files for your Nutshell admin to rebuild manually using Nutshell's own pipeline and task logic.

  • Owner and user resolution by email is required — inactive Salesforce users block record assignment

    Salesforce Field Service users may include dispatcher accounts, contractor accounts, and technician profiles that were never invited as Salesforce CRM users. When migrating records to Nutshell, owner resolution relies on email matching against Nutshell user accounts. Any Salesforce user whose email does not correspond to a Nutshell user is flagged before migration and assigned to a fallback owner specified in the migration plan. Unresolved owners that are left unaddressed result in records landing without an assigned owner, which disrupts reporting in Nutshell from day one.

  • Salesforce API rate limits cap extraction throughput during large migrations

    Salesforce enforces daily API request limits that vary by edition and licensing model — Enterprise and Unlimited editions typically allow 150,000 API calls per day, while Starter and Professional tiers are lower. For migrations exceeding 100,000 records, extracting all objects within the daily limit requires sequencing the export across multiple days using Bulk API 2.0 batch jobs. FlitStack AI manages batch sizing and retry logic to stay within rate limits and avoid org-wide API throttling that could affect your live Salesforce instance during the extraction window.

Migration approach

Six steps for a successful Salesforce Field Service to Nutshell data migration

  1. Discovery and Salesforce export preparation

    FlitStack AI reviews your Salesforce org to catalogue all standard and custom objects, field sets, and field-service-specific records (WorkOrder, ServiceAppointment, Asset, Skill). We generate a Salesforce Data Export or configure Bulk API extraction for all target objects, aligned to your org's API rate limits. We also surface FSL-managed-package objects that require individual migration plans and confirm with you which objects contain operational data versus platform configuration.

  2. Schema plan and Nutshell custom field creation

    Before any records move, we deliver a Nutshell schema plan that lists every custom field to be created, its Salesforce source field, data type mapping, and placement (Company, Person, Lead, or Deal). Your Nutshell admin creates the custom fields from the plan — FlitStack can execute this via Nutshell's API if given admin credentials. WorkOrder flattening logic is documented with exact field names so service history is organised logically on Company records from the start.

  3. Owner and user email resolution

    We extract the full list of Salesforce users from the export and match them against Nutshell user accounts by email address. Records whose owner email has no Nutshell match are flagged with a fallback owner from your migration plan. This step runs before any records are written to Nutshell so every migrated record lands with a valid owner from the first import batch.

  4. Sample migration with field-level diff

    A representative slice of records typically comprising 200–500 records spanning Accounts, Contacts, Leads, Deals, and WorkOrder history migrates first. We generate a comprehensive field-level diff comparing source Salesforce values against the Nutshell destination fields so your team can verify custom field mapping accuracy, WorkOrder flattening layout structure, owner resolution correctness, and stage-to-pipeline value mapping alignment before the full migration run commits to the destination system.

  5. Full migration with delta-pickup cutover

    The full migration runs in dependency order: Companies first (to resolve AccountId lookups), then People and Leads (to resolve Contact-to-Company links), then Deals (to resolve Opportunity-to-Account links), then WorkOrder data (flattened to Companies) and Activities. A 24–48 hour delta-pickup window at cutover captures any records modified in Salesforce during the migration window. Files are re-hosted to Nutshell in a parallel step. An audit log documents every record written, and one-click rollback is available if reconciliation identifies a mapping error.

Platform deep dives

Context on both ends of the pair

Salesforce Field Service logo

Salesforce Field Service

Source

Strengths

  • Real-time technician location tracking and dispatch console with Gantt visualization for multi-technician schedule management.
  • Skill-based routing matches technician certifications to Work Order requirements automatically during scheduling optimization.
  • Deep integration with standard Salesforce CRM objects preserves context across field service, sales, and customer service teams.
  • Mobile app with offline capability lets field technicians update status, log parts, and capture signatures in low-connectivity environments.

Weaknesses

  • Per-seat licensing plus storage overages, API throttling charges, and Agentforce conversation fees create a total cost that significantly exceeds the base license price.
  • Inherited implementations with years of customizations, Process Builder flows, and AppExchange add-ons create tangled configurations that are difficult to migrate or audit.
  • API rate limits vary by edition and require careful monitoring—large data migrations can exhaust daily limits or concurrent call budgets mid-transfer.
  • Limited native export tooling means migrations typically require third-party tools, Data Loader configuration, or managed services partners to extract complete data.
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 Salesforce Field Service 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

    Salesforce Field Service: Per-org daily API limit starts at 100,000 requests / 24 hours for Enterprise Edition and scales with licenses purchased. Additional API calls can be purchased in 200-10,000 increments. Bulk API and Bulk API 2.0 share an allocation of 15,000 batch submissions per 24 hours. HTTP 429 returned when rate-limited..

  • Data volume sensitivity

    A

    Salesforce Field Service exposes a bulk API — large-volume migrations stream efficiently.

Estimator

Estimate your Salesforce Field Service 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 Salesforce Field Service to Nutshell data migrations

Answers to the questions buyers ask most during Salesforce Field Service to Nutshell migration scoping. Not seeing yours? Book a call.

Can't find your answer?

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

Book a free 30 minute consultation

Most Salesforce Field Service to Nutshell migrations complete in 48–96 hours of clock time for under 50,000 total records. Migration complexity scales with the number of WorkOrder, ServiceAppointment, and custom FSL objects in your org — each non-standard object adds planning and mapping work. For orgs with 200,000+ records or multiple FSL custom objects, plan for 7–14 days to allow for schema setup, sample migration validation, and delta-pickup cutover. The Nutshell-side custom field creation (driven by our schema plan) runs in parallel with extraction planning and does not add sequential time.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Salesforce Field Service.
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