Migrate from Leadfox to Twenty CRM

Leadfox Contact records map directly to Twenty People. Standard fields (name, email, phone, address) migrate with type-preserved field mapping. Custom fields per Contact export as field definitions plus values; we recreate the custom field schema in Twenty's Data Model (Settings > Data Model) before import and map field types (text, number, date, dropdown) to their Twenty equivalents. The Leadfox contact ID is preserved as a custom field leadfox_id__c for audit trail and cross-reference.

Leadfox Tags applied at the individual Contact level export as a comma-separated list per contact. We convert this to a Twenty multi-select picklist field tags__c on the People object. During scoping, we identify which tags represent company affiliations versus audience segments; company-affiliation tags may instead be resolved to a Company lookup or converted to a Company field if the tag clearly indicates organization membership.

Leadfox Segments are dynamic lists based on filter criteria. The dynamic filter logic does not migrate because Twenty does not support the same dynamic segment model. We export current Segment membership (the list of contacts in each segment at migration time) and convert it to a static Twenty Topic with TopicAssignment records. The customer's team defines the rebuild criteria in Twenty using Twenty's filter and view capabilities if ongoing dynamic segmentation is required.

Leadfox does not have a standalone Company or Account object; organization data lives as fields within the Contact record (company name, domain, address). We extract unique organization names from Contact records and create Twenty Company records, deduplicating by domain or name. The People record then receives a Company lookup link. This N:1 merge is computed at migration time from the Contact dataset.

Leadfox calculates numeric lead scores based on behavioral rules. We export the current numeric score value as a static custom field leadfox_score__c on each People record. The behavioral rules that produced the score (page visits, email opens, form submissions) are not exported. Teams relying on lead scoring must define new scoring criteria in Twenty using custom number fields and filter conditions, using the historical exported scores as a baseline reference.

Leadfox tracks unsubscribe status and suppression per Contact for CAN-SPAM compliance. We export the suppress file and apply opt-out status to the People email field in Twenty, setting the HasOptedOutOfEmail flag to true for suppressed contacts. This ensures compliance continuity at cutover. Email template personalization tokens export as a field token map for reference during email template reconstruction.

Leadfox landing page form submissions create Contact records in Leadfox. We export these as People records with a custom field source_page__c indicating the originating landing page URL. The HTML visual layout of the landing page itself cannot be ported; we export form field definitions and provide a page volume ranking (by submission count) so the customer can prioritize rebuilding the highest-converting pages first in their chosen landing page tool.

Leadfox automation sequences (triggers, time delays, conditional branches, goal steps) are stored in a proprietary format that does not export. We document every active workflow as a step-by-step action map listing the trigger event, each condition branch, all action steps, and the goal definition. The customer's team uses this document to rebuild workflows in Twenty's workflow builder or via an external automation tool integrated through Twenty's API. We do not migrate automation logic as executable code.

Leadfox email sequences (time-triggered cadence emails) are exported as a template reference list with step order, delay intervals, and subject/body variables. We deliver this as a written sequence map so the customer's team can rebuild the cadence in Twenty using Tasks with scheduled reminders, third-party email sequencing tools (Lemlist, Mailshake, or a custom API integration), or a marketing automation platform that handles cadence logic independently. Native sequence functionality in Twenty was absent as of research date; teams should verify current feature status during scoping.

Leadfox user accounts and role assignments do not export via standard tools. We provide a manual mapping table listing each source user name and email address, and the customer provisions matching Member accounts in Twenty before migration. Owner assignments on Contact and any Deals map by email lookup against the Twenty Member list. Users without a match go to a reconciliation queue for manual provisioning.