Migrate from Ascent360 to Freshsales

Ascent360 guest Profiles map to Freshsales Contact for qualified guests (customers, members, past visitors) and to Freshsales Lead for new or unqualified contacts (inquiry-stage, event attendee). We use Ascent360's profile status, segment membership, and lifetime value to determine qualification. All standard fields (name, email, phone, company) map directly. Custom Profile Properties transfer to Freshsales custom fields on Contact or Lead, which we pre-create during schema design. Ascent360's daily enrichment data (last stay date, total spend, visit frequency) migrates as read-only derived fields in custom fields on the destination record.

Ascent360 enriches guest Profiles with address data sourced from PMS, POS, or direct input. This address populates Freshsales' standard address compound field (Street, City, State, Postal Code, Country). We normalize address formatting during transform to match Freshsales field structure. Direct mail campaign associations (which segment of a guest list is tied to a mail drop) are preserved as Tags on the Contact record.

Ascent360 Segments define audiences using criteria like purchase history, lifetime value tier, demographics, and preferences. Segment logic does not export as executable rules. We extract the full member list for each Segment and write each member-to-segment relationship as a Tag on the corresponding Contact or Lead record in Freshsales. For segments with complex multi-criteria logic, we document the segment definition and deliver a written guide for recreating the audience as a Freshsales filter-based view or dynamic list.

Ascent360 tags applied to Profiles for classification (loyalty tier, room preference, interests, source channel) migrate directly as Freshsales Tags on the Contact or Lead record. Tags are preserved intact so that sales and service teams can immediately filter by the same audience groupings used in Ascent360 marketing campaigns.

Ascent360 stores open rates, click rates, delivery rates, and conversion data per campaign. We extract this as a structured CSV export. Because Freshsales' native reporting covers pipeline and activity metrics rather than historical email campaign performance, we deliver the campaign metrics as an importable CSV mapped to a custom object (Campaign_History__c) with fields for campaign_name, send_date, open_rate, click_rate, and conversion. The customer's admin can connect this to Freshsales reports or maintain it as a reference sheet.

Ascent360's 150+ integrations (Shopify, WooCommerce, PMS systems, POS systems) are connection credentials, not data objects to migrate. We extract the integration name and last sync date for each connected source and record it as a custom field on the Contact (e.g., last_pos_sync__c, source_system__c) so that the service history of each guest record reflects where their data originated.

Ascent360 allows customers to define custom fields on Profiles. These fields are sometimes excluded from standard bulk export unless specifically requested. We run a pre-migration field audit against a sample export provided by Ascent360 to identify every active custom property. Each field is then pre-created in Freshsales with the matching field type (text, number, date, picklist, multi-select) before migration begins. Any missing fields in the initial export are flagged and a corrected export is requested from Ascent360 before we proceed to load.

Abandoned cart recovery campaigns in Ascent360 are tied to eCommerce integration events. The campaign automation logic does not export. We extract the event log (which contacts were in an active abandoned-cart flow at migration time) and record this as a custom field (abandoned_cart_date__c, abandoned_cart_value__c) or a timestamped Note on the Contact so that the sales team can follow up on uncompleted bookings. The customer rebuilds the abandoned-cart automation in Freshsales Workflows post-migration.