Migrate from Leadfwd to HubSpot

Leadfwd contacts migrate directly to HubSpot contacts. Email address is the primary deduplication key — FlitStack checks for existing HubSpot contacts by email before creating new records to prevent duplicates on re‑migration. The match is case‑insensitive and ignores whitespace, preventing duplicate records. For contacts already present in HubSpot, FlitStack updates existing properties while preserving the original create timestamp and owner assignment.

Leadfwd targets represent prospects not yet enrolled in a sequence. They merge into HubSpot contacts on migration — the Target's firmographic data (company, title, phone) maps to the corresponding HubSpot Contact properties, and the original target record type is flagged in a custom property for audit purposes.

Leadfwd target records include a primary company name and domain. FlitStack extracts these to create a HubSpot Company record first, then links the Contact to it via the company's domain. If a matching HubSpot Company exists, the Contact is associated to the existing record rather than creating a duplicate.

Leadfwd tracks which sequences a contact is enrolled in and the enrollment state (active, paused, completed, bounced). This enrollments data has no native HubSpot equivalent, so FlitStack creates a custom multi-select property (Sequence_Enrollments__c) on the Contact record that stores the sequence names and states as comma-separated values for reporting visibility.

Leadfwd engagement events (email_sent, email_opened, email_replied, email_bounced, task_completed) are converted to HubSpot timeline entries. Email-related events map to HubSpot email logging on the Contact. Task completions map to HubSpot notes with a 'Task Completed' label and the original timestamp preserved. The engagement-type label is stored in a custom note field for filtering.

Leadfwd custom fields on contacts (beyond standard name/email/phone) require HubSpot custom properties to be created first. FlitStack generates a schema setup plan listing each Leadfwd custom field name, its data type, and the HubSpot property name to create before migration runs so the data lands in the correct fields.

Leadfwd target-level custom fields map to either Contact or Company custom properties depending on whether the field data is prospect-level or firmographic. FlitStack's pre-migration audit reviews each custom field and assigns it to the correct HubSpot object to avoid data misplacement.

Leadfwd owner assignments on contacts and targets resolve by email match against HubSpot Users. If a HubSpot User with the matching email does not exist, FlitStack flags the record before migration and either assigns it to a fallback HubSpot owner or defers it for your admin to create the user first.

Leadfwd stores LinkedIn profile URLs on contact and target records. HubSpot has no native LinkedIn URL field. FlitStack maps this to a custom text property (LinkedIn_URL__c) on the Contact so sales reps can reference it without leaving HubSpot. The property stores the full URL and can be used in HubSpot sequences or reports to link directly to the prospect's LinkedIn profile.

Leadfwd campaigns group targets and sequences for a specific outreach initiative. HubSpot's campaign object tracks marketing campaign performance but does not map 1:1 to Leadfwd's campaign concept. FlitStack preserves campaign membership as a custom property on each contact and exports a campaign-list CSV for rebuilding in HubSpot Lists or the Campaigns tool.