Migrate from Leadfwd to Salesforce Sales Cloud

Leadfwd Contact records map directly to Salesforce Contact using the Salesforce Contact ID as the foreign key. Because Leadfwd syncs FROM Salesforce, the Contact record already exists in Salesforce; our migration layer confirms the ID match, audits custom field parity (Leadfwd's visible fields are gated by Salesforce field-level security), and flags any custom Contact properties that would not appear in Leadfwd's mapping interface due to Profile-level restrictions.

Leadfwd Lead records map to Salesforce Lead using the Salesforce Lead ID as the foreign key. The original Leadfwd enrollment status (Active, Paused, Completed, Unsubscribed) is preserved in a custom field lf_enrollment_status__c for sequencing audit. Leadfwd does not have a separate Lead object distinct from Salesforce; it mirrors Salesforce Leads through the bidirectional sync.

Leadfwd Company records map to Salesforce Account. The Salesforce Account ID is the parent key for all Contact records. Custom Company properties migrate to Account custom fields (Account __c), but any field referencing Leadfwd-specific picklist values requires manual value mapping before insert.

Leadfwd Targets are prospect records in a pre-enrichment state. We map Targets with an email address to Salesforce Contact (if attached to an Account) or Lead (if no Account association). Targets without contact information are staged in a Salesforce custom object or held in a CSV reconciliation file for the customer's admin to enrich and load.

Leadfwd Sequences define automated outreach journeys across email, LinkedIn, SMS, and voicemail steps. We export the full sequence structure including step order, delay rules, action types, and body templates as a written inventory document. Salesforce Sales Engagement (formerly High Velocity Sales) or a third-party cadence tool is the rebuild target. Sequence logic does not migrate as executable code.

Enrollment records track which Contact or Lead is enrolled in which Sequence at what step. We preserve enrollment status, current step index, and last activity date in custom fields on the Contact or Lead record (e.g., lf_current_sequence__c, lf_current_step__c, lf_last_enrollment_date__c). The execution state is Leadfwd-specific and cannot resume in Salesforce; we flag every active enrollment as requiring manual re-enrollment in the destination cadence tool.

Icebreakers are personalized conversation openers generated per Contact using LinkedIn profile data. We export the generated text and source LinkedIn URL as a custom text area field (lf_icebreaker__c) on the Salesforce Contact. The AI-generated variants are Leadfwd-specific and do not have an equivalent in Salesforce without a separate AI personalization integration.

Leadfwd creates Tasks for manual sales actions linked to Sequence steps. We export Task records with Status, Priority, ActivityDate, and Owner resolved by email match to Salesforce User. Automated task-generation logic does not transfer; Salesforce Flow or Sales Engagement replaces this behavior post-migration.

Opens, clicks, replies, and bounces are logged as engagement events in Leadfwd. We export these as Salesforce Task records with TaskSubtype and custom engagement metadata fields (lf_engagement_type__c, lf_channel__c). Deep event details such as which exact email body variant was opened are not fully portable; we preserve the aggregate engagement count per Contact.

Custom fields on Contacts and Companies migrate to Salesforce custom fields on Account and Contact. We map them field-by-field using Salesforce field types (text, picklist, checkbox, date, number) but flag any field referencing Leadfwd-specific picklist values for manual value translation. Custom field sync visibility is gated by the Salesforce connected app's OAuth scope; we audit field-level access during scoping.

Sender rotation configuration, mailbox authentication credentials, and warming progress (warmth scores, daily send curves) are stored in Leadfwd's own infrastructure and cannot be exported. We scope mailbox infrastructure out of migration deliverables upfront. Salesforce does not manage sender mailboxes natively; customers configure external email delivery (Gmail, Outlook, or a dedicated sending platform) separately.

User-level preferences such as timezone, notification settings, and LinkedIn integration tokens do not migrate. We preserve user email addresses for Owner reconciliation and provide a preferences reset checklist for the customer's admin to configure Salesforce User settings post-migration.