CRM migration
Field-level mapping, validation, and rollback between Sellsation CRM and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Sellsation CRM
Source
Nutshell
Destination
Compatibility
7 of 8
objects map 1:1 between Sellsation CRM and Nutshell.
Complexity
BStandard
Timeline
4-6 weeks
Overview
Moving from Sellsation CRM to Nutshell is a manual-extraction migration because Sellsation publishes no public API, which means CSV exports drive the data extraction phase. We perform a full scoping call to enumerate every object and custom field in the Sellsation instance, export each entity as CSV, validate record counts against the Sellsation UI, then map and import into Nutshell's Companies, People, Deals, Tasks, and Events objects. Sellsation's traffic-light stagnation system maps to a custom Deal status field in Nutshell, and the geo map heatmap data attaches as address metadata to the corresponding Company. Multi-level campaign structures with conditional stage movements do not migrate as automations; we deliver a written campaign inventory for the customer's Nutshell admin to rebuild. The migration typically runs four to eight weeks from scoping to cutover, depending on activity history volume and data cleanliness.
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 Sellsation 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.
Sellsation CRM
Customer
Nutshell
Company
1:1Sellsation Customers are the primary account-level records and map directly to Nutshell Company records. The Customer name, address, phone, website, and industry fields map to the corresponding Nutshell Company fields. We use the Customer's primary address as the Company address and preserve any geo map location metadata as a custom address field or note attachment. Company is the first object imported because all Contact Persons and Sales Projects reference their parent Customer.
Sellsation CRM
Contact Person
Nutshell
Person
1:1Sellsation Contact Persons map 1:1 to Nutshell People records. Each Contact Person's name, email, phone, role, and linked Customer reference migrates to the Person record with the Customer-to-Company lookup resolved at import time. Full activity history including calls, meetings, and notes attaches to the Person record in Nutshell. Duplicate detection in Nutshell uses email as the dedupe key during import.
Sellsation CRM
Sales Project
Nutshell
Deal
1:1Sellsation Sales Projects map to Nutshell Deals. The pipeline stage name migrates as the Deal's pipeline stage, and Sellsation's automated potential analysis value maps to a custom field on the Deal. Sellsation's traffic-light stagnation flag (red/yellow/green deal status) maps to a custom Deal status field since Nutshell does not have a native traffic-light system. Closed-Lost and Closed-Won dates migrate as custom fields if the Nutshell account uses a Deal edition that supports them.
Sellsation CRM
Activity (calls, appointments, notes)
Nutshell
Task and Event
1:1Sellsation Activities are individual records attached to Contact Persons or Sales Projects. Calls map to Nutshell Tasks with type set to Call and duration stored in a custom field. Appointments with date, time, and attendees map to Nutshell Events with attendee lists preserved as notes or custom fields. Notes map to Nutshell Task records with type set to Note. All activity timestamps migrate as ActivityDate to preserve the chronological timeline in Nutshell's People record.
Sellsation CRM
Task
Nutshell
Task
1:1Sellsation Tasks assigned to users with due dates map directly to Nutshell Tasks. Task status, priority, and the linked Contact Person or Sales Project reference migrate with the parent lookup resolved at import time. Completed tasks preserve their completion date; open tasks preserve the due date and assignment. Tasks without a resolved parent record are held in a reconciliation queue for the customer to clarify before import.
Sellsation CRM
Campaign
Nutshell
Campaign (mapping)
1:1Sellsation's multi-level campaigns with conditional stage movements and automated task creation do not have a direct Nutshell equivalent. Nutshell supports basic campaign tracking for list-based email sends but does not support conditional stage movement automation or multi-level campaign structures natively. We export the campaign enrollment data and campaign structure as a CSV mapping document that the customer's Nutshell admin uses to rebuild campaigns using Nutshell's basic campaign lists or an external automation tool like Zapier.
Sellsation CRM
Custom Fields
Nutshell
Custom Fields
lossySellsation custom fields on Customers, Contact Persons, and Sales Projects map to Nutshell custom properties. We enumerate all custom fields during scoping, verify field types (text, number, date, picklist) during export, and create matching custom properties in Nutshell before import. Picklist-based custom fields from Sellsation require manual value mapping in Nutshell if the picklist values differ between systems.
Sellsation CRM
Geo Map Data
Nutshell
Company Address Fields
1:1Sellsation's geo map and heatmap data is stored as internal map state rather than standard geographic coordinates. We extract the linked Sales Project location data as standard address fields (street, city, region, postal code, country) and attach the original Sellsation location reference as a custom note on the Company record. The native heatmap visualization does not migrate since Nutshell does not support that visualization type.
| Sellsation CRM | Nutshell | Compatibility | |
|---|---|---|---|
| Customer | Company1:1 | Fully supported | |
| Contact Person | Person1:1 | Fully supported | |
| Sales Project | Deal1:1 | Fully supported | |
| Activity (calls, appointments, notes) | Task and Event1:1 | Fully supported | |
| Task | Task1:1 | Fully supported | |
| Campaign | Campaign (mapping)1:1 | Fully supported | |
| Custom Fields | Custom Fieldslossy | Mapping required | |
| Geo Map Data | Company Address Fields1:1 | Mapping required |
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.
Sellsation CRM gotchas
No documented public API for programmatic export
Activity history volume can bloat export files
Custom reports and dashboards do not migrate
Geo map and heatmap data is proprietary visualization
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 CSV export enumeration
We schedule a scoping call with the customer's Sellsation admin to enumerate every object, custom field, pipeline stage name, and activity type in the Sellsation instance. We identify which objects and fields are visible in the Sellsation UI versus what is exportable via CSV. We extract record counts for each object and flag any objects that appear to lack export capability, which may require manual re-entry in Nutshell. The discovery output is a written migration scope with a CSV export checklist for the customer's Sellsation admin to execute.
CSV validation and data quality assessment
We receive the exported CSV files and validate them against the scoping checklist: all enumerated fields are present, record counts in CSV match the counts reported in Sellsation, date formats are consistent, and email addresses are structurally valid. We identify duplicates, missing required fields, and orphaned records (Contact Persons with no Customer link, Sales Projects with no Contact Person link). We deliver a data quality report to the customer and agree on a data-cleansing approach before import begins.
Nutshell schema setup and custom field provisioning
We create the custom fields in Nutshell to host Sellsation-specific data that has no native Nutshell equivalent, including the traffic-light deal health field, any Sellsation custom properties, and the original Sellsation record ID for audit purposes. We configure the Deal pipeline stages to match the Sellsation pipeline stage names as closely as possible and set stage probabilities. Nutshell's custom fields are created before any data import so that the import mapping can reference them directly.
Import in dependency order: Companies, People, Deals, Activities
We import in record-dependency order: Companies first (from Sellsation Customers), then People (from Contact Persons) with the Customer-Company lookup resolved at import time, then Deals (from Sales Projects) with the Contact Person-User assignment and pipeline stage resolved, then Activities (Tasks, Events, Notes) in time-bounded batches with parent-record lookups validated before each batch. Each phase emits a row-count reconciliation report before the next phase begins.
Campaign inventory and automation handoff
We export the Sellsation campaign structure and enrollment data as a CSV mapping document. This includes campaign names, enrolled Contact Persons, campaign stage, conditional rules, and associated automated tasks. We do not rebuild campaigns in Nutshell because Nutshell's campaign model and Sellsation's multi-level campaign model are structurally different. The handoff document provides the customer's Nutshell admin with enough context to rebuild campaigns using Nutshell Sequences or an external automation platform.
Cutover, validation, and data reconciliation
We freeze Sellsation writes during cutover, run a final delta migration of any records modified during the migration window, then mark Nutshell as the system of record. We deliver a reconciliation report comparing record counts between the Sellsation export and the Nutshell import, flagging any gaps. We support a one-week hypercare window for the customer's team to report missing or incorrectly mapped records. Custom reports, dashboards, and automations are outside migration scope; we provide the underlying data for the customer's Nutshell admin to rebuild.
Platform deep dives
Sellsation CRM
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 Sellsation CRM 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
Sellsation CRM: Not publicly documented.
Data volume sensitivity
Sellsation 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 Sellsation CRM to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your Sellsation 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 Sellsation 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.