Migrate from Leadfox to Microsoft Dynamics 365 Sales

Leadfox Contacts with early lifecycle stages (subscriber, lead, marketing qualified) map to Salesforce Lead. We use Leadfox's lifecycle stage property and tag membership to determine the split. Contacts with advanced stages (opportunity, customer) map to Salesforce Contact and Account pairs. The original Leadfox lifecycle stage value migrates as a custom field on the Lead record for reporting continuity.

Leadfox Contacts representing companies and customers map to Salesforce Contact records linked to Account records. We extract the company name from the Leadfox Contact company field, create the Account first, then link the Contact with the resolved AccountId. If no company name exists, the Contact migrates as an individual without an Account link, flagged for manual Account assignment post-migration.

Leadfox stores company data as a property of Contact records rather than a standalone object. We extract distinct company names and domain values from Contact records and create Salesforce Account records. The Leadfox company domain maps to the Account Website field, and any associated address fields map to the Account address composite.

Leadfox custom fields per Contact map to Salesforce custom fields on the corresponding Lead, Contact, or Account entity. We pre-create the destination schema in Dynamics 365 including field types (text, number, date, dropdown), field lengths, and required settings. Field names are normalized to Salesforce naming conventions with __c suffixes. Dropdown fields map to Salesforce picklist fields with the same value set.

Leadfox tags applied at the Contact level migrate to a Salesforce multi-select picklist field on Contact and Lead. If tag sets exceed the 255-character multi-select limit, we create separate custom fields per tag group or map to Salesforce Topics. The customer chooses the tag strategy during scoping based on tag volume and reporting needs.

Leadfox dynamic Segments are defined by filter criteria against behavioral data. Since the behavioral criteria cannot migrate, we export the current Segment membership (the list of Contacts currently in each Segment) as a Salesforce Campaign with each Contact added as a CampaignMember. Segment definitions are documented for the customer to rebuild using Dynamics 365 Marketing or Power Automate.

Leadfox calculates numeric lead scores based on engagement rules. We export the current score value as a static custom numeric field on each Lead and Contact record. The scoring rules themselves (page visit weights, email open triggers, form submission logic) are documented in the workflow inventory and do not migrate. Teams rebuild scoring logic in Dynamics 365 Sales Accelerator or Power Automate using the migrated historical scores as a baseline.

Leadfox tracks unsubscribe status and suppression list entries per Contact. We export the suppression status and apply it to the Dynamics 365 Contact or Lead record by setting the HasOptedOutOfEmail field to true for suppressed contacts. Email opt-in status migrates as a custom field to preserve the original subscription consent record.

Leadfox user accounts, roles, and permissions are not exportable via standard tools. We extract the list of active Leadfox users with their names and email addresses and provide a mapping table. The customer's Dynamics 365 admin provisions the corresponding User records in Salesforce before migration begins. OwnerId lookups on migrated records are resolved against this table.