Migrate from Ascent360 to Mailchimp

Ascent360 Profiles (the unified guest record aggregating PMS, POS, and eCommerce identity) map 1:1 to Mailchimp Members within an Audience. Standard fields (email, first name, last name, phone, address) map to their Mailchimp equivalents. We obtain the export from Ascent360 via their support team, resolve email deduplication (Ascent360 may have multiple addresses per Profile), and load Members via Mailchimp's Members API endpoint. Profiles without a valid email address are excluded and reported separately.

Ascent360 Segments define audiences using criteria like purchase history, lifetime value, stay frequency, and demographic properties. Segment logic does not export as executable rules, but the membership list (the set of Profile IDs in each Segment) does export. We extract each Segment's member list, resolve the corresponding email addresses, and apply Tags in Mailchimp matching each Segment name. The customer rebuilds the segment logic in Mailchimp's Segments builder using the migrated tags as the criteria base. Active Segment-to-campaign assignments are documented for the admin to reassign post-migration.

Tags and labels assigned to individual Profiles (for classification, preference tracking, or behavioral flags) migrate directly as Mailchimp Tags. We extract tag assignments per Profile from the Ascent360 export and apply them to the corresponding Member in Mailchimp. Tags used for content classification (e.g., room type, activity preference, booking channel) map to Mailchimp Tags that can then drive segmentation in Mailchimp's Segments tool.

Ascent360 allows customers to define custom fields on Profiles (e.g., loyalty tier, total lifetime spend, property visited, ski pass type). These fields are not always visible in Ascent360's standard bulk export, so we run a pre-migration field audit against a sample export to surface all active custom properties. Each custom property is then mapped to a Mailchimp Merge Field, with field type conversion applied: text properties map to Mailchimp TEXT (capped at 255 characters per Mailchimp's limit), date properties map to DATE, and numeric properties map to NUMBER. Any custom property exceeding 255 characters is flagged during scoping and truncated with a note in the migration report.

Ascent360 stores open rates, click rates, delivery rates, and conversion data per campaign. This historical performance data exports as a structured table. We deliver this as a structured CSV alongside the Member migration so the customer's admin can reimport performance history into Mailchimp's reporting layer or a connected BI tool. Mailchimp does not accept historical engagement metrics (open/click on historical sends) via API, so the performance data serves as a reference document rather than native Mailchimp reporting data.

Ascent360 includes address data on enriched Profiles used for direct mail campaigns. Address fields (street, city, state, postal code, country) map to Mailchimp's ADDRESS merge field type. Physical mail assets (design files, print specs) do not migrate; we document the address structure and campaign associations so the admin can coordinate physical mail reactivation with a print vendor independently.

Ascent360's 150+ integrations (PMS, POS, eCommerce) generate behavioral event data on Profiles (e.g., last stay date, total spend, booking channel). These events are stored as derived data on the Profile rather than as standalone objects. We extract key behavioral event values as merge field data or as tags on the Member record, flagging the source system for each behavioral attribute. This allows Mailchimp's segmentation to reference original purchase behavior even though the full integration event log is not migrated as a separate object.

Ascent360 campaign records include email/SMS content, timing, and channel assignments, along with a template library for Post-Stay, Birthday, Win-Back, and Cross-Sell campaigns. The campaign content does not export as portable HTML. We document every active campaign (name, channel, trigger logic, audience association, send history) as a written record. The customer's admin uses Mailchimp's built-in templates and automation builder to recreate the campaign logic. We do not migrate campaign HTML as a deliverable.