Migrate from Wetroo to Twenty CRM

Wetroo Contact records (name, phone, email, custom fields) map directly to Twenty's People object. We extract via the Wetroo contact list API endpoints and map to Twenty's firstName, lastName, and email fields. Phone numbers preserve with country code stored in the phone field. Custom fields on Contact migrate as custom fields on People via Settings → Data Model after schema discovery. Owner resolution maps Wetroo owner email to Twenty user email for assignment.

Wetroo Leads captured through WhatsApp conversations and qualified via lead qualification workflows map to Twenty People for unqualified prospects and to Opportunities for qualified leads ready for pipeline entry. We extract lead records including lead status, source, and qualification score from Wetroo's API and preserve these in Twenty custom fields (lead_status__c, lead_source__c, lead_score__c). The customer chooses the qualification threshold during scoping.

Wetroo Deals tied to pipeline stages map to Twenty Opportunities. We extract deal records including associated contact (resolved to People ID), deal value (amount), stage (mapped to Opportunity stage), and owner. Deal values migrate to Opportunity amount. If the deal has a close date, it maps to Opportunity closeDate. Wetroo's per-deal custom fields migrate as Twenty Opportunity custom fields.

Wetroo pipelines use customer-defined stage names tied to WhatsApp workflow triggers. We map Wetroo stage names to Twenty Opportunity stage values during migration. The original stage sequence and names are preserved in a custom field wetroo_original_stage__c on each Opportunity for audit. Stage probability percentages from Wetroo are stored in a custom field wetroo_stage_probability__c if the customer used them.

Stage order and naming are customer-defined in Wetroo. We preserve the original sequence as a custom field and map to Twenty's Opportunity stage picklist. Any stages with no direct Twenty equivalent are flagged for the customer to confirm replacement values. Stage-level WhatsApp trigger logic (a Wetroo-specific concept) cannot map to Twenty and is documented separately as automation requiring rebuild.

Wetroo assigns an Owner to each Deal and Lead. Owner records include name and email. We map Wetroo owners to corresponding Twenty user accounts by email match. Any Wetroo owner without a matching Twenty user goes to a reconciliation queue for the customer to provision before record import resumes. Users must be provisioned in Twenty BEFORE importing Deals that reference them.

Wetroo supports custom fields on Contacts, Leads, and Deals. We discover custom field definitions via the Wetroo API before migration, include them in the field mapping phase, and recreate them in Twenty via Settings → Data Model before importing any records. Custom fields must exist in Twenty before CSV import runs; they are not auto-created by the import process. Field types map as follows: text to text, number to number, date to date, checkbox to boolean, picklist to select.

Wetroo's per-owner pricing includes team assignment with up to 20 teams per owner. Team membership records are extracted as a relational export but Twenty does not have a native team/group concept with the same semantics. We export team names and member lists as a structured reference document. The customer recreates team structure in Twenty manually using Workspace settings or custom fields if team-based filtering is required.

WhatsApp conversation history and chat transcripts are stored in WhatsApp's own infrastructure, not Wetroo's database. They are not accessible via the Wetroo API or any export mechanism. We preserve all structured Contact, Lead, and Deal records that originated from conversations, but the conversation history itself cannot be transferred. Customers requiring chat history should export directly from WhatsApp before the migration cutover. This is a data loss boundary that must be communicated explicitly before scoping begins.

Wetroo's automation playbooks and sequence triggers are JSON-configured workflows tied to WhatsApp events. They do not map to Twenty's workflow builder format without manual reimplementation. We export sequence names, trigger conditions, and step definitions as a structured reference document delivered alongside the migration package. The customer rebuilds automations in Twenty's workflow builder. Note: Twenty's native sequencing (email/call cadences) is not yet available as of 2026 per Reddit r/CRM community discussion.