Migrate from Actimo to Twenty CRM

Actimo People map 1:1 to Twenty CRM People records without requiring object-level transformation. Standard fields including first name, last name, email address, phone number, job title, and company association transfer directly from Actimo to Twenty. Custom properties defined on the Actimo Person object must be pre-created as custom fields in Twenty via Settings → Data Model before the import begins, ensuring field name and type compatibility throughout the migration run.

Actimo Companies map directly to Twenty CRM Companies with no intermediate transformation step. Standard fields including company name, domain or website URL, industry classification, employee count, and complete address components (street, city, country) transfer as-is. The Actimo internal company identifier is preserved in a custom text field (source_system_id__c) on the Twenty Company record to maintain traceability and support delta-run de-duplication on subsequent migration passes.

Actimo's contact-to-company relationship (where one contact can belong to one primary company) maps to the Twenty companyId lookup relation on the People object. Since Twenty enforces a single primary company per Person, any multi-company associations from Actimo require custom multi-select field capture on the People record to preserve the full relationship history. We identify multi-company contacts during the audit phase and configure the appropriate custom field structure before import.

Actimo Learning Path completion records (which specific training was completed, the completion date, and the final score) have no native equivalent in Twenty CRM because Twenty lacks a learning management system object. We transform these records into custom fields attached to the People record: training_completed__c (multi-select text storing completed path names), completion_date__c (date of most recent training completion), and training_score__c (numeric final score). These fields must be created in Twenty Settings → Data Model before the migration run executes.

Actimo calculates engagement scores from message opens, pulse survey responses, learning completions, and login frequency using a proprietary weighting formula. Because that calculation logic lives in Actimo's platform and does not transfer, we capture the most recent score as a static custom Number field (engagement_score__c) on the Twenty People record. We also store the calculation date in engagement_score_date__c to indicate when the value was snapshot from Actimo, since the score will not auto-recalculate in Twenty.

Actimo pulse survey responses have no direct equivalent in standard CRM object models, including Twenty. We import the response text content as a Twenty Note attached to the relevant People record, preserving the full qualitative response. Metadata including the survey name, response submission date, and numeric score value are stored as custom fields (survey_name__c, response_date__c, response_value__c) on that Note record for structured querying and filtering within Twenty's interface.

Actimo messages and news posts directed at specific people or companies become Notes in Twenty attached to the corresponding People or Company record. The original message body, send timestamp, author name, and open count metrics are preserved as Note metadata and custom fields on the Note. This transformation keeps communication history accessible within Twenty's timeline view while maintaining all original engagement indicators for reference and reporting.

Actimo tasks and action items map directly to Twenty Tasks with no object transformation required. Core task attributes including due date, assigned user, completion status (completed vs. open), and parent record link transfer as-is. Actimo task owner assignments are resolved by matching the owner's email address against invited Twenty Workspace Members — if no matching Workspace Member exists, the record is flagged with an unresolved owner for manual resolution before the migration finalizes.

Actimo platform users map to Twenty Workspace Members during migration. The critical sequencing requirement is that Twenty Workspace Members must be invited and accepted before any data import runs, because Actimo owner and assignee references on records are stored as email addresses that require a matching Twenty Workspace Member ID to link correctly. We audit Actimo user emails against invited Twenty members during the pre-migration phase and flag any unresolved owners for team invitation or fallback assignment.

Actimo learning paths (ordered sequences of training content, multimedia assets, and assessment checkpoints) have no equivalent object in Twenty CRM because Twenty does not include a content management or learning management system. Learning path definitions are exported as a structured JSON document and PDF reference that lists each path's module sequence, content references, and completion criteria so your team can manually rebuild the training structure in Twenty's workflow builder or a dedicated LMS.

Actimo workflows (automated triggers for engagement sequences, onboarding flows, pulse survey timing, and multi-step engagement automations) do not transfer programmatically to Twenty CRM. Twenty's workflow builder (available in Organization tier at $19/user/month) must be used to recreate these automations from scratch. We export Actimo workflow definitions as a structured JSON and PDF rebuild reference that documents every trigger condition, action step, timing rule, and conditional branch so your Twenty admin or implementation partner can systematically reconstruct each automation in Twenty's workflow canvas.

Actimo message analytics (open rate percentage, click-through rate, delivery status, and engagement timestamps) cannot populate as native CRM metrics in Twenty because Twenty has no message engagement tracking model. We attach these analytics as custom numeric fields to the Note record representing the original Actimo message: open_rate__c, click_rate__c, and delivery_status__c preserve the engagement data for historical reference. These values are static snapshots from Actimo and will not update automatically within Twenty's environment.