Migrate from Leadfwd to Microsoft Dynamics 365 Sales

Leadfwd Contacts sync from Salesforce and map directly to Dynamics 365 Contact records via the Salesforce Contact ID preserved as an external reference field (sf_contact_id__c). We extract from Salesforce after Leadfwd's hourly sync completes to capture the most recent state. Contact fields including name, email, phone, title, and company association transfer to the equivalent Dynamics 365 Contact fields. Any Leadfwd-specific custom fields that reference Leadfwd picklist values (e.g., enrollment status) require manual value remapping before import.

Leadfwd Lead records (treated as equivalent enrollment targets alongside Contacts) map to Dynamics 365 Lead records. The original Leadfwd lead score, source, and status properties migrate to corresponding Dynamics 365 fields. We flag every Lead record as requiring re-qualification in Dynamics 365 because Lead-to-Contact conversion is an explicit admin action rather than an automatic sync event.

Leadfwd Company records sync from Salesforce and map to Dynamics 365 Account. The Company name, domain, address, industry, and phone fields map to Account equivalents. The Salesforce Account ID is preserved as sf_account_id__c for cross-reference during reconciliation. Custom Company fields migrate to Account custom fields with type mapping applied (text to text, number to whole number or decimal, picklist to picklist).

Leadfwd Sequences (multi-channel outreach journeys across email, LinkedIn, SMS, and voicemail steps) are exported as a written structure inventory covering step order, delay rules, channel assignment, and action types. Microsoft Dynamics 365 Sales Sequences (Sales Engagement module) require explicit re-enrollment of contacts post-migration. We deliver the complete sequence structure in a machine-readable format (CSV and JSON) so the customer's admin can rebuild cadences in Microsoft Dynamics 365 Sales without reconstructing the logic from memory.

Active and historical sequence enrollments are exported with enrollment status, current step index, last activity date, and the enrolled Contact reference. These are written to Dynamics 365 as read-only Note records or custom fields on the Contact, tagged with enrollment context (sequence name, enrollment date, last step). They do not resume in Dynamics 365 because the execution engine is Leadfwd-specific. Every enrollment record is flagged as 'requires re-enrollment' in the migration manifest.

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 field icebreaker_text__c on the Dynamics 365 Contact record. The AI-generated variants are Leadfwd-specific and do not regenerate automatically in Dynamics 365; the customer's admin decides whether to preserve them as reference notes or clear the field for manual entry.

Leadfwd engagement events (opens, clicks, replies, bounces, SMS responses, LinkedIn interactions) are exported as typed activity records. Email engagements map to Dynamics 365 EmailMessage records linked to the Contact. Call engagements map to Task with TaskSubtype=Call and CallDurationInSeconds preserved. LinkedIn and SMS interactions map to Note records with channel metadata. Activity timestamps are preserved to maintain the Contact's engagement timeline ordering.

Leadfwd Tasks (manual sales actions linked to Sequence steps) map to Dynamics 365 Task records with Status, Priority, Subject, and ActivityDate preserved. Task assignment migrates by resolving the Leadfwd owner email to the corresponding Dynamics 365 User. Automated task creation logic (Leadfwd's sequence-step automation) does not transfer and must be rebuilt as a Microsoft Dynamics 365 Sales Sequence or Power Automate flow post-migration.

Custom fields on Leadfwd Contacts and Companies sync through the Salesforce API pipeline and are available for extraction. We map them field-by-field to Dynamics 365 custom fields on Contact and Account, applying type conversion (Salesforce data types to Dataverse logical types). Any custom field referencing a Leadfwd-specific picklist value (e.g., sequence enrollment status codes) requires manual value remapping or conversion to a text field to avoid import rejection.