Migrate from Leadfox to Salesforce Sales Cloud

Leadfox Contact records with no associated Opportunity or deal history map to Salesforce Lead. Contacts with a deal association or a lifecycle status indicating a qualified buyer map to Salesforce Contact tied to an Account. We apply the split rule during data extraction using Leadfox's contact lifecycle fields and deal associations, and preserve the original Leadfox contact ID and lifecycle status in custom fields (leadfox_id__c and leadfox_lifecycle__c) on both the Lead and Contact for audit and reconciliation.

Leadfox Companies map to Salesforce Account. The company's domain and name map to Account Website and Name respectively. If Leadfox stores a parent company relationship, we replicate it as a Salesforce Account hierarchy via the ParentId field. We resolve Account records before any Contact insert so that AccountId is available as a required Lookup at migration time.

Leadfox unlimited custom fields per Contact map to Salesforce custom fields on the Lead and Contact objects. We export field definitions (name, type, options for picklists) from Leadfox and recreate them in Salesforce via the Field Creation API before data migration. Field type mapping: Leadfox text to Salesforce Text (255), long-text to Text Area (Long), number to Number, date to Date, dropdown to Picklist, multi-select to Multi-Select Picklist.

Leadfox Tags are applied at the Contact level as single-select or multi-select values. We export the complete tag vocabulary and the full tag assignment per Contact. In Salesforce, tags that apply to all records of a type become a Multi-Select Picklist field on Lead or Contact. Tags used for segmentation or campaign classification become a Custom Object (Leadfox_Tag__c) with a junction object (Contact_Tag__c) enabling many-to-many assignment, which is more scalable for large tag vocabularies.

Leadfox Segments are dynamic lists based on filter criteria (behavioral rules). We export current Segment membership as static contacts at migration time. Each Segment maps to a Salesforce Campaign with the Segment's filter criteria documented as a Campaign Description so the admin can rebuild the dynamic logic in Salesforce Reports or Flow. Segment membership that represents a static list migrates as Campaign Members.

Leadfox Lead Score is a numeric value computed from behavioral rules (page visits, email opens, form submissions). We export the current numeric score for each Contact as a custom field (leadfox_score__c) on the Lead or Contact record. The underlying scoring rule logic does not export and must be rebuilt in Salesforce using a scoring model (such as Salesforce Rebate and Incentive Management or a custom Flow-based scoring app from the AppExchange). Historical scores serve as a baseline for calibrating the new rules.

Leadfox enforces CAN-SPAM compliance by tracking unsubscribe status per Contact. We export the opt-out flag and suppression list membership and map them to Salesforce HasOptedOutOfEmail (standard field) plus custom fields for detailed subscription status (leadfox_email_pref__c, leadfox_suppressed_date__c). These custom fields preserve the source data so that if the customer later moves to Salesforce Marketing Cloud Account Engagement (Pardot), the full preference history is available.

Leadfox Email Templates stored in Content Studio migrate as Salesforce Classic Email Templates or Lightning Email Templates depending on the destination org's configuration. We export the template HTML and the dynamic personalization token map, then recreate each template in Salesforce and reconnect the personalization tokens to the corresponding Salesforce merge field syntax. We do not migrate template performance metrics (open rates, click rates) as these are campaign-level analytics that do not persist in a transferable format.

Leadfox Landing Pages are built with the platform's proprietary page builder and cannot be exported as live editable pages. We export all form submissions as Contact records with custom fields capturing the originating page name (leadfox_landing_page__c) and UTM parameters if available. Page conversion volumes are exported as a reference table so the customer's team can prioritize rebuilding the highest-volume pages first in Salesforce Experience Cloud or a third-party landing page tool.

Leadfox Automation Workflows (email sequences, triggers, time delays, conditional branches, goal steps) are stored in a proprietary format that does not export as executable code. We document every active workflow as a step-by-step action map (trigger, conditions, actions, delays) in a written Workflow Inventory document. The customer's Salesforce admin or a certified Salesforce partner uses this document to rebuild equivalent logic in Salesforce Flow. We do not migrate automation logic as code; complex multi-branch workflows almost always require manual reconstruction.

Leadfox user accounts, roles, and permissions are not exportable via the standard CSV export or Zapier integration. We extract all Leadfox user names and email addresses referenced on Contact and Deal records and produce a User Mapping Table listing the Leadfox user and their Salesforce User equivalent. The customer's Salesforce admin provisions matching User records (or flags inactive status) before migration begins. This is a manual step that must complete before any OwnerId references can be resolved during import.

Leadfox Campaign and Event Tracking data (search tracking, keyword performance, UTM parameters, campaign names) migrates to Salesforce Campaign records with custom tracking fields (leadfox_utm_source__c, leadfox_utm_medium__c, leadfox_utm_campaign__c). We export the tracking data as a reference table. Actual analytics (impressions, conversions, revenue attribution) do not transfer because Leadfox does not expose these as structured exportable records; the customer reviews these metrics in Leadfox before cutover or reconstructs them in Salesforce's Campaign Influence reporting post-migration.

Leadfox Deals map to Salesforce Opportunity. The Deal name, amount, stage, and close date migrate to Opportunity Name, Amount, StageName, and CloseDate. If Leadfox stores deal line items or product associations, we map these to Salesforce Products and OpportunityLineItems with a Pricebook2 reference resolved at migration time. Leadfox's deal custom fields map to custom Opportunity fields using the same type-mapping logic as Contact custom fields.

Leadfox does not expose a native activity timeline equivalent to Salesforce's Task and Event objects. Email open and click events are available as metadata on the Contact record (last opened, click count). We extract this metadata and map it to custom fields on the Lead or Contact record (leadfox_last_email_open__c, leadfox_email_click_count__c) and create a summary Task record for the most recent email engagement. Full chronological engagement history (individual email open timestamps) is not available for bulk export from Leadfox and is noted as a data gap in the migration scope document.