CRM migration

Migrate from Simple Sales Tracking to Nutshell

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 logo

Simple Sales Tracking

Source

Nutshell

Destination

Nutshell logo

Compatibility

80%

8 of 10

objects map 1:1 between Simple Sales Tracking and Nutshell.

Complexity

BStandard

Timeline

2-3 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

Field-level fidelity

Every standard and custom field arrives verified.

Schema-aware mapping

AI proposes the map; you confirm before any record moves.

Relationships preserved

Parent–child, lookups, and ownership stay linked.

Full activity history

Calls, emails, meetings — with original timestamps.

Attachments & notes

Documents, uploads, and inline notes move with the record.

Why teams make this switch

Two sides of the same decision

Leaving

Simple Sales Tracking logo

Simple Sales Tracking

What's pushing teams away

  • Lack of native integrations with email platforms, calendars, and accounting tools forces teams to maintain workarounds that break over time.
  • No built-in marketing automation, email sequences, or lead scoring means the platform does not scale as the team grows beyond reactive tracking.
  • File storage capped at 1 GB across all users creates a hard ceiling for teams that rely heavily on document attachments.
  • Limited reporting depth compared to mid-market CRMs leaves sales managers without the drill-down analytics needed for pipeline reviews.
  • Absence of a public API changelog or versioned endpoints raises concerns about long-term data portability and integration stability.

Choosing

Nutshell logo

Nutshell

What's pulling them in

  • Lowest cost entry point among mid-market CRMs—Foundation plan starts at $13/user/month, making it accessible for teams validating CRM fit before committing.
  • Integrated sales automation and email sequencing on Pro plans without requiring a separate email marketing platform, per verified Capterra reviews.
  • Consistently praised for intuitive interface and fast onboarding, with case studies reporting 100% team adoption rates within initial deployment periods.
  • Strong customer support responsiveness cited across G2 reviews, with dedicated support tiers available on Enterprise plans.
  • Native integrations with WhatsApp, Facebook Messenger, Instagram, and Slack reduce reliance on third-party middleware for common communication channels.

Object mapping

How Simple Sales Tracking objects map to Nutshell

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

maps to

Nutshell

Lead

1:1
Fully supported

Simple 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

maps to

Nutshell

Deal

1:1
Fully supported

Simple 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

maps to

Nutshell

Company

1:1
Fully supported

Simple 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

maps to

Nutshell

Person

1:1
Fully supported

Simple 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

maps to

Nutshell

Activity (Task or Event)

1:1
Mapping required

Simple 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

maps to

Nutshell

Task

1:1
Mapping required

Simple 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

maps to

Nutshell

Note

1:1
Mapping required

Simple 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

maps to

Nutshell

Custom Fields

lossy
Mapping required

Simple 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

maps to

Nutshell

Pipeline Stage

lossy
Mapping required

Simple 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

maps to

Nutshell

User

1:1
Mapping required

Simple 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.

Gotchas + challenges

What specifically takes care here

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 logo

Simple Sales Tracking gotchas

Medium

Trial import ceiling of 50 records masks true data volume

High

No public bulk export API requires iterative extraction

Medium

Custom field definitions are not exposed via a schema endpoint

Low

Activity Feed is a real-time stream with no historical query API

Nutshell logo

Nutshell gotchas

High

Contact tier limits enforced on import

Medium

No bulk API endpoint requires paginated extraction

Medium

Email sequences not exportable via API

Medium

Foundation plan disables key sales features

Pair-specific challenges

  • No bulk export API requires iterative paginated polling

    Simple Sales Tracking exposes read and write endpoints for individual records but does not document a bulk or batch export endpoint. For migrations involving more than a few hundred records, we implement paginated polling against the standard object endpoints. We set conservative request pacing during extraction to avoid triggering any undocumented throttling, and we checkpoint our progress between page fetches to handle mid-export session timeouts gracefully. This extends the extraction phase compared to platforms with a documented bulk export endpoint.

  • Custom field schema is not exposed via any API endpoint

    Simple Sales Tracking allows users to define custom fields on Sales Records and pipeline objects, but there is no API endpoint that returns the current field schema. We must extract custom field definitions from the platform's UI metadata or by inspecting a sample export. We address this by requesting a screen capture of the customer's custom field configuration page during discovery, then cross-referencing it against a sample API response to build the complete field map before migration day. Without this step, custom fields are silently dropped during import.

  • 1 GB file storage cap limits attachment migration volume

    Simple Sales Tracking provides 1 GB of uploaded file storage total per account. During discovery, we request a file inventory estimate to determine whether the attachment set fits within the destination plan's storage allowance. Nutshell's storage limits vary by plan tier. We export files attached to Contacts, Opportunities, and Notes as individual downloads and re-attach them in Nutshell, but if the source attachment set approaches or exceeds 1 GB, we flag the overage and ask the customer to prioritize the most critical files for migration.

  • Trial import ceiling masks true data volume

    During the trial period, Simple Sales Tracking limits batch imports to 50 sales records at a time. Customers often assume their dataset is small when they have only exercised this trial ceiling. We request a full record count estimate from the customer before migration scoping to avoid discovering a 3,000-record dataset only after trial constraints lift. We schedule a data-volume discovery call before the trial ends to capture accurate record counts for all object types.

  • Activity Feed has no historical query API

    The activity feed visible in the Simple Sales Tracking UI is a live event log rather than a queryable history table. There is no API endpoint to retrieve historical feed entries. For customers who rely on the feed for audit trails, we explain that the historical feed cannot be migrated as a standalone dataset. We suggest exporting any critical feed entries as manual notes before the migration date and attaching them to the relevant Contact or Opportunity record in Nutshell after migration.

Migration approach

Six steps for a successful Simple Sales Tracking to Nutshell data migration

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

  6. 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

Context on both ends of the pair

Simple Sales Tracking logo

Simple Sales Tracking

Source

Strengths

  • Single flat price of $15/user/month with unlimited Leads, Opportunities, Contacts, Tasks, and Notes.
  • Custom Sales Record fields and custom Pipeline stage definitions allow small teams to model their exact process.
  • Multi-level user permissions support hierarchical sales team structures without requiring admin overhead.
  • Smart BCC Email integration and daily reminders provide lightweight automated nudges for reps.
  • Real-time activity feed surfaces team-wide updates without requiring a separate communication layer.

Weaknesses

  • No public rate limit documentation for the API makes it difficult to estimate migration throughput before scoping.
  • No documented bulk export endpoint means large record sets require iterative API polling during extraction.
  • File storage capped at 1 GB total per account limits the volume of document attachments that can be migrated.
  • No native email sequencing or marketing automation restricts the platform to reactive sales tracking only.
  • Language-specific API kits are limited to a small set; most integrations require custom HTTP wrapper code.
Nutshell logo

Nutshell

Destination

Strengths

  • Simple, intuitive interface with minimal learning curve for sales teams new to CRM
  • Per-seat pricing is transparent and predictable, with annual billing reducing monthly cost
  • Full data export tool available for all account data including backups
  • Open JSON-RPC API allows programmatic access to all core objects
  • Native multichannel engagement (email, SMS, WhatsApp) without third-party add-ons for communication

Weaknesses

  • Reporting and analytics are considered weak, requiring manual Excel exports for detailed analysis
  • No bulk API endpoint—migration requires paginated API reads that must be rate-limited carefully
  • JSON-RPC API is less common than REST, requiring custom integration code compared to standard REST CRMs
  • Add-on costs (Forms, Nutshell IQ, Email Marketing) are per-company charges that stack on top of per-seat pricing
  • Feature restrictions on entry-level plans mean teams often need mid-tier to get basic automation

Complexity grading

How hard is this migration?

Standard CRM migration. 2 of 8 objects need a mapping; the rest are 1:1.

B

Overall complexity

Standard migration

Derived from compatibility, mapping clarity, API constraints, and data volume across Simple Sales Tracking and Nutshell.

  • Object compatibility

    B

    2 of 8 objects need a mapping; the rest are 1:1.

  • Field mapping clarity

    C

    Field mapping is derived from defaults — final spec confirmed during the sample migration.

  • Timeline complexity

    B

    8-object category — typical timelines run 2–7 days end-to-end.

  • API constraints

    B

    Simple Sales Tracking: Not publicly documented.

  • Data volume sensitivity

    B

    Simple Sales Tracking doesn't expose a bulk API — REST + parallelization used for high-volume runs.

Estimator

Estimate your Simple Sales Tracking to Nutshell migration cost

Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.

Step 1

What are you migrating?

Pick a category, then your source and destination platforms.

Category

FAQ

Frequently asked questions about Simple Sales Tracking to Nutshell data migrations

Answers to the questions buyers ask most during Simple Sales Tracking to Nutshell migration scoping. Not seeing yours? Book a call.

Can't find your answer?

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 consultation

Most migrations land between two and three weeks for accounts with fewer than 2,000 records per object type and under ten custom fields. Migrations with larger contact lists (over 10,000 records), extensive task or appointment histories, or complex custom field sets extend to four to six weeks because of the iterative API polling required during extraction and the manual custom field schema reconstruction when no schema endpoint exists.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Simple Sales Tracking.
Land in Nutshell, intact.

Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.

Accuracy guarantee Rollback included Quote in 1 business day