CRM migration
Field-level mapping, validation, and rollback between Wetroo and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Wetroo
Source
Nutshell
Destination
Compatibility
5 of 8
objects map 1:1 between Wetroo and Nutshell.
Complexity
BStandard
Timeline
2-3 weeks
Overview
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.
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 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
Nutshell
Person (Nutshell CRM Contact)
1:1Wetroo 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
Nutshell
Person (Nutshell CRM Contact)
1:1Wetroo 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
Nutshell
Deal
1:1Wetroo 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
Nutshell
Pipeline
lossyWetroo 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
Nutshell
Pipeline Stage
lossyWetroo 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
Nutshell
Custom Fields
1:1Wetroo 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
Nutshell
User
1:1Wetroo 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
Nutshell
Teams
lossyWetroo'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.
| Wetroo | Nutshell | Compatibility | |
|---|---|---|---|
| Contact | Person (Nutshell CRM Contact)1:1 | Fully supported | |
| Lead | Person (Nutshell CRM Contact)1:1 | Fully supported | |
| Deal | Deal1:1 | Fully supported | |
| Pipeline | Pipelinelossy | Fully supported | |
| Pipeline Stage | Pipeline Stagelossy | Fully supported | |
| Custom Fields | Custom Fields1:1 | Mapping required | |
| Owner | User1:1 | Fully supported | |
| Teams | Teamslossy | 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.
Wetroo gotchas
No documented public API rate limits or quota structure
WhatsApp conversation history is not exportable from Wetroo
Automation sequences do not transfer 1:1 to destination CRMs
Support SLA and escalation paths are undocumented
Pricing page uses INR; annual discounts are tiered inconsistently
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 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.
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.
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.
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.
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.
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
Wetroo
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 Wetroo 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
Wetroo: Not publicly documented.
Data volume sensitivity
Wetroo exposes a bulk API — large-volume migrations stream efficiently.
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 Wetroo to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your Wetroo 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 Wetroo
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.