Migrate from Wetroo CRM to Salesforce Sales Cloud

Wetroo Lead records map directly to Salesforce Lead. The source attribution field (Facebook, Google, manual) preserves as a custom field for reporting. We apply a Lead-Contact split rule during scoping: if all Wetroo records are unqualified prospects, they migrate as Leads; if they are pre-qualified or have a Company association, they may be mapped directly to Contact under an Account. The original Wetroo record ID preserves as an external ID field for deduplication and audit.

Wetroo Contact records map to Salesforce Contact. Contact details (name, phone, email, address) migrate directly. The lifecycle stage property on Wetroo Contacts maps to a custom field hs_original_lifecycle__c for audit and reporting continuity. If a Wetroo Contact has an associated Company record, we resolve the AccountId at migration time by matching the Company name to the Account we created from the Wetroo Company record.

Wetroo Company records map to Salesforce Account. Company name becomes Account Name; industry tags and address data migrate to standard Account fields. Industry values require value-list mapping if Wetroo uses picklist values not present in Salesforce's industry picklist. Account records are created before Contact records so that the AccountId lookup is satisfied at the moment of Contact insert.

Wetroo Deal records map to Salesforce Opportunity. Deal value maps to Amount; expected close date maps to CloseDate; stage value maps to Salesforce StageName via a stage-mapping table built during scoping; owner assignment maps to Salesforce OwnerId via email-matched User records. Any Wetroo custom fields on Deal migrate as Opportunity custom fields with equivalent API names and data types.

Wetroo's single pipeline with configurable stages maps to a Salesforce Opportunity Record Type and corresponding Sales Process that whitelists the stage values. Stage order and names preserve; stage probability percentages migrate from Wetroo to Salesforce StageProbability, rounded to the nearest integer. If the customer requires multiple Salesforce pipelines later, additional Record Types are configured as a separate scope item.

Wetroo Activity records (calls, emails, meetings, tasks) map to Salesforce Task and Event objects. Task records carry the activity content and status; Event records carry meeting details with StartDateTime, EndDateTime, and Location. All Activity records require WhoId (Lead or Contact) and WhatId (Account or Opportunity) resolved at migration time via lookup against the migrated Contact and Opportunity records. Activities are the highest-volume migration object for most Wetroo accounts.

Wetroo OBD call records are extracted via the /api/v1/?apirequest=obd_record endpoint and map to Salesforce Task with TaskSubtype = Call. Call duration, disposition, recording URL (if stored in Wetroo), and timestamp migrate to custom Task fields. The WhoId links to the Contact resolved by the phone number on the call record. This is the only natively documented Wetroo data endpoint and serves as a reliable extraction anchor.

WhatsApp conversation threads extracted via Wetroo's conversation API map to Salesforce EmailMessage records with the MessagingType field set to WhatsApp. Message content, timestamps, sender, and receiver preserve. Media attachments require a separate download step and re-upload to Salesforce as ContentDocument records linked to the EmailMessage. This adds a step to the migration timeline for accounts with high WhatsApp volume.

Wetroo Task records map to Salesforce Task with Status, Priority, due date, and assignee preserved. Assignee resolution is by email match against the User mapping. Task records with no assignee migrate with the original owner noted in a custom field for reconciliation. Completed status maps directly; open tasks retain their due date relative to the migration cutover timestamp.

Wetroo Event records (meetings, appointments) map to Salesforce Event with StartDateTime, EndDateTime, Subject, and Location preserved. Attendee lists map to EventRelation records pointing at the resolved Contact, Lead, or User. If Wetroo stores attendee email addresses rather than Contact IDs, we resolve them against the migrated Contact records by email match.

Wetroo custom fields on Leads, Contacts, Companies, and Deals are mapped to Salesforce custom fields created before migration begins. Custom field type mapping: Wetroo text fields map to Salesforce Text fields; picklist fields map to Salesforce Picklist or Multi-Select Picklist; date fields map to Date fields. Custom field API names are created with __c suffix per Salesforce convention. Value-list mapping is required for picklist fields where Wetroo uses values not present in Salesforce's standard picklists.

Wetroo User records (team members) map to Salesforce User by email match. We extract every distinct user referenced on Leads, Contacts, Deals, and Activities and reconcile against the destination org's User table. Users without a matching Salesforce User go to a reconciliation queue for the customer's admin to provision before record import resumes. Team structure and role data map to Salesforce Role hierarchy where applicable.