CRM migration

Migrate from Saleshiker to Nutshell

Field-level mapping, validation, and rollback between Saleshiker and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.

Saleshiker logo

Saleshiker

Source

Nutshell

Destination

Nutshell logo

Compatibility

92%

11 of 12

objects map 1:1 between Saleshiker and Nutshell.

Complexity

BStandard

Timeline

2-3 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

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

Saleshiker logo

Saleshiker

What's pushing teams away

  • Very limited public review presence makes it hard to assess real-world reliability, support responsiveness, and long-term viability before committing.
  • WhatsApp template approval by Meta can delay or block message campaigns if templates violate Meta's policies, with no recourse through Saleshiker.
  • Conversation-based billing from Meta adds unpredictable costs on top of the subscription price, which is not clearly disclosed on the pricing page.
  • Fewer integrations than established CRMs—WooCommerce, Google Sheets, Zapier, and Zoho only—limits connectivity to broader sales and marketing stacks.

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 Saleshiker objects map to Nutshell

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

maps to

Nutshell

People (Lead context)

1:1
Fully supported

Saleshiker 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

maps to

Nutshell

People

1:1
Fully supported

Saleshiker 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

maps to

Nutshell

Company

1:1
Fully supported

Saleshiker 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

maps to

Nutshell

Deal

1:1
Fully supported

Saleshiker 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

maps to

Nutshell

Pipeline

lossy
Fully supported

Each 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

maps to

Nutshell

Product

1:1
Fully supported

Saleshiker 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

maps to

Nutshell

Quote

1:1
Fully supported

Saleshiker 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

maps to

Nutshell

Task

1:1
Fully supported

Saleshiker 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

maps to

Nutshell

Event

1:1
Fully supported

Saleshiker 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

maps to

Nutshell

File

1:1
Fully supported

Saleshiker 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

maps to

Nutshell

Not Migrated

1:1
Fully supported

Saleshiker 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

maps to

Nutshell

Not Migrated

1:1
Fully supported

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

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.

Saleshiker logo

Saleshiker gotchas

High

Meta conversation billing applies on top of subscription cost

Medium

WhatsApp template approval governed by Meta policy

Medium

Workflow and automation definitions are not portable

Low

Limited API documentation with no publicly documented rate limits

Low

Invoice and payment data may reference internal accounting state

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

  • WhatsApp broadcast history and Meta billing state do not migrate

    Saleshiker's WhatsApp broadcasts, message logs, conversation timestamps, chatbot flows, and Meta template approval statuses are governed by Meta's Business API and have no equivalent data model in Nutshell. Nutshell does not have a WhatsApp integration layer. We flag active WhatsApp business phone numbers during scoping, document any campaigns in flight, and exclude broadcast records from the migration. The customer should retain a Saleshiker read-only export for audit purposes if historical WhatsApp logs are required.

  • Saleshiker Workflows and Schedulers are not portable to Nutshell

    Saleshiker's Workflow engine stores trigger-action logic referencing WhatsApp events, message templates, and drip sequence states that do not map to any Nutshell automation construct. Nutshell's automation rules use different trigger types (record changes, date-based, form submissions) without WhatsApp event awareness. We do not migrate Workflow definitions. We deliver a written inventory of every active Workflow and Scheduler with its trigger conditions, action sequences, and a recommended Nutshell automation replacement path.

  • Meta conversation billing flags in Saleshiker have no Nutshell equivalent

    Saleshiker tracks conversation-based billing state from Meta that affects which contacts are flagged for WhatsApp billing. This metadata is Saleshiker-specific and does not carry over to Nutshell's per-user model. Any billing or cost-allocation logic that relies on Saleshiker's Meta conversation metadata requires manual reconstruction post-migration. We flag any records that reference active WhatsApp business phone numbers for customer awareness.

  • Nutshell API uses JSON-RPC with rate limits on find and get requests

    Nutshell's API uses JSON-RPC over HTTPS at app.nutshell.com/api/v1/json, with rate limits applied to find operations (non-stub responses) and get requests. We throttle find requests incrementally, probe for rate limit responses during the dry-run, and chunk large record sets into batches to stay within Nutshell's throughput. Import2 is used for the sample migration phase per Nutshell's documented import process, and the full migration runs via the JSON-RPC API for control over mapping and validation.

Migration approach

Six steps for a successful Saleshiker to Nutshell data migration

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

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

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

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

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

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

Context on both ends of the pair

Saleshiker logo

Saleshiker

Source

Strengths

  • WhatsApp-native CRM with integrated Business API access
  • No-code chatbot builder for automated lead qualification
  • Shared team inbox for WhatsApp conversations
  • Bulk WhatsApp broadcast and drip marketing automation
  • Mobile app for iOS and iPad with real-time data access

Weaknesses

  • Minimal public review presence limits visibility into real customer experiences
  • Meta conversation charges create variable billing outside the stated subscription price
  • Limited integrations restrict connectivity to other business tools
  • Workflow definitions are not portable across CRM platforms
  • No Wikipedia article or independent analyst coverage to validate long-term roadmap
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 Saleshiker 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

    Saleshiker: Not publicly documented.

  • Data volume sensitivity

    B

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

Estimator

Estimate your Saleshiker 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 Saleshiker to Nutshell data migrations

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

Can't find your answer?

Walk through your Saleshiker 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 under 5,000 Contacts and 1,000 Deals with a single pipeline and no quotes or custom fields. Migrations with multiple Saleshiker pipelines, quote records, large attachment volumes (over 500 files), or custom field-heavy schemas move to three to six weeks because of pipeline configuration, quote line-item mapping, and file re-upload steps.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Saleshiker.
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