Migrate from Ascent360 to HubSpot

Ascent360 guest profiles map directly to HubSpot contacts. Each guest becomes one contact record with all profile properties preserved. Original create date, owner, and source system ID are carried over. Multi-channel preference flags (email, SMS, direct mail opt-in) map to HubSpot's contact property-level subscription fields.

Every segmentation dimension in Ascent360 (guest type, preference tags, visit frequency tier, loyalty tier) becomes a HubSpot custom property on the contact. Dynamic segmentation rules that Ascent360 evaluates at send time cannot be migrated — those rules export as reference documents for rebuilding as HubSpot active lists.

Ascent360 calculates guest lifetime value as a numeric score tied to historical spend and visit frequency. This value migrates to a HubSpot custom number property (Lifetime_Value__c) on the contact record. Any Ascent360 LTV tier classification (Bronze, Silver, Gold) maps as a value-mapped pick-list property.

Ascent360 tracks email sends, opens, clicks, SMS deliveries, and direct mail responses per guest. These migrate as HubSpot engagement activities on the contact timeline. Campaign attribution data (which campaign drove a booking) migrates as a custom property on the associated deal or contact record.

Ascent360 booking records contain booking ID, total spend, room type or product SKU, check-in date, nights stayed, and venue. These map to HubSpot deals with deal name derived from the booking ID, amount from total spend, close date from check-in, and custom properties capturing the remaining booking attributes. Each booking becomes one deal.

Ascent360 venues or properties where guests book or visit map to HubSpot companies. Business address, industry classification, and employee range are populated where available. Multi-location operators (ski resort, retail chain) get one HubSpot company per location with a custom location identifier property.

Ascent360 owner assignment per guest migrates to HubSpot's contact owner field. Owner resolution matches by email address against HubSpot user accounts. Unresolved owners are flagged before migration — teams either invite them to HubSpot or reassign records to a designated fallback owner.

Ascent360 workflows, automation sequences, and campaign templates do not have a HubSpot equivalent that preserves logic. FlitStack exports workflow definitions as reference documents so HubSpot admins can rebuild them. Marketing automation logic (enrollment triggers, delay actions, A/B split logic) requires manual rebuild in HubSpot's workflow builder.

Internal notes attached to guest profiles in Ascent360 migrate as HubSpot contact notes with original create timestamps and author preserved. Note associations to specific bookings or campaigns are captured as custom properties or linked via note timestamps. These notes remain searchable in HubSpot and can be enriched with contact-specific tags for better context.

Any custom fields defined in Ascent360 beyond the standard guest properties (industry-specific attributes like ski pass tier, dining preferences, room block history) migrate as HubSpot custom contact properties. FlitStack creates these as custom properties in HubSpot before the migration run so field mapping resolves on first import.

Ascent360 audience exports download as static lists in HubSpot. Dynamic segments in Ascent360 that recalculate on every send cannot migrate as live lists — FlitStack exports the filter criteria so HubSpot admins can build equivalent active lists using the same conditions.

Ascent360 attribution data (booking channel, referral source, campaign that drove acquisition) maps to a custom property on the contact. Attribution models with multi-touch complexity in Ascent360 cannot fully reproduce in HubSpot's attribution reporting without a separate attribution tool, but the source data migrates as a reference field.