Migrate from Leadfox to HubSpot

LeadFox contacts migrate as HubSpot contacts. Email address is the primary deduplication key. All standard contact properties (firstname, lastname, email, phone) map directly. Custom LeadFox properties migrate as HubSpot custom contact properties. The migration preserves the original LeadFox contact ID in a custom field for traceability and future delta synchronization needs.

LeadFox company records map to HubSpot companies. Domain is preserved as the website URL property on the HubSpot company record. Parent-company relationships in LeadFox require custom property mapping since HubSpot handles company hierarchies differently through the Parent Company association field. This ensures organizational structures transfer correctly.

LeadFox list membership (static segments) migrates to HubSpot lists. Dynamic lists in LeadFox require recreation as HubSpot smart lists using HubSpot's filter logic. List names and descriptions transfer as HubSpot list names and descriptions. This maintains your segmentation structure while adapting to HubSpot's list management capabilities.

LeadFox campaigns migrate to HubSpot campaigns. UTM parameters, campaign source, and medium from LeadFox map to HubSpot's utm_parameters JSON property on the HubSpot campaign record. Historical performance metrics transfer as custom properties. This preserves your campaign attribution history for continued performance analysis.

LeadFox email sequences and automation workflows do not migrate to HubSpot. They are exported as documentation including step definitions, timing rules, enrollment criteria, and A/B variant logic so your HubSpot admin can rebuild them in HubSpot's Workflows tool using a functionally equivalent design. This preserves your automation logic for systematic recreation.

LeadFox landing pages have no direct HubSpot equivalent. Contact data captured by LeadFox landing pages migrates to HubSpot contacts and form submissions. The page designs and templates must be rebuilt using HubSpot's CMS or as embedded HubSpot Forms on your existing website. Page recreation typically requires 2–4 weeks before go-live.

Form submission records in LeadFox transfer to HubSpot form submissions. Form field mappings are created between the LeadFox form structure and the equivalent HubSpot form. UTM data and referrer information from LeadFox submissions map to HubSpot's standard tracking fields. This maintains complete lead source attribution across the migration.

LeadFox's engagement or lead scoring property migrates to a HubSpot custom number property (e.g. Leadfox_Engagement_Score__c). If LeadFox used multiple scoring dimensions, each becomes a separate HubSpot custom property. This preserves your lead scoring methodology for continued segmentation and prioritization in HubSpot.

LeadFox A/B test results and historical variant performance data have no native HubSpot equivalent. We preserve A/B test names, test duration, and winner variant as HubSpot custom properties on the campaign record. The test history itself cannot be recreated in HubSpot's native reporting interface.

LeadFox custom objects migrate 1:1 to HubSpot custom objects. Custom object associations that use LeadFox's relationship model need HubSpot custom object associations set up before migration. We deliver a schema plan for HubSpot custom object creation based on the LeadFox data model.

LeadFox file attachments linked to contacts or companies are downloaded and re-uploaded to HubSpot Files. Files are associated with the corresponding HubSpot record. Large files exceeding HubSpot's 25MB limit are flagged for chunked upload or alternative storage before migration to ensure successful transfer.

LeadFox notes migrate as HubSpot engagement timeline notes on the contact or company record. Original timestamps and note authors are preserved during the migration. Rich-text formatting in LeadFox notes is converted to HubSpot's note body format to maintain readability and context for each record.