Migrate from Adaptix to Twenty CRM

Adaptix Contact records map 1:1 to Twenty Person objects. The email field on Contact becomes the email on Person and serves as the dedupe key during import. First name, last name, phone, and address fields migrate directly. All Adaptix Custom Properties on the contact record require pre-creation as typed custom fields in Twenty's Data Model before import begins.

Adaptix Company records map 1:1 to Twenty Company objects. The company domain becomes the website field. Company is imported before Person so that the relationship lookup between Person and Company is satisfied at the moment of Person insert.

Adaptix tags used for audience segmentation map to Twenty Labels. We export the full tag assignment table (contact ID to tag name) during discovery and reconstruct labels in Twenty's label system. Tag strategy is confirmed with the customer during scoping since Twenty's label model may require grouping or renaming to match the new taxonomy.

Adaptix Custom Properties on contacts vary per account and are not standardized. We flag every custom property during discovery, identify its data type, and pre-create matching custom fields in Twenty's Data Model under the Person object. Field types in Twenty include text, number, date, boolean, select, multi-select, and relation; we match type to the Adaptix property type before migration begins.

Adaptix company-level Custom Properties map to Twenty Company custom fields. Same pre-creation requirement applies. We configure field order, display labels, and picklist values (for select/multi-select types) in Twenty before loading any company records.

Adaptix tracks lead status and lifecycle stage as contact-level Custom Properties (e.g., lifecyclestage or custom stage fields) rather than a distinct object. We preserve these values in a custom field on the Twenty Person record for reporting continuity. We do not map to a separate Lead object unless the customer explicitly requests it during scoping.

Adaptix automation journeys are not exportable as executable workflows. We extract every active automation as a written reference template: trigger type, trigger conditions, each step's action, conditions, and delays, total journey length, and estimated rebuild complexity. This document is delivered as part of the migration handoff for the customer's admin to rebuild in their chosen automation layer post-migration.

Adaptix form definitions export as JSON (field names, types, consent settings). We package the JSON and flag every field that had a live automation trigger or tag-assignment action. Form field definitions require manual mapping to Twenty's form structure (or a third-party form tool) because Twenty does not include a native form builder in the base CRM.

Adaptix landing pages export as static HTML with embedded form markup. Dynamic connections to Adaptix's internal form handler, tag assignments, and automation triggers are severed on export. We package each page as an HTML asset with a separate documentation file listing every broken form-to-automation connection for manual reconstruction in the destination platform.

Adaptix audience segments are built from contact filter rules. We extract segment definitions (filter logic, conditions, operators) and contact membership lists separately. The filter logic is documented for manual rebuild in the destination; contact membership lists are delivered as CSV for bulk re-tagging if the destination supports it.

SMS consent status and opt-in records are tied to Contacts in Adaptix. We flag SMS consent fields explicitly during discovery and create matching boolean custom fields on the Twenty Person record. These fields are critical for compliance if the customer intends to continue SMS sending in any downstream platform, as consent state affects sending eligibility.

Adaptix tracks opens, clicks, sends, and automation events at the activity level. These are typically not exported as discrete records through Adaptix's standard export tools. We flag this as a known limitation during scoping and advise the customer that engagement activity history may require manual reconstruction in Twenty or a third-party engagement tool. We migrate what is available (standard contact properties with timestamps) and document the engagement history gap in the handoff report.