CRM migration
Field-level mapping, validation, and rollback between Simple Sales Tracking and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Simple Sales Tracking
Source
Nutshell
Destination
Compatibility
8 of 10
objects map 1:1 between Simple Sales Tracking and Nutshell.
Complexity
BStandard
Timeline
2-3 weeks
Overview
Moving from Simple Sales Tracking to Nutshell is a migration from a flat-rate entry-level CRM to a platform with deeper sales feature depth, integrated marketing tools, and a documented API surface. Simple Sales Tracking exposes read and write endpoints for Contacts, Opportunities, and pipeline data but lacks a bulk export endpoint, requiring paginated API polling for extraction. Custom field definitions are not returned by any schema endpoint, so we reconstruct the field map from customer-provided screen captures and sample API responses during discovery. The 50-record trial import ceiling can mask true data volume during scoping, so we always request a full record count before finalizing migration timelines. We do not migrate workflows, sequences, or the real-time Activity Feed as standalone objects; we deliver written inventories of these for the customer's admin to rebuild in Nutshell's automation builder.
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 Simple Sales Tracking 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.
Simple Sales Tracking
Leads
Nutshell
Lead
1:1Simple Sales Tracking Lead records map directly to Nutshell Lead. We preserve Lead source fields, status, and any custom Lead-level properties. Nutshell's Lead object supports custom fields for fields that do not map to standard properties. The migration resolver holds Lead records that reference unresolvable Owner IDs in a reconciliation queue for the customer to address before final import.
Simple Sales Tracking
Opportunities
Nutshell
Deal
1:1Simple Sales Tracking Opportunities map to Nutshell Deals with amount, stage, expected close date, and owner assignment preserved. The source pipeline stage name maps to the closest Nutshell pipeline stage; any custom stages with no direct equivalent are flagged for the customer to configure in Nutshell before migration completes.
Simple Sales Tracking
Accounts
Nutshell
Company
1:1Simple Sales Tracking Accounts store company-level data associated with Contacts and Opportunities. We migrate Account names, addresses, industry tags, and associated Contact relationships as a joined unit. Nutshell's Company object serves as the parent record for Person records, so we create Companies first and resolve the Company-Contact linkage before inserting Person records.
Simple Sales Tracking
Contacts
Nutshell
Person
1:1Simple Sales Tracking Contacts hold individual person records with name, email, phone, and address fields. We handle Contact-to-Account (Company) linking explicitly during import to avoid orphaned Person records in Nutshell. Where a Contact has no linked Account in Simple Sales Tracking, we create a placeholder Company record to satisfy Nutshell's data model.
Simple Sales Tracking
Appointments
Nutshell
Activity (Task or Event)
1:1Simple Sales Tracking Appointments include date, time, duration, title, and linked Contact reference. We migrate appointment records with their timestamps and linked Contact Person references. Destination calendar systems may require re-association of invitees; Nutshell Activities preserve the original date and duration and link to the associated Person or Company.
Simple Sales Tracking
Tasks
Nutshell
Task
1:1Simple Sales Tracking Tasks carry a due date, assignee, and completion status. We migrate open and completed tasks with their timestamps and assignee references. Task histories in Simple Sales Tracking do not include a full log of status changes, so we import the final status state without the intermediate transition history.
Simple Sales Tracking
Notes
Nutshell
Note
1:1Simple Sales Tracking Notes are free-text records attached to Contacts or Opportunities. We preserve note content and timestamp but do not guarantee retention of rich-text formatting or embedded file links. Notes attach to the migrated Person, Company, or Deal record via Nutshell's note linking mechanism.
Simple Sales Tracking
Custom Sales Record Fields
Nutshell
Custom Fields
lossySimple Sales Tracking allows custom fields on Sales Records but exposes no schema endpoint to enumerate them. We reconstruct the field map during discovery by requesting a screen capture of the customer's custom field configuration page, then cross-reference a sample API response against those definitions. Each custom field is created in Nutshell as a typed custom field (Text, Long Text, Currency, Date, etc. per Nutshell's supported types at support.nutshell.com) before data migration begins.
Simple Sales Tracking
Custom Pipeline Stages
Nutshell
Pipeline Stage
lossySimple Sales Tracking users can define custom stage names and reorder pipeline stages. We capture the full stage sequence and map each named stage to the closest equivalent in Nutshell's pipeline configuration. Any stages with no direct equivalent are flagged with a severity note for the customer to create before final migration.
Simple Sales Tracking
Users and Permissions
Nutshell
User
1:1Simple Sales Tracking multi-level permissions map to Nutshell user roles. We export user records and role assignments by email match against the destination Nutshell account. Any Simple Sales Tracking user without a matching Nutshell account is placed in a reconciliation queue for the customer admin to provision before record import resumes.
| Simple Sales Tracking | Nutshell | Compatibility | |
|---|---|---|---|
| Leads | Lead1:1 | Fully supported | |
| Opportunities | Deal1:1 | Fully supported | |
| Accounts | Company1:1 | Fully supported | |
| Contacts | Person1:1 | Fully supported | |
| Appointments | Activity (Task or Event)1:1 | Mapping required | |
| Tasks | Task1:1 | Mapping required | |
| Notes | Note1:1 | Mapping required | |
| Custom Sales Record Fields | Custom Fieldslossy | Mapping required | |
| Custom Pipeline Stages | Pipeline Stagelossy | Mapping required | |
| Users and Permissions | User1: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.
Simple Sales Tracking gotchas
Trial import ceiling of 50 records masks true data volume
No public bulk export API requires iterative extraction
Custom field definitions are not exposed via a schema endpoint
Activity Feed is a real-time stream with no historical query API
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 data volume audit
We request a data-volume estimate from the customer covering Leads, Opportunities, Accounts, Contacts, Appointments, Tasks, Notes, and any files. We ask for a screen capture of the Simple Sales Tracking custom field configuration page and a list of all custom pipeline stage names. We also request the total file attachment count and approximate storage used. This information determines the extraction pacing strategy and flags any data volume risks before migration planning begins.
Custom field schema reconstruction
Since Simple Sales Tracking does not expose a schema endpoint, we cross-reference the customer's custom field screen capture with a sample API response to enumerate every custom field and its data type. We map each to the closest Nutshell custom field type (Text, Long Text, Currency, Date, etc.) and pre-create the fields in the destination Nutshell account before any data migration begins. Any unmappable fields are flagged for the customer to review.
Extraction via paginated API polling
We extract records from Simple Sales Tracking using paginated API polling against the standard object endpoints. We implement checkpoint-based extraction with conservative request pacing to avoid triggering any undocumented throttling. Each object type (Contacts, Opportunities, Leads, Accounts, Tasks, Appointments, Notes) is extracted independently and written to a staged export file. File attachments are downloaded in parallel and associated with their parent record by reference ID.
Sandbox import and reconciliation
We run a full migration into a staging environment within Nutshell using production-like record volumes. The customer reconciles record counts against the Simple Sales Tracking source and spot-checks 15-25 records per object type. Any mapping corrections, custom field gaps, or pipeline stage mismatches are addressed here before the production migration begins.
Production migration in dependency order
We run production migration in record-dependency order: Companies first (to serve as parent records), then Persons (with CompanyId resolved), Leads, Deals (with Person and Company lookups resolved), Tasks, Appointments, Notes, and file attachments last. Each phase emits a row-count reconciliation report. Custom field values are loaded after the base object import using the pre-created Nutshell custom field definitions.
Cutover and workflow inventory handoff
We freeze writes to Simple Sales Tracking during cutover, run a final delta migration of any records modified during the migration window, and enable Nutshell as the system of record. We deliver a written inventory of any Simple Sales Tracking automation equivalents that require rebuild in Nutshell (including Nutshell's automation triggers and any workflow patterns the customer used). We do not rebuild automations inside the migration scope; that work is handled by the customer's admin or a Nutshell implementation partner.
Platform deep dives
Simple Sales Tracking
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 Simple Sales Tracking 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
Simple Sales Tracking: Not publicly documented.
Data volume sensitivity
Simple Sales Tracking 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 Simple Sales Tracking to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your Simple Sales Tracking 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 Simple Sales Tracking
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.