CRM migration
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
Source
Nutshell
Destination
Compatibility
15 of 15
objects map 1:1 between Salesforce Field Service and Nutshell.
Complexity
BStandard
Timeline
48–96 hours of clock time
Overview
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.
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 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
Nutshell
Company
1:1Salesforce 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
Nutshell
Person
1:1Salesforce 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
Nutshell
Lead
1:1Salesforce 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
Nutshell
Deal
1:1Salesforce 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
Nutshell
Company (custom fields)
1:1Salesforce 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
Nutshell
Company (custom fields)
1:1WorkOrderLineItem 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
Nutshell
Activity (custom fields)
1:1Salesforce 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
Nutshell
Company (custom fields)
1:1Salesforce 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
Nutshell
Person (custom fields)
1:1Salesforce 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
Nutshell
Company (custom fields)
1:1Salesforce 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
Nutshell
Task
1:1Salesforce 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
Nutshell
Activity
1:1Salesforce 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
Nutshell
Note
1:1Salesforce 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)
Nutshell
Custom Field (per object)
1:1Every 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
Nutshell
Company (custom fields)
1:1Salesforce 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.
| Salesforce Field Service | Nutshell | Compatibility | |
|---|---|---|---|
| Account | Company1:1 | Fully supported | |
| Contact | Person1:1 | Fully supported | |
| Lead | Lead1:1 | Fully supported | |
| Opportunity | Deal1:1 | Fully supported | |
| WorkOrder | Company (custom fields)1:1 | Fully supported | |
| WorkOrderLineItem | Company (custom fields)1:1 | Fully supported | |
| ServiceAppointment | Activity (custom fields)1:1 | Fully supported | |
| Asset | Company (custom fields)1:1 | Fully supported | |
| Skill | Person (custom fields)1:1 | Fully supported | |
| Product2 | Company (custom fields)1:1 | Fully supported | |
| Task | Task1:1 | Fully supported | |
| Event | Activity1:1 | Fully supported | |
| Note | Note1:1 | Fully supported | |
| Custom Object (__c) | Custom Field (per object)1:1 | Fully supported | |
| Entitlement | Company (custom fields)1: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.
Salesforce Field Service gotchas
250-record batch limit for Enhanced Scheduling optimization
Process Builder workflows do not migrate—must be rebuilt in Flow Builder
API rate limits vary by edition and are easy to exhaust during bulk migration
Storage overages at $125/GB inflate migration data costs
Custom fields and lookups require explicit field-level mapping
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
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.
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.
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.
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.
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
Salesforce Field Service
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 Salesforce Field Service 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
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
Salesforce Field Service 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 Salesforce Field Service to Nutshell migration scoping. Not seeing yours? Book a call.
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 consultationAdjacent paths
Other ways to leave Salesforce Field Service
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.