CRM migration
Field-level mapping, validation, and rollback between Field Pros and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Field Pros
Source
Nutshell
Destination
Compatibility
12 of 12
objects map 1:1 between Field Pros and Nutshell.
Complexity
BStandard
Timeline
24–72 hours
Overview
Teams migrate from Field Pros to Nutshell when they need a full CRM rather than a recruiting-centric tool — pipeline management, deal tracking, built-in call and email logging, and a sales-automation layer that Field Pros does not provide natively. The migration carries every record that exists in Field Pros (contacts, companies, and associated deal or candidate data) into Nutshell's people, accounts, and opportunities model. The main planning work is mapping Field Pros contact properties to Nutshell's standard person fields and identifying any custom properties that require Nutshell custom fields. FlitStack AI extracts data via the source API or structured export, validates field-level parity against Nutshell's schema, and delivers a test migration before committing the full cutover. Because Field Pros does not publish a direct export-to-CRM endpoint, the data extraction phase uses the account's available export tools and handles any CSV normalization before loading into Nutshell. Workflows and automations in Field Pros do not transfer and must be rebuilt in Nutshell using Nutshell's built-in sequences and task-automation features. Activities, notes, and any attachments migrate as records with their original timestamps and owners intact.
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 Field Pros 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.
Field Pros
Contact (Person record)
Nutshell
Person
1:1Field Pros person records map directly to Nutshell People. Standard fields (name, email, phone, address) carry over as-is. Records with no associated company land as standalone People in Nutshell rather than requiring an account link first.
Field Pros
Company (Organization record)
Nutshell
Account
1:1Field Pros organization records map to Nutshell Accounts. Company name, domain, industry, employee count, and revenue fields translate directly. Multi-office organizations are stored as a single Account record with address as the primary location.
Field Pros
Contact–Company association
Nutshell
Person linked to Account
1:1Field Pros N:1 person-to-company links translate to Person records with a primary AccountId set in Nutshell. If a person is associated with multiple organizations in Field Pros, the most recently modified association becomes the primary link and secondary associations are stored in Nutshell's contact-company relationship fields.
Field Pros
Deal / Opportunity
Nutshell
Opportunity
1:1Field Pros deal records (if used for candidate placements or commission tracking) map to Nutshell Opportunities. Deal name, amount, expected close date, and owner resolve by email match to Nutshell users. The Nutshell pipeline stage value maps via a value-by-value table configured during migration planning.
Field Pros
Candidate status / stage
Nutshell
Custom field on Person / Opportunity
1:1Field Pros uses stage names tied to recruiting pipelines (e.g., Applied, Screening, Interview, Offer, Hired). Nutshell does not have a native candidate-stage equivalent. These values migrate as a custom pick-list field on Person or Opportunity depending on the most natural use — your team chooses the record type during migration planning.
Field Pros
Activity / Communication log
Nutshell
Call / Email / Meeting
1:1Field Pros candidate communication logs (emails, call notes, interview schedules) map to Nutshell's Call, Email, and Meeting activity types. All original timestamps, owners (resolved by email match), and linked record IDs are preserved so activity history is continuous from day one in Nutshell.
Field Pros
Custom fields on contacts
Nutshell
Custom fields on Person
1:1Field Pros supports custom fields per contact record. Nutshell allows custom fields on People, Companies, and Leads via Settings > Custom Fields. All Field Pros custom field values migrate into the corresponding Nutshell custom fields. The Nutshell API supports setting custom field values at import time. If the custom field does not yet exist in Nutshell, it is created during the schema-setup phase before the full migration runs.
Field Pros
Attachment / Resume file
Nutshell
File attachment on Person
1:1Field Pros resume and document attachments per candidate record re-upload to Nutshell Files linked to the corresponding Person record. File size limits are enforced at 25MB per file for Nutshell's storage layer. Inline images or embedded objects within documents are downloaded separately and re-attached as discrete files.
Field Pros
Owner / Recruiter assignment
Nutshell
Assigned user on Person / Account / Opportunity
1:1Field Pros recruiter or owner assignments link to user records by email address. Nutshell allows a primary assigned user on each Account, Person, Lead, and Opportunity. Where Field Pros allows multiple assignees, Nutshell uses the most recently active assignment as the primary and records the full assignment list in a custom field or the notes field.
Field Pros
Tags / Labels
Nutshell
Tag
1:1Field Pros tags and labels on contacts map 1:1 to Nutshell Tags. Nutshell applies tags as a comma-separated list at the record level. All tags from Field Pros are preserved on the mapped Person or Account record without transformation.
Field Pros
Source tracking (referral, job board)
Nutshell
Source field on Person
1:1Field Pros tracks candidate source (referral, job board, direct application). Nutshell has a native Source pick-list on People and Leads. Values map value-by-value; any source values not yet configured in Nutshell are added as new Source options during the schema-setup phase.
Field Pros
Internal notes
Nutshell
Note on Person / Account / Opportunity
1:1Free-text notes on Field Pros records migrate as Nutshell Notes linked to the corresponding Person, Account, or Opportunity. Original note timestamps and author (resolved by email match) are preserved. Rich-text formatting in Field Pros notes is flattened to plain text during import to match Nutshell's Note model.
| Field Pros | Nutshell | Compatibility | |
|---|---|---|---|
| Contact (Person record) | Person1:1 | Fully supported | |
| Company (Organization record) | Account1:1 | Fully supported | |
| Contact–Company association | Person linked to Account1:1 | Fully supported | |
| Deal / Opportunity | Opportunity1:1 | Fully supported | |
| Candidate status / stage | Custom field on Person / Opportunity1:1 | Fully supported | |
| Activity / Communication log | Call / Email / Meeting1:1 | Fully supported | |
| Custom fields on contacts | Custom fields on Person1:1 | Fully supported | |
| Attachment / Resume file | File attachment on Person1:1 | Fully supported | |
| Owner / Recruiter assignment | Assigned user on Person / Account / Opportunity1:1 | Fully supported | |
| Tags / Labels | Tag1:1 | Fully supported | |
| Source tracking (referral, job board) | Source field on Person1:1 | Fully supported | |
| Internal notes | Note on Person / Account / Opportunity1: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.
Field Pros gotchas
Work Order status enums differ between FSM platforms
Asset parent-child hierarchies do not transfer cleanly
Offline writes require re-sync handling
Custom field picklist values have no cross-platform equivalent
Preventive maintenance schedule rules cannot be exported
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 and normalize data from Field Pros
FlitStack AI pulls data from Field Pros using your account's available export tools. Because Field Pros does not publish a CRM-native export endpoint, we work with the structured report exports your account generates and normalize the CSV headers, date formats, and multi-value fields (tags, stage-change logs) to match Nutshell's import schema. Any records with missing required fields are flagged for your team to complete before the migration loads.
Set up Nutshell custom fields and pick-list values
Before data loads, we create the custom fields required for your migration: Candidate_Stage__c on Person and Lead, Probability__c on Opportunity, Original_Create_Date__c and Source_System_ID__c on Person and Account, and Secondary_Assignees__c if needed. Nutshell pick-list values (Industry, Source, Opportunity Stage) are populated with the exact values that exist in Field Pros so no data is lost to an unmapped default.
Resolve owners by email and sequence the migration order
We match Field Pros recruiter and owner email addresses against Nutshell user accounts. Accounts are migrated first so they exist when People are linked. People are loaded next with their AccountId resolved. Opportunities are loaded last since they reference both People and Accounts. Any Field Pros contacts with no corresponding Nutshell user are flagged before migration runs so your team either invites the user to Nutshell or designates a fallback owner.
Run a sample migration with field-level diff
A representative slice of 100–500 records migrates first, spanning contacts, companies, and any deals or activities. We generate a field-level diff between the Field Pros export and the Nutshell records so you can verify candidate-stage mapping, owner resolution, and tag assignment before the full run commits. Adjustments to field mapping or pick-list values are made before proceeding.
Execute full migration with delta pickup and rollback plan
The full migration loads into Nutshell with an audit log capturing every record created and every field value set. A delta-pickup window of 24–48 hours captures any new or modified records in Field Pros during the cutover period. Your team continues working in Field Pros throughout — FlitStack AI uses read-only access. If reconciliation identifies missing or mis-mapped records, one-click rollback restores the pre-migration state in Nutshell while the issue is resolved.
Platform deep dives
Field Pros
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 Field Pros 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
Field Pros: Not publicly documented.
Data volume sensitivity
Field Pros 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 Field Pros to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your Field Pros 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 Field Pros
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.