Migrate from Force24 to Twenty CRM

Force24 Contacts map to Twenty CRM Person records. Standard fields (firstName, lastName, email, phone, address) migrate directly. We preserve Force24 lifecycle stage (subscriber, lead, marketing qualified, sales qualified, customer) as a custom field lifecycle_stage__c on the Person record for audit and reporting continuity. Tags migrate as comma-separated text in a custom tags__c field or as a dedicated tag relationship depending on Twenty's current schema support at migration time. The contact's creation date and last-modified date migrate as createdAt and updatedAt timestamps.

Force24's lightweight Company records (typically a name and URL) map to Twenty CRM Company. The domain name stored against the Force24 contact becomes the Company website field. We resolve the Company lookup on the Person record at migration time using domain matching or a pre-built name-dedupe key. If Force24 contacts share no explicit company link, we offer a domain-grouping option that associates contacts from the same email domain to a single Company record.

Force24 stores Lead records as Contacts with a lifecycle_stage property indicating funnel position. We migrate these as Twenty CRM Person records and flag them with a lifecycle_stage__c value of 'lead' to preserve the original classification. If the customer used Force24's lead-specific fields (lead status, lead source, lead score), these map to custom fields lead_status__c, lead_source__c, and lead_score__c on the Person record.

Force24 Custom Objects (user-defined linked-data tables) map to Twenty CRM custom objects of equivalent schema. We export each Custom Object definition — all fields, data types, and relationship fields — during scoping, then pre-create the destination schema in Twenty before any record import. The critical constraint is that Force24 Custom Objects require account manager activation before the API exposes the data; if the feature is not enabled, we flag this at scoping and the customer must arrange activation with Force24 before export. Relationship fields linking Custom Object records to the parent Contact are preserved as lookup fields in Twenty's custom object schema.

Force24 email engagement events (opens, clicks, deliveries) map to Twenty CRM Comment records attached to the Person. The Comment body carries a structured summary (e.g., 'Email opened: [subject] on [date]'). Open and click timestamps preserve as Comment createdAt. This mapping preserves the engagement timeline in Twenty's activity feed without requiring a native engagement-log object.

Force24 SMS and WhatsApp message records migrate as Comment records on the Person, with message body and direction (sent/received) captured in the Comment text. Delivery status is preserved as a custom field delivery_status__c. Because Twenty CRM does not have a native SMS/WhatsApp object, the message history lives in the activity feed alongside email engagement records.

Force24 form submission events (form name, submitted fields, submission date) map to Comment records on the Person. The Comment records the form name and timestamp; form field values are documented separately as a custom data summary for the customer's admin to review. This preserves the fact that a contact submitted a form without requiring a native Form object in Twenty.

Force24 contact tags migrate as a custom tag field on the Person record. If Twenty supports a native tag or label field at migration time, we use it; if not, we write tags as comma-separated values in a custom field tags__c. The customer's admin chooses the strategy during scoping. The tag set is preserved in full — no tag is discarded.

Force24 Smart Lists are saved audience segments with property-based and behavioural filter criteria. We export the segment membership (which contacts are in each list) and recreate it in Twenty as static Person records in a named group, or as a multi-select custom field if the customer prefers a dynamic filter approach. The original filter logic (property conditions, behavioural triggers, AND/OR conditions) is documented in the handoff specification for manual rebuild in Twenty's segmentation layer.

Force24 distinguishes between Marketing users and Sales users with different seat pricing. We export all active and inactive users referenced on contacts and Custom Object records, map by email address to Twenty CRM WorkspaceMember, and hold any unresolved owners in a reconciliation queue for the customer's admin to provision before record import begins. The marketing-vs-sales classification is preserved as a custom field user_type__c for reference.

Force24 lead scoring assigns numeric values to contacts based on engagement and property rules. We export the score value stored on each contact record and write it to a custom field lead_score__c on the Twenty Person record. The scoring rules themselves are Force24 platform configuration and cannot be exported; we document the rule structure (property thresholds, engagement weights) in the handoff specification for manual rebuild.