Migrate from Ascent360 to Microsoft Dynamics 365 Sales

Ascent360 guest Profiles map directly to Dynamics 365 Contact records. The guest's primary address, email, phone, and demographic fields map to standard Contact fields. We resolve the contact's associated property or organization as an Account lookup, creating the Account record first during migration. Daily enrichment fields appended by Ascent360 migrate as read-only custom fields with a data-origin note indicating the Ascent360 enrichment date.

Ascent360 Segments define audiences using criteria like lifetime value, stay history, preferences, and demographics. Segment logic does not export as executable rules. We reconstruct audience membership by exporting the segment-to-profile membership list and populating a custom multi-select picklist field on Contact (segment_membership__c) with each segment name. For complex behavioral segments, we create a custom Dataverse entity (GuestSegmentMembership) with a Contact lookup and segment attributes for flexible querying.

Profile-level tags migrate as comma-separated values in a custom Contact field (ascent360_tags__c) or as Dynamics 365 Topics with TopicAssignment records linked to Contact. The customer chooses the tagging strategy during scoping. Tags used for preference classification (ski pass holder, spa member, bike rental frequent user) map to descriptive topic names for quick filtering in Dynamics views.

Ascent360 stores open rates, click rates, delivery rates, and conversion data per campaign. These metrics have no direct Microsoft Dynamics 365 Sales standard object equivalent. We create a custom CampaignMetrics Dataverse entity with fields for campaign_name, send_date, open_rate, click_rate, delivery_rate, and conversion_rate, and link it to the associated Contact record via a custom lookup. We also attach a formatted summary as a Note on the Contact for quick reference in the Dynamics timeline.

Ascent360 allows customers to define custom fields on Profiles that are sometimes excluded from standard bulk exports. We run a pre-migration field audit against a sample export to identify all active custom properties, then create matching custom fields in the Dataverse Contact schema before migration begins. Field data types are inferred from Ascent360's field definitions and mapped to the nearest Dataverse field type (string to single-line text, numeric to whole or decimal number, boolean to two-option).

Physical mailing addresses stored on Ascent360 guest Profiles migrate to the standard Dynamics 365 Contact address fields (address1_line1, address1_city, address1_stateprovince, address1_postalcode, address1_country). We validate address completeness during the transform phase and flag records with missing postal codes for customer review before insert.

Ascent360's 150+ integrations are connection credentials to external systems, not migratable data objects. The behavioral events captured from those integrations (stay history, purchase history, booking events) that exist as enriched data on the Profile migrate as records in a custom Dataverse entity (GuestActivityLog) with a Contact lookup and event-type, event-date, and source-system fields. This preserves the behavioral record without migrating integration credentials.

Abandoned cart events captured from Ascent360's eCommerce integration migrate as AbandonedCartEvent records in a custom Dataverse entity linked to Contact. The campaign logic triggering recovery emails does not migrate — we document the event log and flag which contacts were in an active abandoned-cart flow at migration time so the customer's Dynamics admin can rebuild the recovery sequence in Power Automate.

Automated nurture sequences (birthday emails, anniversary reminders, pre-arrival campaigns, win-back flows) are stored as platform-native workflow objects with no documented export mechanism. We do not migrate automations. We deliver a written automation-rebuild guide during migration that documents every active automation's trigger conditions, audience logic, delay steps, and CRM actions with recommended Power Automate equivalents and the Microsoft Dynamics 365 Sales Insights sequence approach.