CRM migration
Field-level mapping, validation, and rollback between Prospects CRM and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Prospects CRM
Source
Nutshell
Destination
Compatibility
15 of 15
objects map 1:1 between Prospects CRM and Nutshell.
Complexity
BStandard
Timeline
1–3 days
Overview
Prospects CRM and Nutshell take different approaches to core CRM objects. Prospects CRM uses a unified data model with People linked to Companies and Deals, where Deals optionally reference inventory/order data from integrated accounting platforms. Nutshell separates People, Companies, and Leads as distinct record types, with Deals (called 'Deals' in Nutshell) as separate objects that can associate with People and Companies through Nutshell's linking model. We map Prospects People to Nutshell People, Prospects Companies to Nutshell Companies, Prospects Deals to Nutshell Deals, and Prospects Leads to Nutshell Leads. Custom fields created in Prospects migrate as custom fields on the corresponding Nutshell object (Person, Company, or Lead). Activity history — notes, calls, meetings — migrates as Nutshell Activities with original timestamps and owner links preserved. Prospects' workflows, automations, and RFM segmentation rules do not have equivalents in Nutshell; we export them as JSON reference files for your admin to rebuild. The migration runs via Prospects API (JSON-RPC over HTTPS) pulling full record payloads, then writes into Nutshell through their API, with a delta-pickup window capturing any in-flight changes during the cutover.
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 Prospects CRM 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.
Prospects CRM
People
Nutshell
Person
1:1Prospects People map 1:1 to Nutshell People records. Core contact fields including name, email address, phone number, physical address, and social media links migrate directly without transformation. Any custom fields defined on the Prospects People object become Nutshell custom fields attached to the Person object, with field types matched to their nearest Nutshell equivalents. The original Prospects record owner is resolved by matching the owner email address to an existing Nutshell user account during migration.
Prospects CRM
Company
Nutshell
Company
1:1Prospects Companies map directly to Nutshell Company records. Company name, domain/website, industry classification, employee count, and annual revenue fields migrate as straightforward field-to-field transfers. Physical address components combine into Nutshell's compound address structure. Parent-company hierarchical relationships from Prospects transfer into a custom Parent_Company__c text field in Nutshell to preserve organizational structure reporting. Company record ownership resolves via owner email matching to Nutshell users.
Prospects CRM
Lead
Nutshell
Lead
1:1Prospects Leads migrate directly to Nutshell Leads with full fidelity. Lead source attribution, current status, and assigned owner transfer as-is without transformation. All custom fields attached to Prospects Leads create corresponding custom fields on the Nutshell Lead object. Unconverted Prospects Leads route automatically into Nutshell's lead inbox queue where they await follow-up assignment by your sales team. Lead create timestamps and last modified dates preserve as custom datetime fields in Nutshell.
Prospects CRM
Deal
Nutshell
Deal
1:1Prospects Deals map to Nutshell Deals with deal name, monetary amount, and current stage preserved exactly. Each Prospects sales pipeline becomes a separate Nutshell pipeline with pipeline-specific stage configurations. Stage names transfer value-by-value across the mapping. When Prospects Deals contain inventory item references from integrated accounting platforms, those external references are captured as line-item text in the Nutshell Deal description field for manual product entry after migration.
Prospects CRM
People-Company association
Nutshell
Person-Company link
1:1Prospects' N:1 relationship model where multiple People records can associate with a single Company migrates as Nutshell's person-to-company linking architecture. The primary company assignment on a Prospects Person record becomes the main Company link on the corresponding Nutshell Person. Any secondary company associations are flagged in the migration audit log as secondary links requiring admin review and potential cleanup in Nutshell after migration completes.
Prospects CRM
Deal-People-Company link
Nutshell
Deal-Person link
1:1Prospects Deal-to-Person and Deal-to-Company association records migrate as Nutshell Deal links connecting to the corresponding Person and Company objects. All linked People appear on the Nutshell Deal record under its People tab for complete visibility. When a Prospects Deal links to multiple People and Companies, each association creates a separate link record in Nutshell preserving the full relationship graph from the source system.
Prospects CRM
Note
Nutshell
Activity (Note)
1:1Prospects Notes migrate as Nutshell Activity records with activity type set to 'Note'. The original Prospects create timestamp is preserved in a custom Created_In_Source__c datetime field on the Activity record. Note body content transfers as-is maintaining all text formatting. Each note links to its associated Person or Company record using Prospects' original record association identifiers to maintain the complete contextual thread of customer communication history.
Prospects CRM
Call / Meeting
Nutshell
Activity (Call / Meeting)
1:1Prospects logged calls and scheduled meetings migrate as Nutshell Activity records with the appropriate activity type ('Call' or 'Meeting'). Original start timestamps, end timestamps, duration measurements, and activity owner all transfer with full fidelity. Each activity links to its associated Person record in Nutshell using the original Prospects record association data. Call outcomes and meeting notes embedded in the Prospects activity records populate the Nutshell activity description field.
Prospects CRM
Custom Field (People)
Nutshell
Custom Field (Person)
1:1All custom fields defined on Prospects People objects migrate as Nutshell custom fields attached to the Person object. Field data types including text strings, numeric values, dates, checkboxes, and dropdown selections are matched to the closest available Nutshell field type equivalent. Each custom field is created in Nutshell before the migration execution phase begins, ensuring the field exists and is properly configured to receive data during the transfer process.
Prospects CRM
Custom Field (Deal)
Nutshell
Custom Field (Deal)
1:1Prospects Deal-level custom fields including discount codes, internal order reference numbers, and shipping flags migrate as Nutshell Deal custom fields with appropriate type matching. When Prospects custom fields contain references to integrated inventory data from platforms like Unleashed or Xero, the field migrates as a text field and the underlying reference value surfaces in the Nutshell Deal description for manual product entry and reconciliation.
Prospects CRM
Owner / User
Nutshell
User
1:1Prospects owner and user assignments resolve through email address matching to existing Nutshell user accounts during migration. When a Prospects owner email has no corresponding Nutshell user, records are assigned to a designated fallback Nutshell user account and flagged individually in the migration audit log. Admins receive a cleanup checklist identifying all records requiring owner reassignment after migration completes for proper accountability alignment.
Prospects CRM
Workflow Rule
Nutshell
No Equivalent
1:1Prospects workflow rules including automated task creation, stage-change triggers, and lead scoring updates have no direct equivalent in Nutshell's object model or automation framework. We export complete workflow definitions as a structured JSON reference file documenting each rule's trigger conditions, evaluation criteria, and resulting actions for your Nutshell administrator to rebuild equivalent automation using Nutshell's email sequences and task triggers.
Prospects CRM
RFM / Segmentation Data
Nutshell
Tag / Custom Field
1:1Prospects' RFM (Recency, Frequency, Monetary) analysis scores and customer segment labels migrate as Nutshell Tags applied to the Person record for segmentation visibility. Numeric RFM component scores (recency days, frequency count, monetary value) preserve as custom number fields on Person enabling segment re-creation within Nutshell's reporting capabilities. Segment criteria documentation is included in the migration artifacts for reference during Nutshell segment rebuild.
Prospects CRM
Inventory Integration Reference
Nutshell
Deal Line Item / Description
1:1Prospects' live inventory integration links including stock-on-hand quantities, reorder point thresholds, and supplier data from integrated platforms like Unleashed or Xero cannot migrate because they reference external system identifiers that no longer exist post-migration. We capture these inventory references as formatted text notes attached to the associated Nutshell Deal record for your team to manually enter product details and rebuild the product catalog in Nutshell.
Prospects CRM
Attachment / File
Nutshell
File (Activity Attachments)
1:1File attachments associated with Prospects records including documents on Person, Company, and Deal objects as well as Activity records are downloaded from Prospects storage and re-uploaded to Nutshell as file attachments on the corresponding Activity or Person record. Standard Nutshell file size limits apply with a maximum of 25MB per individual file upload. File metadata including original filename and upload timestamp are preserved where supported by the Nutshell API.
| Prospects CRM | Nutshell | Compatibility | |
|---|---|---|---|
| People | Person1:1 | Fully supported | |
| Company | Company1:1 | Fully supported | |
| Lead | Lead1:1 | Fully supported | |
| Deal | Deal1:1 | Fully supported | |
| People-Company association | Person-Company link1:1 | Fully supported | |
| Deal-People-Company link | Deal-Person link1:1 | Fully supported | |
| Note | Activity (Note)1:1 | Fully supported | |
| Call / Meeting | Activity (Call / Meeting)1:1 | Fully supported | |
| Custom Field (People) | Custom Field (Person)1:1 | Fully supported | |
| Custom Field (Deal) | Custom Field (Deal)1:1 | Fully supported | |
| Owner / User | User1:1 | Fully supported | |
| Workflow Rule | No Equivalent1:1 | Fully supported | |
| RFM / Segmentation Data | Tag / Custom Field1:1 | Fully supported | |
| Inventory Integration Reference | Deal Line Item / Description1:1 | Fully supported | |
| Attachment / File | File (Activity Attachments)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.
Prospects CRM gotchas
Inventory integrations must be active before migration scoping
Magic Matrix and RFM scores require manual reconfiguration in destination
Pipeline stage names are customer-defined and non-standard
Historical order data structure varies with connected accounting platforms
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 Prospects data via JSON-RPC API with full record payloads
We authenticate to Prospects CRM using your API token over HTTPS (JSON-RPC format). We pull all People, Companies, Deals, Leads, and Activity records with their custom field values, owner assignments, and association metadata in a single pass. Each object's create date, last modified timestamp, and Prospects internal ID are captured for traceability. The Prospects API returns records in paginated responses — we iterate through all pages to ensure no record is missed before field mapping begins.
Build field mapping plan against Nutshell's object schema
We map every Prospects field to its Nutshell equivalent based on the object_mapping plan. Custom fields in Prospects are created in Nutshell as Person, Company, or Deal custom fields before migration runs. We validate the target Nutshell plan's contact cap against your Prospects total People count and flag if the target plan requires an upgrade. Stage names and pipeline names are matched value-by-value. Owner email addresses are cross-referenced against your Nutshell user list to pre-identify any unmatched owners.
Run a sample migration on a representative record slice
We migrate a stratified sample of 100–500 records spanning People, Companies, Deals, Leads, and Activities. The sample exercises every object mapping and field transformation. We generate a field-level diff report comparing source Prospects values against the resulting Nutshell records, so you can verify that custom fields, stage names, owner assignments, and activity timestamps migrated correctly. You review the sample in Nutshell before we proceed to the full run.
Execute full migration with delta-pickup window at cutover
The full migration runs against your Nutshell account. A 48-hour delta-pickup window opens at the start of cutover — any Prospects records modified or created during the migration window are captured in a second pass and written to Nutshell to ensure the destination reflects Prospects' final state. All operations are logged in an audit log. If reconciliation fails or record counts diverge from expectations, one-click rollback reverts the Nutshell account to its pre-migration state.
Deliver migration artifacts and rebuild reference package
After migration, we deliver the audit log, the field-level diff report, and a rebuild reference package. The rebuild package includes your Prospects workflow definitions as a structured JSON file, your RFM and segmentation tags mapped to Nutshell Tags, and the inventory reference text captured in Deal description fields. We also document any Prospects-integrated platform connections (Unleashed, Xero) that need to be re-established in Nutshell manually.
Platform deep dives
Prospects CRM
Source
Strengths
Weaknesses
Nutshell
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 3 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 Prospects CRM and Nutshell.
Object compatibility
3 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
Prospects CRM: Not publicly documented.
Data volume sensitivity
Prospects CRM 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 Prospects CRM to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your Prospects CRM 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 Prospects CRM
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.