CRM migration

Migrate from Wetroo CRM to Nutshell

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

Wetroo CRM logo

Wetroo CRM

Source

Nutshell

Destination

Nutshell logo

Compatibility

90%

9 of 10

objects map 1:1 between Wetroo CRM and Nutshell.

Complexity

BStandard

Timeline

1-3 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Moving from Wetroo CRM to Nutshell is a data extraction and re-platforming migration driven by Wetroo's lack of a documented bulk-export endpoint and its per-user seat-tier pricing that hard-caps team size. Wetroo organizes data around Leads, Contacts, Companies, Deals, and Activities tied to each record via its REST API using API-key authentication and paginated record retrieval; there is no bulk-export method for the primary CRM objects. We extract all migratable objects in dependency order (Contacts first, then Companies, then Deals, then Activities), map Wetroo Leads to Nutshell's People object, and preserve pipeline stage assignments and owner assignments by resolving Wetroo owner emails to Nutshell user emails. WhatsApp conversation threads are extracted from Wetroo's separate conversation API and loaded as Note records linked to the migrated People. Drip marketing sequences and automation cadences live in Wetroo's automation layer with no exportable schema and must be rebuilt in Nutshell manually; we deliver a written sequence inventory before cutover so your team can document logic while data is still live in Wetroo.

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 CRM logo

Wetroo CRM

What's pushing teams away

  • Small businesses outgrow the feature set when they need advanced reporting, custom objects, or enterprise-grade permissions beyond 20 users.
  • API documentation is minimal — developers building custom integrations or extraction pipelines hit walls quickly with no public schema reference.
  • Lead attribution and pipeline reporting are adequate but not deep; teams used to analytics-forward CRMs find the reporting surface limiting.
  • Customer support quality varies; some reviews report good experience while others cite responsiveness issues when problems arise at scale.

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

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

Lead

maps to

Nutshell

People (Lead intake)

1:1
Fully supported

Wetroo Lead records map to Nutshell People in the lead intake state. The Wetroo lead source property (Facebook, Google, manual, WhatsApp) maps to Nutshell's standard source field, and any custom lead-attribution fields migrate as custom People fields. Lead status values from Wetroo map to Nutshell's lead status pipeline. Once a Wetroo Lead converts in the destination, it moves through Nutshell's standard People lifecycle. If the customer uses Wetroo Leads that are already qualified contacts, we recommend migrating them directly as People rather than through the lead intake layer.

Wetroo CRM

Contact

maps to

Nutshell

People

1:1
Fully supported

Wetroo Contact records (enriched records after lead qualification) map directly to Nutshell People. Full contact details including phone numbers, email addresses, and lifecycle stage migrate. The primary challenge is that Nutshell People are singular contact records, so Wetroo Contacts with multiple assigned decision-makers may require a split into a primary People record plus additional linked People records. Custom fields on Wetroo Contacts map to equivalent Nutshell custom People fields that must be pre-created on the target account.

Wetroo CRM

Company

maps to

Nutshell

Company

1:1
Fully supported

Wetroo Company records map to Nutshell Company records. Company names, industry tags, billing address, and custom fields migrate directly. In Nutshell, People records are linked to a Company via the relationship field, so we resolve the Wetroo Contact-to-Company relationship during migration and set the People.Company reference at insert time. Address and billing data may require normalization if Wetroo stores them in non-standard formats.

Wetroo CRM

Deal

maps to

Nutshell

Lead (pipeline)

1:1
Fully supported

Wetroo Deal records map to Nutshell's Lead pipeline in Nutshell's standard CRM workflow. Deal value, expected close date, stage, and owner assignment migrate. Wetroo's pipeline stages are read via API during scoping and mapped to Nutshell's lead status values or a custom pipeline stage set if the customer configures one. Any custom deal fields migrate as custom fields on Nutshell's pipeline record.

Wetroo CRM

Pipeline and Stages

maps to

Nutshell

Lead Pipeline Configuration

lossy
Fully supported

Wetroo's pipeline configuration (stages, stage order, stage-specific probability values) is read from the API during discovery and configured in Nutshell before Deal migration begins. Stage names and relative order are preserved. If Wetroo has stage-specific fields (e.g., a custom loss reason or win reason field), we create equivalent fields in Nutshell and map values during import. Nutshell's pipeline stages are configurable per account without plan restrictions.

Wetroo CRM

Activities (Call Logs)

maps to

Nutshell

Activity (Task)

1:1
Fully supported

Wetroo OBD call records are extracted via the /api/v1/?apirequest=obd_record endpoint during extraction. Call duration, disposition, timestamp, and recording URL (if stored) map to Nutshell Activity records linked to the resolved People or Company. Call type is preserved as an activity sub-type. We resolve the owner by email match before inserting activities.

Wetroo CRM

Activities (Notes and Tasks)

maps to

Nutshell

Activity (Note/Task)

1:1
Fully supported

Wetroo Notes and Tasks migrate to Nutshell Activity records with the appropriate activity type. Note body content migrates as a Nutshell Activity with the note flag set. Task due dates, assignees, and completion status migrate directly. Automated reminders tied to Wetroo tasks cannot be migrated; these are flagged for manual recreation in Nutshell.

Wetroo CRM

WhatsApp Conversations

maps to

Nutshell

Activity (Note)

1:1
Mapping required

WhatsApp message threads are extracted from Wetroo's separate conversation API. Each thread is written as a Nutshell Activity record with message content, timestamps, sender/receiver, and conversation direction preserved. Media attachments (images, documents) require an additional download step and are re-attached to the Nutshell Activity as linked files. WhatsApp conversations are high-volume objects; we recommend scoping message history retention (e.g., last 12 months) during discovery to manage extraction time and Nutshell storage.

Wetroo CRM

User (Team Member)

maps to

Nutshell

User

1:1
Fully supported

Wetroo User records with name, email, role, and team assignment migrate by matching email to existing Nutshell users or provisioning new users in Nutshell before record migration. Team structures and sub-teams in Wetroo do not have a direct Nutshell equivalent; we flag team-to-role mapping during scoping and advise on whether to flatten the structure or recreate teams as Nutshell groups.

Wetroo CRM

Drip Marketing Sequences

maps to

Nutshell

Automation inventory (not migrated)

1:1
Not supported

Wetroo drip marketing sequences and sales automation cadences are stored in an automation layer with no exposed schema or export endpoint. We do not migrate them. During discovery we extract the sequence list (sequence names, step counts, contact counts, and step logic descriptions captured from the UI) and deliver it as a written inventory document. The customer's admin uses this inventory to rebuild sequences in Nutshell Automation (Pro tier) or Power tier's cadence tools.

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 CRM logo

Wetroo CRM gotchas

High

No official bulk-export endpoint complicates migration extraction

High

Drip sequences and automation logic are not exportable

Medium

Seat-tier limits can cause billing surprises during team migration

Medium

WhatsApp message history requires separate extraction

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 endpoint means extraction via paginated API only

    Wetroo exposes only two documented API endpoints: OBD call records and a webhook for lead creation. There is no bulk-export endpoint for Contacts, Companies, Deals, or Activities. We extract these records using paginated REST API calls with an API key, iterating through record pages to build the full dataset. This is slower than bulk export on platforms with proper export APIs. We test pagination limits during scoping to calibrate extraction timelines and flag any records that return incomplete or malformed data before migration begins.

  • WhatsApp message history requires a separate extraction layer

    WhatsApp conversation threads are stored in Wetroo's separate messaging API layer, distinct from the main CRM REST API. Media attachments within WhatsApp threads may require an additional download step. We extract message content, timestamps, and sender/receiver, but media files are downloaded separately and re-attached to Nutshell Activity records post-migration. Accounts with high WhatsApp volume (tens of thousands of messages) should scope message history retention during discovery to control extraction time and storage cost in Nutshell.

  • Drip sequences and automation logic cannot be migrated

    Wetroo's drip marketing sequences and automation rules are stored in an automation layer with no exposed schema or export endpoint. These cannot be migrated and must be rebuilt from scratch in Nutshell. We extract sequence names, step counts, contact assignments, and step descriptions from the Wetroo UI during discovery and deliver a written rebuild inventory. The customer's admin reconstructs the sequences in Nutshell Automation (Pro) or the cadence tool (Power) using the contact lists we export as the audience. Teams should document their sequences before migration begins.

  • Custom fields may require pre-creation in Nutshell before import

    Wetroo custom fields on Leads, Contacts, and Deals map to Nutshell custom fields, but the number of custom fields available is determined by the customer's Nutshell plan tier. We check custom field counts during scoping and advise if the current plan tier limits field creation. Custom fields with picklist or multi-select values require value-level mapping to ensure that Wetroo picklist codes resolve to the correct Nutshell picklist labels. We create the destination fields in Nutshell before any data is imported.

  • Nutshell's Lead vs People model requires scoping decision

    Nutshell separates People (existing contacts) from Leads (new intake). If the customer has a mix of unqualified and qualified contacts in Wetroo, we scope how to handle the split during discovery. Unqualified Wetroo Leads can map to Nutshell Leads; qualified Wetroo Contacts map to Nutshell People. If the customer does not use a formal lead qualification process in Wetroo, we recommend migrating all contacts as People to avoid the extra lead intake layer in Nutshell. This decision affects the migration mapping and is confirmed with the customer before extraction begins.

Migration approach

Six steps for a successful Wetroo CRM to Nutshell data migration

  1. Discovery and extraction calibration

    We audit Wetroo CRM via API across all active objects: Leads, Contacts, Companies, Deals, Activities, Users, and pipeline configuration. We test pagination limits on the Contact and Deal endpoints to calibrate extraction speed and estimate record counts. We also identify any custom fields, sequence assignments, and WhatsApp conversation volume. The discovery output is a written migration scope document with record counts per object, a pipeline stage mapping table, a custom field inventory, and a WhatsApp retention recommendation.

  2. Nutshell plan and schema preparation

    We assess the customer's Nutshell plan tier against the custom field count and automation requirements. If the plan tier limits custom field creation, we advise on upgrading before migration. We pre-create all required custom fields in Nutshell People, Company, and Lead objects, configure the pipeline stages to match Wetroo's pipeline configuration, and provision any missing Nutshell user accounts so that owner email resolution works at migration time.

  3. Sample migration and reconciliation

    We run a sample migration of 50-100 records per object type into the customer's Nutshell account using Import2's sample-first workflow. The customer reconciles field mapping, verifies that custom fields are populated correctly, and confirms that pipeline stage assignments match expectations. Any mapping corrections are applied before the full migration begins. This step prevents record rejection on the full load and reduces post-migration cleanup.

  4. Full data extraction and transformation

    We extract all Wetroo records in dependency order: People (Contacts) first, then Companies, then Deals, then Activities (calls, notes, tasks, WhatsApp messages), and finally Users. The Wetroo API pagination loop handles record pages with retry logic on rate-limit responses. WhatsApp conversations are extracted from the messaging API layer separately. We apply the pipeline stage mapping, custom field value mapping, and owner email resolution during the transform phase before loading into Nutshell.

  5. Production load and activity history migration

    We load data into Nutshell in dependency order via the Nutshell REST API. Activities (calls, notes, tasks) are loaded last after all parent People and Company records are confirmed in Nutshell, ensuring that activity-to-contact and activity-to-company lookups resolve correctly. WhatsApp conversation content loads as Activity records with media attachments linked. Each phase emits a row-count reconciliation report so the customer can verify record counts against the Wetroo source before proceeding to the next phase.

  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 drip sequence rebuild inventory to the customer's admin team with sequence names, contact counts, and step logic notes. We support a one-week hypercare window where we resolve any reconciliation issues. We do not rebuild Wetroo sequences as Nutshell automations inside the migration scope; that work is handled by the customer's admin using the inventory document.

Platform deep dives

Context on both ends of the pair

Wetroo CRM logo

Wetroo CRM

Source

Strengths

  • Native WhatsApp Business API channel gives sales teams a unified inbox for leads, follow-ups, and support without third-party middleware.
  • Meta Conversions API official partner enables direct CRM-to-Meta attribution without workarounds, optimising ad spend ROI.
  • Instant lead alerts from Facebook Lead Forms, Google Data Extractor, and manual entry reach reps on mobile within seconds of submission.
  • Free tier with unlimited alerts and no credit card requirement provides a genuine zero-cost starting point for very small teams or solo operators.
  • Visual canvas workflow builder lets non-technical users construct custom API-based integrations without writing code.

Weaknesses

  • No documented bulk-export endpoint means data extraction relies on paginated API calls and scripted access — bulk migration tooling is not officially supported.
  • Per-user pricing with hard seat caps on lower tiers (5 on Pro, 20 on Business) creates an immediate cost cliff when teams grow beyond the tier limit.
  • API documentation is sparse; the public reference at api.wetroo.com covers only two endpoints (OBD records and webhook lead creation), limiting what we can confidently extract.
  • Drip marketing sequences and sales automation cadences live in a separate automation layer with no exportable schema — they cannot be migrated and must be rebuilt manually.
  • English-language community presence and third-party support resources are thin compared to major CRMs, making troubleshooting harder for non-Hindi-speaking teams.
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. 3 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 CRM and Nutshell.

  • Object compatibility

    B

    3 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 CRM: Not publicly documented.

  • Data volume sensitivity

    B

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

Estimator

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

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

Can't find your answer?

Walk through your Wetroo CRM to Nutshell migration with a real engineer — 30 minutes, free, written quote within 24 hours.

Book a free 30 minute consultation

Migrations under 5,000 Contacts, 1,000 Companies, and 2,000 Deals with moderate WhatsApp volume (under 10,000 messages) typically complete in one to three weeks. Migrations with high WhatsApp volume, multiple custom fields, or complex pipeline configurations extend to three to five weeks. The Wetroo API extraction step (paginated REST calls rather than bulk export) adds time on the source side that depends on record volume and API response speed. Discovery and scoping add one to two weeks before extraction begins.

Adjacent paths

Related migrations to explore

Ready when you are

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