Migrate from Leadfox to Zoho CRM

Leadfox Contacts map directly to Zoho CRM Leads as the primary record type. The Lead's standard fields (First Name, Last Name, Email, Phone, Company) are populated from the corresponding Leadfox contact fields. The Leadfox contact's current lifecycle status (subscriber, lead, MQL, SQL, customer) is preserved in a custom picklist field lf_original_lifecycle__c for reference. No automatic Lead-to-Contact conversion is triggered at migration time; that decision belongs to the customer's Zoho admin post-migration based on their sales process.

Leadfox does not have a standalone Company/Account object; company data lives in the Contact record's company name field. If the customer's Leadfox account contains contacts sharing the same company name and that company data is important for Zoho's Account-Contact hierarchy, we extract distinct company name values, create Zoho CRM Account records, and attach the Leadfox contacts as Leads with the Account lookup resolved. This step requires a scoping decision on whether to normalize company data or leave it as free-text on the Lead.

If the customer uses Leadfox Deals (Premium tier), they map to Zoho CRM Potentials. The Deal name, stage, value, and expected close date transfer to the Potential's Name, Stage, Amount, and Closing Date fields. We create a Zoho Sales Pipeline (or use the default Standard pipeline) and map Leadfox deal stages to corresponding Zoho stage names during schema setup. The Potential is linked to the resolved Account/Contact lookup.

Leadfox supports unlimited custom fields per contact as text, number, date, or dropdown types. We export the full field definition map alongside record values and recreate each field in Zoho CRM with the matching field type. Zoho's field type system (single-line text, multi-line text, numeric, date, picklist, multi-select picklist, checkbox, phone, email, URL) is mapped from the Leadfox type. Required-field enforcement is disabled during migration and re-enabled after load validation to prevent import rejections from incomplete legacy records.

Leadfox tags are flat label assignments at the contact level, supporting multiple tags per contact. We extract the full tag vocabulary from the Leadfox export and create a Zoho CRM custom multi-select picklist field named lf_tags__c on the Leads module. Each contact's tag set is serialized as semicolon-separated values in that field. If the customer's tag count exceeds Zoho's recommended picklist size (under 300 values), we propose a separate Tags custom module with a many-to-many relationship to Leads instead.

Leadfox Segments are dynamic lists based on filter criteria that re-evaluate on access. These definitions do not transfer as live Zoho CRM filters because the underlying rule logic is not accessible. We export the Segment membership snapshot as a CSV at migration time, create Zoho CRM Custom Views with static filter criteria matching the exported membership, and note the original Segment definition in the migration inventory document for the admin to configure as dynamic Custom Views in Zoho post-migration.

Leadfox tracks CAN-SPAM unsubscribe status per contact and maintains a suppression list. We export the unsubscribe flag and suppression list entries and apply them to Zoho CRM Leads by setting the standard Email Opt Out field (山川Email_Opt_Out) to true for suppressed contacts. Any additional suppression flags from Leadfox are added as a custom checkbox field lf_suppressed__c on the Leads module to preserve the source of the opt-out decision.

Leadfox computes a numeric lead score based on engagement rules (page visits, email opens, form submissions). We export the current score value as a static integer and write it to a custom numeric field lf_lead_score__c on the Zoho Lead. The scoring rules themselves are not exported — the rules are Leadfox-specific and cannot be reproduced without the original rule definitions. The migration inventory documents the score distribution so the customer's admin can rebuild scoring rules in Zoho using Blueprint, Deluge, or a Zoho Marketplace scoring app as a baseline reference.

Leadfox Email Templates stored in Content Studio are exported as HTML with dynamic personalization tokens. We export the full template HTML and the token-to-field mapping as a structured JSON alongside each template. Zoho CRM's Email Templates module supports merge fields and HTML content; we provide the imported HTML as a Zoho template with merge fields reconnected to the corresponding Zoho Lead fields. Any broken token references are flagged in the template inventory for the customer's admin to correct.

Leadfox landing pages are built in the platform's proprietary page builder and cannot be exported as editable assets. We export form submission records as structured Lead records in Zoho CRM, capturing every form field value and the source landing page URL. The landing page HTML is exported as a snapshot reference file. The migration inventory includes a ranked list of pages by submission volume so the customer can prioritize rebuilding the highest-converting pages in Zoho Forms or a third-party landing page tool.

Leadfox automation sequences (triggers, time delays, conditional branches, goal steps) are stored in a proprietary format and are not directly portable. We produce a step-by-step workflow map for every active Leadfox automation: trigger condition, each action, delay duration, branch criteria, and goal definition. This document is delivered as part of the migration inventory and is the basis for manual rebuild in Zoho Workflows, Blueprint, or Deluge. We do not migrate automation logic as executable code.