Migrate from Wetroo CRM to Microsoft Dynamics 365 Sales

Wetroo Lead records map directly to Dynamics 365 Lead. Lead source attribution (Facebook, Google, manual) from Wetroo's source tracking fields migrates to Dynamics 365 Lead's leadsourcecode and a custom field wetroo_lead_source__c. Custom properties on Wetroo Leads are mapped to equivalent Dynamics 365 attributes or stored as custom fields on the Lead entity. Unqualified Leads remain as Lead until a sales rep qualifies them and runs the Convert action in Dynamics 365 to create the associated Contact and Account.

Wetroo Contacts (qualified leads after the initial intake) map directly to Dynamics 365 Contact. Full contact details, phone numbers, email addresses, and lifecycle stage status migrate. Since Dynamics 365 requires a Contact to be associated with an Account, we resolve the parent Company from Wetroo and link the Contact to the corresponding Dynamics 365 Account during import. Any standalone Contacts without a Wetroo Company association are held in a reconciliation queue for the admin to resolve before import.

Wetroo Company records map to Dynamics 365 Account. Company name, industry, and address data migrate directly. Billing and shipping address fields from Wetroo map to the Dynamics 365 Account address fields; note that Dynamics 365 allows one primary address per purpose (Invoice, Delivery) per Account, which may require consolidation if the Wetroo source had multiple addresses per Company. Custom fields on Company migrate to custom fields on Account.

Wetroo Deal records map to Dynamics 365 Opportunity. Deal value (amount), expected close date, and owner assignment migrate directly. The Wetroo pipeline stage name maps to the corresponding Dynamics 365 Opportunity StageName; we configure the sales process and stage values in Dynamics 365 before migration so that the stage mapping is deterministic. Deal-custom field values migrate to Opportunity custom fields.

Wetroo pipeline configurations (stage names, stage order, stage probabilities) are read from Wetroo's API and replicated in Dynamics 365 as Sales Processes and Stage values. For accounts using Wetroo's multi-pipeline feature on Business tier, each Wetroo pipeline becomes a Dynamics 365 Record Type on Opportunity, with its own Sales Process and Page Layout scoped to the relevant stage values. Stage probabilities are rounded to the nearest integer allowed by Dynamics 365.

Wetroo OBD (outbound dialer) call records are extracted via Wetroo's /api/v1/?apirequest=obd_record endpoint. Each call record maps to a Dynamics 365 Task with TaskSubtype = Call. Call duration, disposition, and recording URL are preserved in custom Task fields. Activity timestamp is set to the original Wetroo call timestamp to maintain the activity timeline ordering. Owner of the call activity is resolved via the Wetroo user email match to the Dynamics 365 User.

WhatsApp conversation threads are stored in Wetroo's separate messaging API layer. We extract message content, timestamps, sender/receiver, and media attachment metadata. Since Microsoft Dynamics 365 Sales has no native WhatsApp channel, message content is surfaced as EmailMessage records (for threaded display in the activity timeline) or as Note records attached to the Contact or Lead. Media files are downloaded separately and reattached to the EmailMessage or Note in Dynamics 365. This step adds a discrete extraction pass beyond the standard contact and deal migration.

Wetroo task records (due date, assignee, status) map to Dynamics 365 Task with Status, Priority, and ActivityDate preserved. Event records (meetings, appointments) map to Dynamics 365 Event with StartDateTime, EndDateTime, and Location. Event attendee data maps to EventRelation records linking the Event to the relevant Contact, Lead, or Account participants.

Custom fields on Wetroo Leads, Contacts, Companies/Accounts, and Deals are mapped to equivalent Dynamics 365 custom fields. Picklist and multi-select values require explicit value-list mapping since Wetroo and Dynamics 365 maintain separate option sets. Multi-select picklists in Wetroo migrate to Dynamics 365 multi-select option set fields. Any Wetroo custom fields without a clear Dynamics 365 equivalent are flagged in the scoping report for the customer to decide whether to create a custom field or drop the attribute.

Wetroo user records (name, email, role, team assignment) are extracted and matched by email address against the destination Dynamics 365 User table. Any Wetroo user without a matching Dynamics 365 User is placed in a reconciliation queue; the customer's Dynamics 365 admin provisions the missing Users before production migration begins. Migration cannot complete past record import until all OwnerId references are resolvable, since Dynamics 365 requires a valid OwnerId on all standard entities.