Migrate from Act-On to Twenty CRM

Act-On Contact records map directly to Twenty Person records. Standard fields (first name, last name, email, phone, job title) map cleanly. We preserve lifecycle stage, source, and any custom contact-level properties as custom fields on the Person object. The Person record is created before any related Opportunity or Task imports so that lookups are satisfied at insert time.

Act-On Company records map to Twenty Company records. Company name, industry, website, employee count, and annual revenue migrate directly. Custom company fields from Act-On's schema become Twenty custom fields. We use the company domain as a deduplication key and resolve the Company-to-Person relationship during Person import.

Act-On Lists are audience segments used for campaign targeting. We export List membership as tag data on the Person record, with one tag per List membership (e.g., tag: Newsletter_Q4, tag: Enterprise_Leads). The customer chooses during scoping whether List logic (dynamic vs static) is noted as a reference for manual segmentation rebuild in Twenty's table views and filters.

Act-On Automated Programs define multi-step nurture sequences stored server-side and are not accessible via API for export. We export all Contact data within a Program (who entered, when, what branch they took, what actions fired) as a timestamped reference dataset. We deliver a written Program inventory with each sequence's steps, triggers, conditions, and actions mapped to Twenty's Workflow builder as a blueprint for manual rebuild.

Act-On's Custom Data schemas define user-extended field structures on Contacts and Companies. We read the schema definition via API, export existing records, and create equivalent custom fields in Twenty's Data Model. If the schema defines a standalone custom object (not linked to Contact or Company), we create a Twenty custom object with matching field types and relationships before data import.

Act-On calculates a behavioural engagement score per contact using proprietary weighting rules across email opens, clicks, page visits, and form submissions. These calculation rules do not export. We migrate the current numeric score as a custom field (e.g., acton_engagement_score__c) on the Person record and flag that the customer must configure any new scoring logic manually in Twenty using custom formula fields or an integration with an external scoring service.

Act-On email content, subject lines, and send history are accessible via API. We migrate send events as Task records on the Person record with a custom type field (acton_email_task__c), timestamp, subject line, and a link back to the original email content stored in our migration artifact archive. HTML template content is preserved as a reference document for the customer to rebuild in their preferred email sending tool post-migration.

Web forms in Act-On capture leads with custom field definitions. Form field schemas migrate as custom fields on the Person object. Submission data migrates as historical records. The form embed code does not transfer and must be re-implemented in Twenty or a third-party form tool (Typeform, JotForm, or similar) post-migration.

Act-On logs email opens, clicks, form submissions, and other behavioural events. We export activity history as timestamped Task records linked to the Person record. Volume can be large; we chunk by date range and apply backoff logic. We flag high-volume activity exports (>100,000 records) during scoping as a cost driver because API pagination and chunking add time.

Contact and company tags export cleanly as label arrays. We map them directly to Twenty's tag model on Person and Company records. Tags used for marketing classification migrate as-is; tags used for lead scoring are noted separately since scoring logic does not transfer.