Migrate from Wetroo to Salesforce Sales Cloud

Wetroo Contact records with no lead qualification status map to Salesforce Lead; Contacts with an associated deal value or stage assignment map to Salesforce Contact tied to an Account. We compute the split using Wetroo's lead status and deal association properties at migration time, and preserve the original Wetroo contact status in a custom field wetroo_contact_status__c on both Lead and Contact for audit and reporting continuity.

Wetroo Lead records (captured through WhatsApp conversations and qualified via Wetroo's lead qualification workflows) map directly to Salesforce Lead. Lead source, qualification score, and status properties migrate to custom Salesforce Lead fields so that the original qualification routing logic is preserved as reference data for the customer's Salesforce admin to re-implement in Flow if needed.

Wetroo Company records map directly to Salesforce Account. The company name becomes Account Name, and any stored domain or website property becomes the Website field used as the dedupe key. Account is created before any Contact or Lead import so that the AccountId Lookup relationship is satisfied at the moment of Contact insert, preventing orphaned Contact records without a parent Account.

Wetroo Deals map to Salesforce Opportunity. Deal value maps to Amount, contact association maps to the primary ContactId on Opportunity, and owner assignment maps to OwnerId via email resolution against Salesforce Users. Closed-won and closed-lost deal outcomes from Wetroo map to Salesforce StageName values that we configure as part of the sales process design.

Wetroo pipelines use customer-defined stage names tied to WhatsApp workflow triggers. We map each Wetroo pipeline to a Salesforce Record Type on Opportunity, and create a corresponding Sales Process that whitelists the migrated stage values. Stage probability percentages migrate from Wetroo to Salesforce StageProbability fields. Any Wetroo stage with no direct Salesforce equivalent is flagged during scoping for the customer to confirm the target stage value.

Wetroo stage order and naming are customer-defined and not tied to a standard nomenclature. We preserve the original stage sequence and names as a custom field wetroo_original_stage__c on the Salesforce Opportunity for audit purposes, then map the stage names to Salesforce StageName values using the agreed mapping table created during scoping. Probability weights attached to each stage migrate as StageProbability values.

Wetroo supports custom fields on Contacts, Leads, and Deals. We discover all custom field definitions via the Wetroo API before migration, include them in the field mapping phase, and recreate them on the corresponding Salesforce object before record import begins. Field types are mapped to equivalent Salesforce field types (text to Text, number to Number, date to Date, picklist to Picklist). Custom field API names receive the __c suffix per Salesforce convention.

Wetroo assigns an Owner to each Deal and Lead. Owner records include name and email. We map Wetroo owners to corresponding User email addresses in the Salesforce destination org. Any Wetroo owner without a matching Salesforce User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Active and inactive status on the destination User controls whether the migrated records appear under an active or deactivated owner.

Wetroo's per-owner pricing includes team assignment with up to 20 teams per owner. Team membership records are extracted as a relational export and re-created in Salesforce as a combination of Salesforce Groups (for team-based sharing) and a custom multi-select picklist field on the User or Contact object storing the team names. This preserves the team structure without a direct Salesforce analog.

Wetroo automation playbooks and sequence triggers are JSON-configured workflows tied to WhatsApp events. We export sequence names, trigger conditions, and step definitions as a structured reference document for the customer's ops team to rebuild in Salesforce Flow. The playbook definitions do not map to Salesforce Flow format without manual reimplementation, and no automation logic transfers automatically.

Wetroo stores conversation metadata and chat transcripts in WhatsApp's infrastructure rather than its own database. Chat threads 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 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.

Where Wetroo records structured call, email, meeting, or task activity linked to a Contact or Deal, we migrate those as Salesforce Task (with TaskSubtype for calls) or Event records linked via WhatId to the Opportunity and WhoId to the Contact or Lead. Activity timestamps are preserved as ActivityDate. This mapping applies only to structured activity records stored in Wetroo's database, not WhatsApp chat threads.