Migrate from Ascent360 to Twenty CRM

Ascent360 Profiles map directly to Twenty CRM Person records. The core profile fields — name, email, phone, address, and behavioral attributes — migrate 1:1 into Twenty's Person object fields. We run a pre-migration field audit against a sample export to surface all active custom Profile Properties before mapping; any properties missing from the initial export are flagged and a corrected export is requested from Ascent360. Ascent360's daily enrichment data (contact and behavioral attributes updated on a daily cadence) migrates as read-only derived fields in Twenty and may be stored as custom fields depending on the customer's data strategy.

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 extracting the list of Profile IDs associated with each Segment and applying those as Tag assignments on the migrated Person records in Twenty. We also create Filtered Views in Twenty that reproduce the segment criteria so the customer can see and maintain the audience logic without rebuilding from scratch. The customer chooses between tag-based and view-based audience reconstruction during scoping.

Open rates, click rates, delivery rates, and conversion data per campaign migrate as structured custom fields on Person records and as linked Comment records for audit trail. We preserve the campaign name, send date, and performance snapshot. Physical campaign assets (email HTML, SMS copy, direct mail design files) do not migrate; these are creative assets that belong to the customer and can be re-uploaded to their new email platform of choice.

Ascent360 allows customers to define custom fields on guest Profiles. These are not always visible in standard bulk exports. We surface all visible custom properties during discovery field audits and map each to Twenty's custom field framework using the /metadata API. Custom fields are pre-created in Twenty before any Person record import so that the schema is in place at the moment of insert. Any custom property that was excluded from the initial export is flagged and a corrected export is requested from Ascent360 before Person migration begins.

Ascent360 Profiles and Segments carry Tags for classification. We migrate tag assignments alongside Person records so audience groupings survive the transition intact. Tags are preserved as-is with no transformation, and the complete tag taxonomy is delivered as a reference document for the customer to audit and rationalize post-migration.

Abandoned cart recovery campaigns are specific to Ascent360's eCommerce integration events. The campaign automation logic does not export. We migrate the integration event log — the list of contacts who were in an active abandoned-cart flow — as custom fields on Person records (e.g., abandoned_cart_date, cart_value_at_abandonment, recovery_status) and as Activity records in Twenty's timeline. The customer's team rebuilds the automation logic in Twenty's workflow builder or a connected email platform.

Ascent360's direct mail channel uses enriched Profile address data. We migrate address data from enriched Profiles into Twenty's address fields on Person records. Physical mail assets (design files, print specs) are held assets and do not migrate; we deliver a list of active direct mail campaigns with the associated contact segment and address record count for the customer to reproduce in their print fulfillment tool of choice.

Ascent360's 150+ integrations are connection credentials to external systems (PMS, POS, eCommerce platforms). These are not data objects to migrate; they are credentials that must be re-established in Twenty or in a separate integration layer. We document every active integration during discovery, map the data fields flowing from each source, and deliver a connection plan for the customer to re-establish integrations post-migration. The integration event data (what was synced) is preserved in the Profile export; the connection itself must be rebuilt.

Ascent360 Campaigns include email and SMS content, timing, and channel assignments. Campaign template logic (Post-Stay, Birthday, Win-Back, Cross-Sell) does not export as portable objects. We migrate campaign performance history as Activity and Comment records in Twenty, and deliver a written campaign-rebuild guide listing every active campaign with its trigger conditions, audience logic, content type, and send schedule so the customer's admin can reproduce the campaign flow in Twenty's workflow builder or a connected email platform.

Ascent360 Automations (birthday emails, anniversary reminders, pre-arrival sequences, win-back flows) are platform-native workflows with no documented export mechanism. We do not migrate automations. We document every active automation during discovery, map the trigger conditions and audience logic, and deliver a written automation-rebuild guide as part of the migration package. The customer rebuilds automations in Twenty's workflow builder or connects a dedicated email marketing platform (such as Mailchimp, Klaviyo, or Attio) to handle the cadence layer.