CRM migration
Field-level mapping, validation, and rollback between Wetroo CRM and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Wetroo CRM
Source
Nutshell
Destination
Compatibility
9 of 10
objects map 1:1 between Wetroo CRM and Nutshell.
Complexity
BStandard
Timeline
1-3 weeks
Overview
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.
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 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
Nutshell
People (Lead intake)
1:1Wetroo 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
Nutshell
People
1:1Wetroo 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
Nutshell
Company
1:1Wetroo 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
Nutshell
Lead (pipeline)
1:1Wetroo 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
Nutshell
Lead Pipeline Configuration
lossyWetroo'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)
Nutshell
Activity (Task)
1:1Wetroo 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)
Nutshell
Activity (Note/Task)
1:1Wetroo 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
Nutshell
Activity (Note)
1:1WhatsApp 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)
Nutshell
User
1:1Wetroo 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
Nutshell
Automation inventory (not migrated)
1:1Wetroo 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.
| Wetroo CRM | Nutshell | Compatibility | |
|---|---|---|---|
| Lead | People (Lead intake)1:1 | Fully supported | |
| Contact | People1:1 | Fully supported | |
| Company | Company1:1 | Fully supported | |
| Deal | Lead (pipeline)1:1 | Fully supported | |
| Pipeline and Stages | Lead Pipeline Configurationlossy | Fully supported | |
| Activities (Call Logs) | Activity (Task)1:1 | Fully supported | |
| Activities (Notes and Tasks) | Activity (Note/Task)1:1 | Fully supported | |
| WhatsApp Conversations | Activity (Note)1:1 | Mapping required | |
| User (Team Member) | User1:1 | Fully supported | |
| Drip Marketing Sequences | Automation inventory (not migrated)1:1 | Not 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.
Wetroo CRM gotchas
No official bulk-export endpoint complicates migration extraction
Drip sequences and automation logic are not exportable
Seat-tier limits can cause billing surprises during team migration
WhatsApp message history requires separate extraction
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 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.
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.
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.
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.
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.
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
Wetroo CRM
Source
Strengths
Weaknesses
Nutshell
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 3 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 CRM and Nutshell.
Object compatibility
3 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 CRM: Not publicly documented.
Data volume sensitivity
Wetroo CRM 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 Wetroo CRM to Nutshell migration scoping. Not seeing yours? Book a call.
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 consultationAdjacent paths
Other ways to leave Wetroo CRM
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.