Migrate from Leadfwd to HighLevel

Leadfwd syncs both Contact and Lead records from Salesforce into a unified view. When migrating to GoHighLevel, we export the full Contact and Lead set via the Salesforce export layer, then merge both into GoHighLevel's single Contact object. The original Lead_Status from Leadfwd is preserved in a custom field lf_lead_status__c on the Contact record for audit and segmentation. Duplicate resolution uses email address as the dedupe key; if a Contact and Lead share the same email, they merge into one GoHighLevel Contact with both record's properties combined.

Leadfwd Company records map directly to GoHighLevel Company records. The Company ID from Salesforce export becomes the primary key, and all standard Company fields (name, domain, industry, phone, address) migrate 1:1. Any custom Company properties are mapped to GoHighLevel custom fields, which are created during the schema phase before any data is loaded.

Leadfwd Deal records map to GoHighLevel Opportunity records. The Deal name becomes the Opportunity title, deal value maps to Opportunity Value, and the Leadfwd deal stage maps to a GoHighLevel Pipeline stage that we configure before migration. Deal owner resolves by email match to a GoHighLevel User. If Leadfwd uses multiple deal pipelines (Professional tier), we create corresponding GoHighLevel Pipelines and assign each Opportunity to the correct pipeline during import.

Leadfwd Sequence definitions (step order, step type, delay rules, action content per step) export as a written step-by-step inventory document. GoHighLevel does not have a native Sequence or cadence feature; automated outreach journeys rebuild as Workflows using triggers, conditions, and actions. We deliver the full sequence content (subject lines, body copy, delay intervals, channel per step) in a structured document so the customer's admin can replicate the outreach logic in GoHighLevel Workflows without losing the message content.

Sequence enrollment records (which Contact is enrolled in which Sequence at what step) are exported as status snapshots and written to GoHighLevel Contact custom fields (e.g., lf_active_sequence__c, lf_sequence_step__c) or applied as Tags. Active enrollments cannot resume automatically in GoHighLevel because the execution engine is Leadfwd-specific. We flag every enrolled Contact and provide a recommended re-enrollment approach using the sequence inventory document.

Leadfwd Icebreakers are personalized conversation openers generated per Contact using LinkedIn profile data. We export the generated text and source LinkedIn URL and write them to GoHighLevel Contact custom fields (e.g., lf_icebreaker_text__c, lf_icebreaker_source__c). The AI-generated variants are Leadfwd-specific and do not regenerate in GoHighLevel; the text is preserved for reference but the customer's admin manually activates the openers in GoHighLevel outreach if desired.

Leadfwd creates Tasks for manual sales actions linked to Sequence steps. Task records with status, due date, and assignee migrate to GoHighLevel Task records on the corresponding Contact. Task logic (automated vs. manual trigger) does not transfer; automated tasks from sequences require rebuild as GoHighLevel Workflow actions. Completed tasks carry their original due date and assigned user from the export.

Opens, clicks, replies, and bounces logged in Leadfwd export as engagement events with timestamps and channel metadata. These migrate as GoHighLevel Contact Tags (e.g., tag: 'Opened - Sequence A') or as entries in a custom activity log object if the customer requests it. Detailed event metadata (exact email body excerpt, precise click timestamp to the millisecond) is not available from the Salesforce export layer and is scoped out of the migration.

Leadfwd custom fields sync through the Salesforce API pipeline and are available in the export. We create equivalent GoHighLevel custom fields during the schema phase, map field-by-field, and flag any Leadfwd-specific picklist values (e.g., sequence enrollment status codes) that require manual value remapping because GoHighLevel picklists are independently managed. Fields referencing Leadfwd-specific objects (e.g., Icebreaker status) are mapped as text fields and noted for admin review.