CRM migration

Migrate from Wetroo to Nutshell

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

Wetroo logo

Wetroo

Source

Nutshell

Destination

Nutshell logo

Compatibility

63%

5 of 8

objects map 1:1 between Wetroo and Nutshell.

Complexity

BStandard

Timeline

2-3 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Moving from Wetroo to Nutshell is a migration from a WhatsApp-embedded, Indian-market CRM to a US-based SMB CRM with transparent per-user pricing and built-in marketing, automation, and reporting. Wetroo exports its structured records (Contacts, Leads, Deals) through API calls or manual CSV dumps with no bulk-data UI, which means scoping must confirm whether the customer's export scope captures all custom fields and owner assignments. WhatsApp conversation history is not accessible via any export path and must be retained in WhatsApp itself. Wetroo pipeline stages are customer-defined and tied to WhatsApp workflow triggers; we preserve the original stage sequence as a custom field in Nutshell and map to Nutshell's pipeline stage values during import. Automation playbooks, team structures, and per-owner pricing records require field-level mapping and are delivered as reference documents for manual reimplementation. We do not migrate workflows, WhatsApp templates, or sequences as code.

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

Wetroo logo

Wetroo

What's pushing teams away

  • Multiple reviews report the software contains persistent glitches that degrade reliability and disrupt daily sales workflows.
  • Support response times averaging 2–3 days create friction when production issues arise, with users describing slow ticket resolution.
  • Missing or inadequate MIS and reporting features prevent teams from getting a clear pipeline overview, driving users toward platforms with stronger analytics.
  • WhatsApp automation can get stuck without resolution, and users report inability to get working fixes from the support team.
  • Limited notification options and missing workflow controls force teams to build manual workarounds that reduce the value of the automation claim.

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

Each row shows how a Wetroo 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.

Wetroo

Contact

maps to

Nutshell

Person (Nutshell CRM Contact)

1:1
Fully supported

Wetroo Contact records (name, phone, email, custom fields) map to Nutshell Person. Phone number from Wetroo maps to Nutshell's phone field; email maps to email. We discover all Wetroo custom fields on Contact via the API before migration and recreate them as Nutshell custom fields of equivalent type. Wetroo's WhatsApp-originated contact source flag migrates as a Nutshell custom field.

Wetroo

Lead

maps to

Nutshell

Person (Nutshell CRM Contact)

1:1
Fully supported

Wetroo Lead records (captured via WhatsApp conversation qualification workflows) map to Nutshell Person. Lead status, source attribution, and qualification score from Wetroo migrate as Nutshell custom fields. If the customer's Wetroo instance uses lead status values, we map them to Nutshell's person status field or create a custom status field.

Wetroo

Deal

maps to

Nutshell

Deal

1:1
Fully supported

Wetroo Deals map to Nutshell Deal. Deal value, associated contact, owner, and stage migrate directly. We map the Wetroo dealstage property to Nutshell pipeline stage, and pipeline assignment maps to a Nutshell pipeline that we configure before import. Wetroo's custom deal fields migrate as Nutshell custom fields.

Wetroo

Pipeline

maps to

Nutshell

Pipeline

lossy
Fully supported

Wetroo pipelines use customer-defined stage names tied to WhatsApp workflow triggers. We preserve the original pipeline and stage names as a Nutshell custom field for audit, then configure Nutshell pipeline stages to match the original sequence and probability weights. Stages with no direct Nutshell equivalent are flagged for customer review before import.

Wetroo

Pipeline Stage

maps to

Nutshell

Pipeline Stage

lossy
Fully supported

Wetroo stage order and names are customer-defined. We preserve the original stage sequence and names as a custom field on the Nutshell Deal record, then map to Nutshell's standard stage values (Qualification, Presentation Scheduled, Decision Maker Bought-In, Contract Sent, Closed Won, Closed Lost) with stage probabilities carried forward. Stage mapping is validated against Wetroo's export before import.

Wetroo

Custom Fields

maps to

Nutshell

Custom Fields

1:1
Mapping required

Wetroo supports custom fields on Contacts, Leads, and Deals. We discover custom field definitions via the API before migration, map types to Nutshell equivalents (text, number, date, dropdown, checkbox), and create the fields in Nutshell before any record import. Fields that exist in Wetroo with no Nutshell equivalent are flagged for custom field creation.

Wetroo

Owner

maps to

Nutshell

User

1:1
Fully supported

Wetroo assigns an Owner to each Deal and Lead. Owner records include name and email. We extract all distinct Wetroo owners and match by email against Nutshell Users. Owners without a matching Nutshell User are held in a reconciliation queue for the customer's admin to provision before record import resumes. Active Wetroo owners become active Nutshell users; inactive Wetroo owners become inactive Nutshell users.

Wetroo

Teams

maps to

Nutshell

Teams

lossy
Mapping required

Wetroo's per-owner pricing includes team assignment. Team membership records (team name and member list) are extracted as a relational export and mapped to Nutshell Teams. Nutshell Teams are available on the Growth plan ($25/user) and above. If the customer is on a lower Nutshell tier, we flag team membership as a custom field on the Person record instead.

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.

Wetroo logo

Wetroo gotchas

High

No documented public API rate limits or quota structure

High

WhatsApp conversation history is not exportable from Wetroo

Medium

Automation sequences do not transfer 1:1 to destination CRMs

Medium

Support SLA and escalation paths are undocumented

Low

Pricing page uses INR; annual discounts are tiered inconsistently

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

  • Wetroo WhatsApp conversation history cannot be exported

    Wetroo stores conversation metadata and chat transcripts in WhatsApp's infrastructure rather than its own database. When migrating out of Wetroo, the actual chat threads are not accessible via the Wetroo API or any export mechanism. We preserve all structured records (Contacts, Leads, Deals) that originated from conversations, but the conversation history itself must be retained in WhatsApp. Customers should export critical chat history directly from WhatsApp before the migration cutover if a record of conversations is required. This is a platform-level limitation that affects any migration out of Wetroo, not a pair-specific issue.

  • Wetroo API has no published rate limits

    Wetroo's API reference does not publish rate limits or quota thresholds. When we run migration exports against Wetroo's API, we cannot preemptively throttle requests to stay within safe limits, which risks hitting undocumented throttling that stalls or fails an in-progress extraction. We monitor HTTP 429 responses during extraction and apply exponential backoff dynamically, but we advise customers to schedule extraction during off-peak hours and to prepare for a longer-than-expected extraction window if throttling is encountered.

  • Wetroo automation sequences do not map to Nutshell automation

    Wetroo's automation playbooks are configured as JSON-based workflow triggers tied to WhatsApp events. The logic, triggers, delays, and conditions do not map to Nutshell's automation format. We export the playbook definitions as a structured reference document with sequence names, trigger conditions, and step definitions, but the customer must rebuild automations in Nutshell's automation suite or with their marketing and ops team. Nutshell's automation features (included on Growth and Pro plans) use a different event model and must be reconfigured from scratch.

  • Wetroo stage nomenclature requires manual mapping review

    Wetroo pipeline stages are customer-defined and tied to WhatsApp workflow triggers. There is no standard stage naming convention we can reference for Wetroo instances. During scoping, we pull the actual stage names from the customer's Wetroo export and present them for customer review before we configure Nutshell's pipeline stages. Stages that have no intuitive Nutshell equivalent (e.g., stages named for specific WhatsApp message templates) require customer input on the appropriate replacement stage. Skipping this review step results in mismatched stage assignments post-migration.

  • Wetroo per-owner team structures do not map to Nutshell team roles

    Wetroo's per-owner pricing model includes team assignment where the owner manages up to 20 teams. This structure is a Wetroo-specific billing and organization concept that does not map directly to Nutshell's team concept (which is an access and sharing model on Growth+ plans). We preserve team membership records as a custom field on the Nutshell Person record, but the billing relationship between owner and team members is not recreated in Nutshell because Nutshell uses per-user licensing instead of per-owner. Customers should review their Nutshell user count against their Wetroo owner count during planning.

Migration approach

Six steps for a successful Wetroo to Nutshell data migration

  1. Discovery and export scoping

    We audit the Wetroo instance via API and manual export to identify Contact, Lead, Deal, and Pipeline record counts; custom field definitions on each object; owner assignments; team structures; and automation playbook inventory. We confirm whether the customer's Wetroo export scope includes all relevant custom fields and owner records, and we advise on any gaps. We also confirm the Nutshell plan the customer has selected or plans to select, since Teams are available only on Growth and above.

  2. Destination schema design and pipeline configuration

    We design the Nutshell schema before any data import. This includes creating custom fields on Person and Deal to capture Wetroo-specific properties (WhatsApp contact source, original stage names, lead qualification score); configuring Nutshell pipelines and stages to match Wetroo's stage sequence and probability weights; and mapping owner emails to Nutshell Users. We deploy the schema into the customer's Nutshell instance and validate the pipeline configuration before record import begins.

  3. Sample extraction and mapping validation

    We run a sample extraction of 50-100 records from Wetroo (Contacts, Leads, Deals) and import them into a test Nutshell environment. The customer reviews the mapped records for accuracy, confirms the stage mapping, and validates that custom fields populated correctly. Any mapping corrections (field type mismatches, missing fields, stage alignment issues) happen at this stage before production migration begins.

  4. Owner reconciliation and user provisioning

    We extract every distinct Wetroo Owner referenced on Deal and Lead records and match by email against the Nutshell destination's User table. Owners without a matching Nutshell User go to a reconciliation queue. The customer's Nutshell admin provisions any missing Users (active or inactive based on whether the original Wetroo owner is still active in the sales team). Migration cannot proceed past this step because Owner assignments are required on Deal records.

  5. Production migration in dependency order

    We run production migration in record-dependency order: Nutshell Users (validated), People (Contacts and Leads from Wetroo), Companies (extracted from Wetroo Company records or created from contact domain data), Deals (with Person link, Owner assignment, and Pipeline stage resolved), and Custom Fields (populated on each record). Automation playbook definitions and team membership records are delivered as structured export documents alongside the migration. Each phase emits a row-count reconciliation report before the next phase begins.

  6. Cutover, validation, and automation rebuild handoff

    We freeze Wetroo writes during cutover, run a final delta migration of any records modified during the migration window, then enable Nutshell as the system of record. We deliver the automation playbook inventory document to the customer's admin team with step-by-step descriptions for rebuilding Wetroo playbooks in Nutshell's automation suite. We support a one-week hypercare window where we resolve any data quality issues raised by the sales team. We do not rebuild Wetroo automations in Nutshell as part of the migration scope; that is a separate configuration engagement.

Platform deep dives

Context on both ends of the pair

Wetroo logo

Wetroo

Source

Strengths

  • WhatsApp-native CRM positions chat as the primary sales channel, not an add-on integration.
  • Per-owner pricing is predictable and scales without per-seat cost increases.
  • Mobile apps on iOS and Android extend full pipeline access to field teams.
  • Built-in automation templates reduce configuration time for non-technical users.
  • 24/7 support is included on all plans with published CSAT metrics.

Weaknesses

  • Software stability concerns cited across multiple reviews — glitches and reliability issues affect daily workflows.
  • Support responsiveness averaging 2–3 days lags behind competing CRM platforms.
  • Reporting and MIS features are insufficient for teams requiring detailed pipeline analytics.
  • API documentation is minimal and publicly undocumented, limiting custom integration options.
  • WhatsApp-specific automation can fail silently without adequate alerting or recovery mechanisms.
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 Wetroo 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

    Wetroo: Not publicly documented.

  • Data volume sensitivity

    A

    Wetroo exposes a bulk API — large-volume migrations stream efficiently.

Estimator

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

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

Can't find your answer?

Walk through your Wetroo 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, 2,000 Deals, and a straightforward pipeline structure. Migrations with multiple custom fields, large owner and team structures, or post-migration pipeline reconfiguration move to four to six weeks. Wetroo's undocumented API and absence of bulk-export tooling add extraction time that is factored into scoping but can extend the overall timeline if throttling is encountered during extraction.

Adjacent paths

Related migrations to explore

Ready when you are

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