Migrate from Actito to Twenty CRM

Actito Profiles map directly to Twenty People. Standard attributes (email, name, phone, address) migrate as typed fields. Custom profile attributes inspect their data type during scoping and map to Twenty's equivalent field type (text, number, date, boolean, or picklist). We preserve the Actito profile identifier in a custom field actito_profile_id__c for audit traceability.

Actito Companies (if the licence includes a company attribute on Profile) map to Twenty Companies. Domain becomes the Company website. Address attributes migrate to the Billing Address block. The Company record is created before any Person import so the companyId relationship resolves at insert time.

Actito Custom Tables connected to Profiles via relationships migrate to Twenty Custom Objects with equivalent field definitions. We inspect the table schema during scoping, map field types to Twenty equivalents, and recreate the lookup relationships as Twenty field references. Custom table naming convention follows Twenty's API naming rules during schema creation.

Actito Entities partition all resources (data structures, campaigns, scenarios) within a licence. Twenty has workspaces but no entity equivalent. We preserve entity names and scope assignments as workspace-filtered views or as a category field on the Person record, and deliver a written map of which entities map to which views for the customer's admin to configure post-migration.

Profile-level opt-in and preference data migrates as structured fields on the Twenty Person record. We create boolean fields for each active subscription channel (email_optin, sms_optin, push_optin) and a multi-select picklist for preference categories. Double opt-in status and consent timestamps migrate to dedicated date and boolean fields for GDPR audit readiness.

Actito campaign configurations (name, schedule, targeting criteria, channel assignment) do not have a direct functional equivalent in Twenty. We migrate campaign metadata as Opportunity records named after the Actito campaign, with channel type stored in a picklist field and targeting criteria preserved in a long-text notes field for the admin to reference when rebuilding campaign logic manually in Twenty's activity model.

Actito Scenarios are event-triggered automation workflows with multi-step branching, delays, and channel actions. Twenty has no native scenario or workflow engine. We map scenario logic (trigger conditions, branching rules, action steps) to a written task checklist that the customer's admin uses to recreate the automation logic in their chosen external tool or as a manual process. We do not migrate Scenarios as functional code.

Actito channel configurations (sender addresses, DKIM/SPF records, template references) are destination-specific and cannot be transferred. We migrate the template content as a Note attached to the Person record and flag DNS authentication records (DKIM public key, SPF TXT record) that must be reconfigured in the customer's email sending infrastructure before activation in Twenty.

Actito campaign interaction events (opens, clicks, bounces, unsubscribes) generated during campaign execution migrate as Twenty Activity records linked to the Person. The event type (email_open, email_click, sms_delivered, unsubscribe) maps to a Task or Note with a category field, preserving the timestamp and campaign reference. We note that historical reporting will reflect Twenty data only from the go-live date forward.

Actito Export API job definitions (file naming patterns, scheduling, compression type) map to Twenty CSV import configurations. We document the original export schedule and recreate the equivalent import configuration in Twenty's UI for any recurring imports the customer maintains.

Actito segment-building rules and Profile selection criteria migrate to Twenty view filters. Complex Actito-specific operators (such as 'is last month' or behavioural event windows) translate to Twenty filter expressions where equivalent operators exist. Operators without a Twenty equivalent are flagged in the mapping document for manual recreation.