CRM migration
Field-level mapping, validation, and rollback between Saleshiker and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Saleshiker
Source
Nutshell
Destination
Compatibility
11 of 12
objects map 1:1 between Saleshiker and Nutshell.
Complexity
BStandard
Timeline
2-3 weeks
Overview
Moving from Saleshiker to Nutshell is a shift from a WhatsApp-native CRM built for messaging-first teams to a conventional B2B CRM focused on account management and pipeline tracking. Saleshiker's data model centers on Leads, Contacts, Organizations, Deals, and Pipelines with a bundled WhatsApp Business API layer; Nutshell uses People and Accounts with a standard deal pipeline model. We migrate the standard CRM records and preserve associations, but WhatsApp broadcasts, Meta conversation billing state, chatbot configurations, and template approval statuses do not have equivalents in Nutshell and are not migratable. Saleshiker's Workflow engine definitions are also not portable; we deliver a written inventory of active Workflows and Schedulers so the customer's admin can plan rebuilding in Nutshell's automation features. The migration uses Nutshell's JSON-RPC API with rate-limit handling on find and get requests.
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 Saleshiker 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.
Saleshiker
Lead
Nutshell
People (Lead context)
1:1Saleshiker Leads map to Nutshell People records with the lead flag set. We preserve lead status, source attribution, owner assignment, phone number, and any custom properties. The original Saleshiker lead creation date transfers as a custom field for audit. If the destination Nutshell account uses People for both leads and contacts, we set a lead-specific flag field during import to distinguish from converted contacts.
Saleshiker
Contact
Nutshell
People
1:1Saleshiker Contacts map to Nutshell People records. We preserve name fields, email addresses, phone numbers, lifecycle stage values (mapped to Nutshell People fields or custom fields), and owner assignment. Lifecycle stage enum values from Saleshiker that have no direct Nutshell equivalent are stored in a custom text field for reporting continuity.
Saleshiker
Organization
Nutshell
Company
1:1Saleshiker Organizations map to Nutshell Companies. The organization's name, domain, industry, address fields, and any custom properties migrate directly. We resolve the contact-to-organization association during import by matching on the organization ID and creating the People-Company link in Nutshell's data model before the Contact phase completes.
Saleshiker
Deal
Nutshell
Deal
1:1Saleshiker Deals map to Nutshell Deals with pipeline stage, monetary value, expected close date, owner, and associated People and Company links preserved. The pipeline stage mapping is confirmed against a customer-provided table during scoping. Closed-Lost and Closed-Won statuses from Saleshiker map to Nutshell's win and loss states with the reason field carried over.
Saleshiker
Pipeline
Nutshell
Pipeline
lossyEach Saleshiker pipeline becomes a Nutshell Pipeline with its stage names preserved. Nutshell supports multiple pipelines from the Growth tier onward. We configure the stage order and probability percentages from Saleshiker into Nutshell's pipeline editor before Deal records are imported.
Saleshiker
Product
Nutshell
Product
1:1Saleshiker Products (name, SKU, price, description) map to Nutshell Products. Product codes and pricing migrate directly. If the destination uses Nutshell's built-in product catalog for quotes, we create the Price Book entries during the product import phase.
Saleshiker
Quote
Nutshell
Quote
1:1Saleshiker Quotes map to Nutshell Quotes attached to the corresponding Deal. Quote headers, line items, totals, and status transfer directly. If the quote references Products that have not yet been imported, we stage the product import before the quote import phase.
Saleshiker
Task
Nutshell
Task
1:1Saleshiker Tasks (title, due date, status, assignee, related-to linkage) map to Nutshell Tasks. Assignment resolves by matching Saleshiker owner email to Nutshell user email. Tasks linked to specific People, Companies, or Deals carry the relationship forward in Nutshell.
Saleshiker
Event
Nutshell
Event
1:1Saleshiker Events (title, start/end datetime, type, assignee) map to Nutshell Events. Recurrence patterns from Saleshiker are stored as a custom text field in Nutshell if the destination does not support native recurrence. Attendee associations migrate as EventRelation records in Nutshell.
Saleshiker
Attachment
Nutshell
File
1:1Saleshiker file attachments stored on Lead, Contact, Organization, and Deal records are downloaded from Saleshiker's storage, and the files are re-uploaded to Nutshell and linked to the corresponding People, Company, or Deal record. We preserve filename, file type, upload date, and uploader attribution during the re-link step.
Saleshiker
Workflow
Nutshell
Not Migrated
1:1Saleshiker Workflow definitions are not migratable. They reference internal WhatsApp trigger conditions and Saleshiker-specific action types that have no equivalents in Nutshell. We document every active Workflow and Scheduler in a structured inventory with trigger events, conditions, and action sequences so the customer's admin can rebuild them in Nutshell's automation rules or in a connected tool.
Saleshiker
WhatsApp Broadcast
Nutshell
Not Migrated
1:1WhatsApp broadcast history and Meta conversation state are governed by Meta's Business API and are not migratable to Nutshell, which has no WhatsApp integration layer. Broadcast records, message logs, chatbot configurations, and template approval statuses are excluded from the migration scope and flagged during the discovery call for admin awareness.
| Saleshiker | Nutshell | Compatibility | |
|---|---|---|---|
| Lead | People (Lead context)1:1 | Fully supported | |
| Contact | People1:1 | Fully supported | |
| Organization | Company1:1 | Fully supported | |
| Deal | Deal1:1 | Fully supported | |
| Pipeline | Pipelinelossy | Fully supported | |
| Product | Product1:1 | Fully supported | |
| Quote | Quote1:1 | Fully supported | |
| Task | Task1:1 | Fully supported | |
| Event | Event1:1 | Fully supported | |
| Attachment | File1:1 | Fully supported | |
| Workflow | Not Migrated1:1 | Fully supported | |
| WhatsApp Broadcast | Not Migrated1: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.
Saleshiker gotchas
Meta conversation billing applies on top of subscription cost
WhatsApp template approval governed by Meta policy
Workflow and automation definitions are not portable
Limited API documentation with no publicly documented rate limits
Invoice and payment data may reference internal accounting state
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 scoping
We audit the Saleshiker account for record counts across Leads, Contacts, Organizations, Deals, Pipelines, Products, Quotes, Tasks, Events, and Attachments. We identify active WhatsApp business phone numbers, active drip sequences, Workflow count and trigger types, and any custom fields or properties. We also confirm the Nutshell tier (Foundation through Enterprise) to validate that the destination supports the required features, such as multiple pipelines on Growth and above or custom fields on Pro and above.
Field mapping and pipeline configuration
We build the field mapping table mapping each Saleshiker object field to the equivalent Nutshell People, Company, Deal, or Product field by name and data type. Lifecycle stage values from Saleshiker Contacts are mapped to Nutshell custom fields if no direct equivalent exists. Each Saleshiker pipeline and stage becomes a Nutshell Pipeline with stage names and probabilities configured before Deals are imported.
Sample import and mapping validation
We run a sample migration into Nutshell using a subset of records per Nutshell's documented Import2 process. This validates that field mapping is correct, that People-Company associations resolve correctly, that Deal pipeline assignments map to the right Nutshell pipeline, and that attachment links attach to the correct records. The customer's admin reviews the sample and signs off before the full migration proceeds.
Data export from Saleshiker
We extract records from Saleshiker's API using paginated requests against the core objects. Attachments are downloaded to local storage with metadata preserved. Owner records are extracted for email-based matching against Nutshell users. We run a dry-run export to measure API responsiveness and adjust request throttling before the full export begins.
Full production migration in dependency order
We run production migration in dependency order: Companies (Organizations), People (Contacts and Leads), Products, Deals, Quotes, Tasks, Events, and Attachments. Each phase emits a row-count reconciliation report before the next phase begins. Owner resolution by email match happens before record imports; any Saleshiker owner without a matching Nutshell user goes to a reconciliation queue for the admin to provision.
Cutover and Workflow inventory delivery
We freeze writes in Saleshiker during cutover, run a final delta migration of any records modified during the window, and enable Nutshell as the system of record. We deliver the Workflow and Scheduler inventory document to the customer's admin for rebuild planning in Nutshell automation rules. We provide a one-week hypercare window for reconciliation issues. Workflow rebuilds, automation rebuilds, and admin training are outside standard migration scope.
Platform deep dives
Saleshiker
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 Saleshiker 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
Saleshiker: Not publicly documented.
Data volume sensitivity
Saleshiker 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 Saleshiker to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your Saleshiker 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 Saleshiker
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.