Migrate from WayMore to Microsoft Dynamics 365 Sales

WayMore Contact records map to Dynamics 365 Contact. We extract via CSV from the WayMore dashboard contacts section, mapping standard fields (fullname, emailaddress1, telephone1, address) to typed Dataverse columns. Custom properties on Contact migrate as additional Dataverse columns created before import. The unsubscribed-contact flag from WayMore maps to emailaddress1optout on Contact to preserve CAN-SPAM and GDPR compliance at the destination.

WayMore Company records map to Dynamics 365 Account. The CSV export from WayMore includes company name, domain, address, and industry fields that map to the Account entity. We resolve the parent Account reference on each Contact at migration time by matching the company name or domain from the WayMore CSV against the newly created Account records before Contact insert to satisfy the CustomerId lookup.

WayMore does not have a native Opportunity object; revenue and pipeline data are tracked through Engagement records on Contact. We reconstruct Opportunities by extracting WayMore engagement records that represent sales interactions (such as deal-related notes, stage-change events, or custom deal-property records), grouping them by Contact and Company, and inserting them as Dynamics 365 Opportunity records with the Contact as the potentialcustomerid and the Account as the parentaccountid lookup. The original WayMore deal stage and amount values map to Opportunity stage and estimatedvalue.

WayMore Email Campaign records (subject, content, sending history) map to Dynamics 365 Campaign. The CSV export provides campaign metadata including subject, send date, and recipient count. Campaign records in Dynamics 365 serve as the parent container for marketing initiatives and link to Contacts via CampaignResponse or CampaignItem records. Actual delivery statistics and open rates are not available from WayMore's CSV export and are documented separately for the customer's admin to reference.

WayMore SMS campaign records and message templates export via CSV with opt-out status per contact. We map these to Dynamics 365 Campaign with the SMS channel designation and preserve the contact-level opt-out flag to maintain TCPA compliance. SMS-specific fields (message body, sender ID) store in custom Campaign fields since Dynamics 365 standard Campaign entity does not have a dedicated SMS body column.

WayMore custom properties on Contact and Company vary by account and export as additional CSV columns. We create typed Dataverse columns (text, integer, decimal, datetime, picklist, boolean) matching the WayMore property type during the pre-migration schema design phase. Type preservation is confirmed against the WayMore CSV header during extraction; dropdown-type custom properties become Dataverse picklist option sets with the original values replicated as options.

WayMore segments are dynamic rule-based lists that auto-update (e.g., contacts who visited page X more than twice). We export the current contact membership of each segment as a static snapshot at migration time. The snapshot is loaded into Dynamics 365 as a Marketing List with a custom field segment_name__c set to the segment name for each member Contact. The dynamic rule logic cannot be replicated in Dynamics 365 without Power Automate-based rebuilding, which is documented in the automation inventory deliverable.

WayMore automation workflows (triggers, conditions, delays, CRM actions) define customer journey behavior. We export the workflow definitions as structured JSON documentation covering step sequence, trigger type, conditions, and actions. The execution state, pending delays, and queued messages are lost at migration and cannot be transferred. We deliver a written workflow inventory with a recommended Power Automate equivalent for each active WayMore workflow. The customer's admin rebuilds in Power Automate post-migration; this is outside the data migration scope.

WayMore tags applied to contacts for labeling and segmentation export as additional columns in the Contact CSV. We map tag values to a Dataverse contact field, using a multi-select picklist if the tag set is small and bounded, or a text field if the tag vocabulary is large or open-ended. Tags serve as a reference dataset for the customer's admin to configure a permanent segmentation strategy in Dynamics 365.