Migrate from ActiveDEMAND to Twenty CRM

ActiveDEMAND Contacts map to Twenty CRM People. Standard fields (first name, last name, email, phone) map 1:1. Brand Custom Fields attach as custom fields on the Person object after we export the per-account field schema and recreate it in Twenty's Settings → Data Model before import. Community assignment from ActiveDEMAND's multi-tenant structure maps to a custom People field or tag depending on the destination's community architecture.

ActiveDEMAND Company records map to Twenty CRM Company. Company name, domain, address fields, and industry map directly. The Company-to-Person relationship is preserved as a link in Twenty's Company detail view. Deduplication uses company name and domain as the matching key during import.

ActiveDEMAND Campaigns (email, funnel, multi-channel) do not have a direct Twenty CRM equivalent. We export campaign membership per Contact as a Tag assignment on the Person record (campaign name as tag value), and create a Task record per campaign with the campaign name, type, start date, and status as a reference note. The customer's admin rebuilds campaigns as Opportunity pipelines or grouping tags in Twenty post-migration.

ActiveDEMAND Call Tracking records (source number, destination number, duration, recording URL, linked Contact) map to Twenty CRM Task with a custom call subtype field. We preserve the recording URL as a URL field on the Task, call duration as an integer field, and the caller Contact link via Twenty's Person lookup. The original call timestamp becomes the Task due date to preserve activity ordering.

ActiveDEMAND website chat conversations export as structured conversation metadata and message text. We create a Twenty CRM Note linked to the Person record with conversation timestamp, visitor identifier, and message thread content in the Note body. If the conversation references a Company, we link the Note to the Company as well. Chat sentiment or rating data maps to a custom Note field if configured in Twenty.

ActiveDEMAND Appointments (date, time, status, linked Contact, community reference) map to Twenty CRM Task with title set to the appointment description, due date set to the original appointment date, and status set from ActiveDEMAND appointment status. Community reference from the Senior Living model maps to the custom community field on the Person record already established in the Contact mapping step.

ActiveDEMAND Contact Lists and Segments are static lists of Contact IDs. We export the full list membership, then create Tag assignments on each Person record in Twenty for every list the Contact belongs to. This preserves segment membership without requiring a separate List object in Twenty.

ActiveDEMAND Brand Custom Field schemas vary per account and must be exported before any Contact data export. We export the full field schema (field name, type, picklist options) and reproduce equivalent custom fields in Twenty's Settings → Data Model. The data export follows the schema recreation so that field values land in the correct destination fields rather than defaulting or being silently dropped.

ActiveDEMAND Owners map to Twenty CRM workspace users by email match. Owners without a matching Twenty user enter a reconciliation queue for the customer's admin to provision before Person import begins. Owner assignment on Contacts, Companies, and Call Tracking records resolves to the Twenty User ID at migration time.

ActiveDEMAND Workflow definitions are complex JSON structures with trigger-delay-action branching. We do not migrate workflows as code. We deliver a written inventory of every active ActiveDEMAND Workflow with its name, trigger conditions, step count, and action types for the customer's admin to rebuild in Twenty v2.0 Workflows or document manually in the new platform.

ActiveDEMAND Forms and their field definitions export as structured data with HTML/CSS preserved as attachment references. Field-level mapping is required because form field names diverge between platforms. We deliver a form inventory with field mappings and the original form body content for manual reassembly in Twenty or a replacement form tool.