Migrate from Ascent360 to Nutshell

Ascent360 Profiles are the unified contact record, aggregating identity across PMS, POS, eCommerce, Spa, and Golf systems. We map Profiles 1:1 to Nutshell Person records, preserving standard fields (name, email, phone, address) and enrichment data appended by Ascent360's daily processing as read-only derived fields in a custom field or the notes section. A pre-migration field audit against a sample export identifies all active custom Profile Properties before mapping, since these are sometimes excluded from standard bulk exports.

Ascent360 Profile records may carry organizational affiliation or company-level data depending on the customer's data model. We extract company-level fields (business name, industry, website) and create corresponding Nutshell Company records, then link the Person record via Nutshell's person-company relationship. This mapping requires identifying which Profile fields represent organizational identity versus individual guest identity.

Ascent360 Segments define audiences using criteria like purchase history, lifetime value, demographics, and preferences. Segment logic does not export as executable rules. We reconstruct audience membership by exporting the list of Profile IDs within each Segment and applying those as Tag assignments on the corresponding Nutshell Person records. Customers rebuild segment logic in Nutshell using filtered People lists or workflow-triggered audience building; the tag assignments provide the starting membership state.

Open rates, click rates, delivery rates, and conversion data stored per campaign in Ascent360 migrate as a structured export. We load this performance history into Nutshell as a series of Activity records with campaign name and metric type in the description, or as a custom Campaign Performance object if the customer configures one. This preserves reporting continuity but does not restore the campaigns themselves.

Automated nurture sequences are stored as platform-native workflow objects with no documented export mechanism. We do not migrate automations. We deliver a written inventory of every active automation during discovery, documenting the trigger conditions, audience logic, message sequence, and delay steps. Nutshell's workflow management (rated important by 85% of Capterra reviewers who use it) serves as the rebuild target. Customers rebuild these in Nutshell using Nutshell's automation builder.

Ascent360's omnichannel delivery includes direct mail alongside email and SMS. Address data derives from enriched Profiles and migrates into Nutshell's standard address fields on the Person record. Physical mail assets (design files, print-ready artwork) are not data objects and are not migrated; we flag their presence in Ascent360 so the customer can locate and preserve them separately.

Profiles and Segments in Ascent360 can carry tags for classification. We migrate tag assignments alongside Person records so that any existing audience groupings, preference flags, or segmentation labels survive the transition intact. Nutshell Tags are a flat label system on Person records.

Ascent360 allows customers to define custom fields on Profiles. These are not always visible in bulk exports and require a targeted field audit to surface. We identify all active custom properties, map each to an equivalent Nutshell custom field (on Person or Company depending on whether the field applies to the individual or the organization), and handle any type differences (Ascent360 multi-select or date fields map to Nutshell equivalent field types). This is the highest-risk step in the migration and is addressed before any record import begins.