Migrate from Ascent360 to Pipedrive

Ascent360 guest Profiles migrate 1:1 to Pipedrive People. The guest's first name, last name, email, phone, and address fields map directly to Pipedrive's name, email, phone, and address fields. Custom Profile Properties are audited during discovery against a sample export; any missing from the initial file are flagged and a corrected export is requested before mapping finalizes. Historical enrichment data (loyalty tier, visit frequency, total spend) migrates as custom fields on the Person record.

Ascent360 segments define audiences using criteria like lifetime value, purchase history, demographics, and preferences. Segment logic does not export as executable rules. We reconstruct audience membership by exporting each segment's contact list and applying the members as tag assignments in Pipedrive. Customers choose between tags (simple classification) or Pipedrive's filtered views (saved searches) based on the number of segments and how they are used day-to-day. Multi-condition segments split into multiple tags for granular use.

Ascent360 tags migrate directly to Pipedrive tags on the Person record. Tags serve as the fastest path to rebuilding segment-based views in Pipedrive without rebuilding the underlying segment criteria. We preserve the original tag names so that Pipedrive filtered views can reference them consistently.

Ascent360 campaigns include email and SMS content, timing, and channel assignments. Campaign content does not export as portable objects. We migrate campaign metadata (name, start/end dates, channel type, associated segment) and document the channel and audience for the customer to reference during rebuild. Pipedrive does not have native campaign management; teams typically use a separate email marketing tool (Mailchimp, HubSpot Marketing Hub) or Pipedrive's Smart Email Campaigns feature (Professional tier).

Open rates, click rates, delivery rates, conversion data, and revenue attribution per campaign are exported from Ascent360 as a structured data file. We deliver this file formatted for manual import into Pipedrive's reporting layer (as custom fields on Person or as a separate Analytics connection). Historical campaign performance does not map to a native Pipedrive object, so this data requires the customer to decide how to surface it post-migration.

Automated sequences (birthday emails, anniversary reminders, pre-arrival campaigns, win-back flows, abandoned cart recovery) are platform-native workflow objects with no documented export mechanism. We do not migrate automations. We document every active automation during discovery with its trigger conditions, audience logic, message content summary, and send-time rules, then deliver this as a written rebuild guide. Pipedrive has no native automation engine; customers select and configure a separate workflow tool post-migration (ActiveCampaign, HubSpot, or a native Pipedrive automation partner).

Ascent360 supports direct mail as a campaign channel alongside email and SMS. Physical mail assets and address delivery management are Ascent360-native features. We migrate the enriched address data from guest Profiles (which survives the contact migration), but Pipedrive has no direct mail capability. This channel gap is documented in the handoff so the customer can select a standalone direct mail platform if omnichannel campaigns continue to be a requirement.

Ascent360 custom fields on guest Profiles (loyalty tier, room preferences, ski pass type, equipment rental history) migrate as Pipedrive custom fields on the Person object. Custom fields are pre-created in Pipedrive with appropriate field types (text, number, date, picklist, checkbox) before migration begins. Multi-select picklists from Ascent360 become Pipedrive multi-select custom fields. Fields are audited against the initial export to catch any that Ascent360 omitted from the standard export format.

Ascent360's 150+ integrations with PMS, POS, eCommerce, Spa, and Golf systems are connection credentials to external platforms, not data records. The integration event log (booking events, purchase events, check-in/check-out) does not migrate as a structured object. We migrate the resulting guest data and behavioral attributes that Ascent360 derived from these integrations, but the integrations themselves are not transferred. Pipedrive integrations are configured separately post-migration based on the customer's current stack.

Abandoned cart recovery is an Ascent360 campaign type tied to eCommerce integration events. The campaign automation logic does not export. We flag which contacts were in an active abandoned cart sequence at migration time and record this status as a note or custom field on the Pipedrive Person so the customer's sales or service team can follow up. Pipedrive does not have native abandoned cart recovery; this use case requires a separate marketing automation tool.