Migrate from Leadfox to Pipedrive

Leadfox Contacts map directly to Pipedrive People. Standard fields (name, email, phone, address) migrate as their Pipedrive equivalents. We resolve the name field by splitting on known separators to populate first_name and last_name on the Person object. Any contact without an email address is flagged in the reconciliation report and imported with a manual-validation flag so the customer's team can complete the record before it enters the pipeline.

Leadfox Contacts frequently contain a company name field even when no formal Company object exists. We extract the company name from each Contact record, deduplicate by normalized company string, and create a corresponding Organization record. Each Contact then links to its Organization via the org_id field on the Person record. This creates the Pipedrive Person-Organization relationship that enables activity rollup and account-level reporting.

Leadfox tags are flat string labels applied at the Contact level. We export all distinct tag values, create a Pipedrive custom multi-select picklist field named leadfox_tags__c, and populate each Person record with the applicable tag values. If a Contact has more than 10 tags, the excess tags are appended to a secondary text field so no relationship data is lost.

Leadfox Segments are dynamic filter-based lists. We export the segment membership snapshot (the contacts in each segment at the time of export) and write each segment name as a tag value on the Person record. The segment definition (filter criteria) is documented in the workflow inventory as it cannot be recreated automatically in Pipedrive without rebuilding the filter logic manually.

Leadfox assigns numeric lead scores based on behavioral rules. We export the current score value for each Contact and write it to a custom numeric field named leadfox_score__c on the Person record. The underlying scoring rule logic is not exported and cannot be reconstructed automatically; we document the original rule set in the automation inventory for the customer's team to rebuild using Pipedrive's custom field filtering and automation conditions.

Leadfox custom fields migrate to Pipedrive custom fields of equivalent type. Text fields map to Pipedrive varchar fields, numeric fields to number fields, date fields to date fields, and dropdown fields to select fields with the options list preserved. We create the destination custom fields in Pipedrive before any Person import so that the field keys are available for mapping during data load.

If the customer has used Leadfox's custom field workaround to track deal-like records, we extract these and create Pipedrive Deals. The mapping requires the customer to define which Leadfox fields map to Pipedrive Deal fields (title, value, stage, expected_close_date, owner_id). We do not assume a standard mapping for deal custom fields and resolve this during scoping.

Leadfox tracks CAN-SPAM unsubscribe status per contact. We export the suppression list and set the email_opt_out flag on the corresponding Pipedrive Person records during import. This ensures compliance continuity and prevents the customer's Pipedrive instance from sending to previously unsubscribed addresses.

Leadfox email templates with dynamic personalization tokens are exported as HTML files with a field token map. We deliver these as reference assets alongside the migration. Pipedrive does not include a template content library as a standard object, so we attach the exported template HTML to an Activity Note on the related Person or Organization record for the customer's team to repurpose manually in their chosen email tool.

Leadfox automation sequences are documented as a step-by-step action map covering triggers, conditions, time delays, and actions. We deliver this as a written inventory document with each sequence numbered and annotated with the equivalent Pipedrive Automation action. The customer or a Pipedrive specialist rebuilds the automations post-migration. We do not migrate automation logic as executable code.

Leadfox landing pages export as HTML snapshots with form field definitions. We export form field mappings and the page URL. The visual layout cannot be reproduced as an editable page in Pipedrive. We attach the page snapshot and form mapping to a note on the Person record for contacts submitted through that form, and flag the top-converting pages in the handoff document so the customer's team prioritizes rebuilding those in their chosen landing page tool.