Migrate from Leadfox to Freshsales

Leadfox Contacts map to Freshsales Lead for unqualified prospects and to Freshsales Contact for qualified contacts attached to an Account. We use Leadfox lifecycle stage or behavioral lead score as the split criterion during scoping: contacts above a threshold score map to Contact with an Account; below-threshold contacts map to Lead. We preserve the original Leadfox lifecycle stage in a custom field lf_original_lifecycle__c on both Lead and Contact for audit. Freshsales requires the Lead-to-Contact field mapping to be configured in Admin Settings before conversion to avoid data loss.

Leadfox custom fields on Contact (text, number, date, dropdown, checkbox) map to Freshsales custom fields on the corresponding target object (Lead or Contact). We export field definitions from Leadfox alongside values, then pre-create matching custom fields in Freshsales via Admin Settings before import. Field types map by nearest equivalent: Leadfox text to Freshsales text, Leadfox number to Freshsales number, Leadfox date to Freshsales date picker, Leadfox dropdown to Freshsales picklist. Required-field constraints in Freshsales must be reviewed before import because mandatory fields will reject records missing those values.

Leadfox Tags are flat key-value flags applied at the Contact level. We export all distinct tag values across the contact set and create a Freshsales multi-select picklist custom field (e.g., lf_tags__c) containing every unique tag as a picklist value. Each contact's tag assignments populate the multi-select field. If the customer uses tags for segmentation beyond 20 distinct values, we discuss splitting into multiple fields or using Freshsales Topics with TopicAssignment records. Tag strategy is confirmed during scoping before schema deployment.

Leadfox Segments are dynamic lists defined by filter criteria on contact properties. We export the current membership (the flat list of contacts in each segment at export time) and either create Freshsales static contact lists or document the filter criteria as a Freshsales saved filter the admin can recreate. Dynamic segment logic that depends on ongoing behavioral triggers does not transfer; the static snapshot preserves the membership snapshot while the admin rebuilds the dynamic logic in Freshsales.

Leadfox behavioral lead scores migrate as a static numeric custom field (lf_lead_score__c) on both Lead and Contact. The score reflects the value at export time. Leadfox behavioral rules that produced the score (page visit thresholds, email open counts, form submission triggers) do not export. The customer uses the historical scores as a baseline to configure Freshsales Freddy AI scoring or a manual score replacement in Freshsales workflows after migration.

Leadfox unsubscribe status and suppression list entries migrate to Freshsales contact preference fields. We export CAN-SPAM compliance data as a suppress file and apply opt-out status to Freshsales HasOptedOutOfEmail field and Email Status on the contact record. This prevents bounced or suppressed contacts from receiving Freshsales marketing emails post-migration and maintains compliance continuity from Leadfox.

Leadfox Content Studio email templates export as HTML with dynamic personalization tokens. We deliver the HTML body and the token-to-field map so the customer can rebuild templates in Freshsales email template builder and reconnect tokens to Freshsales contact fields. Visual layout and A/B test variants in Leadfox do not export as editable assets; we document the A/B subject lines and content variants as reference for the admin to reconfigure in Freshsales.

Leadfox landing pages and pop-up forms are platform-native and export as HTML snapshots and form field definitions only. Form submission records map to Freshsales Contact with a custom field tracking the original landing page name (lf_landing_page_source__c) so the customer can see which Leadfox pages generated migrated contacts. We prioritize rebuilding the top-converting pages in Freshsales webforms first based on submission volume.

Leadfox User accounts and team member roles do not export via the standard export tools. We extract every distinct owner referenced on Contact records and produce a mapping table listing the Leadfox user name, email, and role. The customer's Freshsales admin provisions corresponding User accounts and we match by email during import. Owner resolution is a prerequisite step before record import because Freshsales requires OwnerId on most standard objects.