Migrate from Leadfwd to Twenty CRM

Leadfwd Contacts sync from Salesforce via the connected app and map directly to Twenty CRM Person records. We use the Salesforce Contact ID as the dedupe key during import, and the Leadfwd Contact's email address becomes the primary identifier on the Twenty Person record. Any custom Contact fields that passed through Salesforce's field-level visibility check migrate as Twenty custom fields. Standard fields including name, email, phone, title, and address map directly.

Leadfwd represents Leads as a parallel enrollment target alongside Contacts. We map Lead records to Twenty Person records and flag the original Leadfwd lead_status in a custom field for audit. If the Lead was in an active Sequence, we preserve enrollment metadata (sequence name, step index, status) as reference fields on the Person rather than as executable state, since Twenty has no native sequence engine.

Leadfwd Company records sync from Salesforce as parent entities and map to Twenty CRM Company records. The Company ID is preserved as a custom field, and any custom Company properties that were visible to the Salesforce connected app migrate as Twenty Company custom fields. Company name, domain, industry, employee count, and address map directly.

If Salesforce Deals were synced to Leadfwd as part of the customer's configuration, they migrate to Twenty CRM Opportunity records. Deal amount, stage, close date, and owner map to Opportunity amount, stage, closeDate, and assignee. If no Deals were present in the Salesforce connector, this object is omitted from the migration scope.

Leadfwd Sequences define automated multi-channel outreach journeys across email, LinkedIn, SMS, and voicemail steps. We export the full sequence structure including step order, delay rules, action types, and step content. Because Twenty has no native sequence engine, we deliver a written Sequence Inventory document: for each Sequence, we document the trigger, step cadence, channel per step, delay logic, and recommended rebuild path using Twenty's workflow builder or an n8n automation. This is not executable code migration.

Enrollment records track which Contact is in which Sequence at what step. We export enrollment status, current step index, last activity date, and sequence name as custom fields on the Twenty Person record. This preserves the historical record of which outreach a contact received, but the enrollment state cannot resume in Twenty because the execution engine is Leadfwd-specific. We flag each enrollment record as 'requires re-enrollment' in the migration report.

Icebreakers are AI-generated personalized openers derived from LinkedIn profile data. We export the generated text and source LinkedIn URL as custom fields on the Twenty Person record. The AI variants are Leadfwd-specific and do not have a functional equivalent in Twenty, so the content migrates as reference text rather than as an active personalization feature.

Leadfwd creates Tasks for manual sales actions linked to Sequence steps. We export Task records with status, due date, assignee, and description. Task logic (automated vs. manual) does not transfer; all migrated tasks appear as completed or open manual tasks in Twenty. Task assignment migrates by resolving Leadfwd owner email to a Twenty User.

Opens, clicks, replies, and bounces logged as engagement events migrate to Twenty Activity records with timestamps, channel metadata, and engagement type preserved. Deep event details such as which exact email variant was opened are Leadfwd-specific and are not available for transfer. We migrate the activity type, timestamp, and contact reference; the customer's team reviews the activity timeline in Twenty post-migration.

Custom fields on Leadfwd Contacts and Companies migrate to Twenty People and Company custom fields. We audit Salesforce field-level visibility during scoping to confirm which fields were actually synced from Salesforce to Leadfwd; any custom field hidden by Salesforce field-level security or Profile restrictions was not in Leadfwd and therefore cannot be migrated. Leadfwd-specific picklist values (e.g., Sequence enrollment status tokens) require manual value mapping to Twenty equivalents before import.

Sender rotation configuration, mailbox credentials, and mailbox warming progress (warmth scores, daily send curves) are stored in Leadfwd's own infrastructure and cannot be exported or replicated in Twenty. We clearly scope mailbox infrastructure out of migration deliverables upfront. If the customer uses Twenty's self-hosted option, they control their own sending infrastructure (SMTP, IP pools, warming tools) independently, but this is a separate configuration step, not a data migration item.