Migrate from Wetroo to Freshsales

Wetroo Contact records (name, phone, email, custom fields) map directly to Freshsales Contact. The phone number field migrates as a string to Freshsales' mobile phone field since Wetroo captures WhatsApp-sourced contacts with phone as the primary identifier. We apply Freshsales' email dedupe rule during import to prevent duplicate Contact records where the same email exists in both systems. Custom fields discovered on Wetroo Contacts are pre-created as Freshsales custom fields before migration begins.

Wetroo Lead records carry lead status, source attribution, and qualification scores from WhatsApp conversation qualification flows. We map Wetroo's lead_status property to Freshsales' Lead Status picklist and preserve any qualification score in a custom field wetroo_lead_score__c for the customer's sales team to reference post-migration. If the customer uses Freshsales' lead-to-contact conversion workflow, we configure the field mapping between Lead custom fields and Contact/Account/Deal fields per Freshsales' field mapping documentation.

Wetroo Deals map to Freshsales Deal with deal value, stage, owner, and associated contact preserved. The Wetroo dealstage property maps to Freshsales Deal Stage via a lookup table built during scoping, since Wetroo stage names are customer-defined and tied to WhatsApp workflow triggers. We recreate stage probabilities from Wetroo as Freshsales stage probability values where available. Closed-won and closed-lost dates migrate as Freshsales Deal close_date and updated_at timestamps.

Wetroo pipelines use custom stage names that vary per customer. We map each Wetroo pipeline to a Freshsales Deal Pipeline with stage names preserved as custom stage labels and the original stage order maintained. If a Wetroo pipeline has stages with no direct Freshsales equivalent, we create them as custom stage values within the Freshsales pipeline configuration before migration.

Wetroo supports custom fields on Contacts, Leads, and Deals discovered via API during scoping. We create equivalent Freshsales custom fields (using the Field API names from Wetroo where valid Freshsales field names are available) before any record import. Field types are mapped: Wetroo text fields become Freshsales text fields, picklist fields become dropdown fields, date fields become date fields. Multi-select fields in Wetroo map to Freshsales multi-select picklists where the destination field type is supported.

Wetroo Owner records (name, email) map to Freshsales User records by email match. We extract every distinct Owner referenced across Contact, Lead, and Deal records and generate a reconciliation report listing owners without a matching Freshsales User. The customer's admin provisions any missing Freshsales Users before the production migration phase begins, since OwnerId references are required on all three objects.

Wetroo automation playbooks are JSON-configured workflow triggers tied to WhatsApp events. We export playbook definitions (sequence names, trigger conditions, step actions) as a structured reference document delivered alongside the migration package. Freshsales Workflows must be rebuilt manually using Freshsales' visual Workflow builder since the trigger models are structurally different. We document each Wetroo playbook with its recommended Freshsales Workflow equivalent (e.g., a Wetroo stage-change trigger becomes a Freshsales Deal stage change Workflow trigger).

Wetroo per-owner pricing includes team membership (up to 20 teams per owner). We extract team names and member lists as a relational export and recreate them in Freshsales as Territories, which serve a similar organizational routing function. Team names and member emails are preserved in a custom field team_name__c on each User record for reference.