Migrate from ActiveTrail to Twenty CRM

ActiveTrail Contacts map directly to Twenty CRM Person records. Email address becomes the dedupe key. Subscription status, behavioral tags, and custom field values attach to the Person record. First name, last name, phone, and address fields map directly. The Person is created after any matching Company so that the Company relationship is satisfied at insert time.

ActiveTrail Contacts may carry a company name or domain association. We extract company affiliation from the contact record and either match it to an existing Twenty CRM Company or create a new one. The company's industry, size, and website fields map to the Company record if populated in ActiveTrail. If the contact has no company association, we flag it for the customer's admin to assign post-migration.

ActiveTrail custom contact fields (text, number, date, dropdown) map to Twenty CRM custom fields on the Person object. We create the custom field schema in Twenty CRM before migration, matching field types where possible. Dropdown fields require value-set mapping between ActiveTrail options and Twenty CRM picklist values.

ActiveTrail behavioral tags migrate as flat string assignments on the Person record. Where Twenty CRM supports native tagging, tags import as tag records. Where the customer prefers a structured field model, we map high-frequency tags to a multi-select custom field and flag the remainder for manual review.

ActiveTrail segments are dynamic contact groups built on filter conditions. The segment definition structure is exported as a rule-set document and delivered to the customer for manual rebuild in Twenty CRM. Static segments (hardcoded contact lists) can be exported as a contact list and imported as a Twenty CRM grouping if the customer requests it.

Automation journeys execute on a trigger-event basis tied to live contact data. We export journey definitions as dormant blueprints documenting trigger conditions, conditions, delays, and channel actions. These blueprints are delivered to the customer for rebuild in Twenty CRM's workflow model. Live-running state, enrolled contacts, and delay-timer positions do not transfer.

ActiveTrail email campaign metadata (name, subject, audience, send time, status) migrates as a written inventory record. HTML template content can be exported and delivered as brand assets for use in a new email marketing platform. Twenty CRM does not host email campaigns, so the campaign itself does not exist post-migration.

ActiveTrail SMS campaign metadata migrates as a written inventory record. SMS template content can be exported and delivered as brand assets. Phone number format normalization (E.164) is applied to all phone numbers during migration. Twenty CRM does not host SMS campaigns, so the campaign does not exist post-migration.

ActiveTrail email engagement history (subject, body, timestamp, open and click events) migrates as Note records attached to the Person. These appear as historical interaction records on the Person's activity timeline. They do not reflect as live campaign analytics in Twenty CRM's reporting dashboard.

ActiveTrail SMS engagement history migrates as Note records attached to the Person. Phone number format normalization (E.164) is applied. Engagement records do not appear as live SMS tracking in Twenty CRM.

Call engagement history from ActiveTrail migrates as Note records attached to the Person. Call duration and disposition notes are preserved if present. This appears as a historical note rather than a structured call log in Twenty CRM.

ActiveTrail landing pages built in the native builder are documented with their URL, form fields, and submission data. HTML or design assets are exported where available. Twenty CRM does not host landing pages; the customer selects a replacement landing page platform post-migration.