Migrate from Leaf360 to HighLevel

Leaf360 contacts map directly to HighLevel contacts. Every contact field (name, email, phone, address) transfers as-is. Primary company association resolves via the Companies step. Owner assignment uses email-match against HighLevel users — unmatched owners flagged for admin resolution before the opportunity step.

Leaf360 companies map to HighLevel companies. Company name, domain/website, industry, employee count, and revenue fields transfer directly. HighLevel companies support multiple contacts per company, so Leaf360's N:1 contact-to-company mapping collapses cleanly to the primary company association. After migration, contact records retain their company linkage in HighLevel, enabling company-level reporting and activity tracking across all associated loan officers and referral partners.

Leaf360 deals map to HighLevel opportunities. Deal name, amount, close date, and owner transfer directly. Leaf360's lending-stage pipeline (Pre-Qual, Submitted, Underwriting, Approval, Closing) maps to a HighLevel pipeline with matching stage names. Probability and forecast category are applied per stage from HighLevel's pipeline configuration.

Leaf360 custom fields like 'loan_type' (Conventional, FHA, VA, USDA) have no native HighLevel equivalent on the opportunity object. We create a HighLevel custom field of type pick-list or text on the opportunity and migrate values value-by-value. The field is available for workflow triggers and pipeline filtering in HighLevel.

Leaf360 referral source data (Real Estate Agent, Builder, Community Partner, etc.) migrates as a HighLevel contact custom field. In HighLevel, this field can drive workflow segmentation so referral follow-up sequences trigger automatically from the imported referral source value. Post-migration, your team can create automated nurture sequences, task assignments, and deadline alerts based on the referral source, ensuring consistent partner engagement without manual outreach tracking.

Leaf360 property address stored as a custom field migrates to a HighLevel custom field. We recommend placing it on the opportunity for deal-specific property context, with the full address text stored as a single formatted field or split into street/city/state/ZIP based on data quality in the source.

Rate lock status (Not Started, In Progress, Locked, Expired) migrates as a pick-list custom field on the HighLevel opportunity. This field can drive pipeline coloring, stage probability overrides, or workflow actions in HighLevel's Automation Builder. Teams can configure automatic task creation when rate lock status changes, send notifications to loan processors when status reaches specific milestones, and use the field for reporting on deal velocity through the rate lock stage.

Leaf360 notes and activity entries migrate to HighLevel notes attached to the corresponding contact or opportunity. Original timestamps and note authors are preserved as note metadata. Rich-text formatting is converted to HighLevel's note format. Notes with no associated contact are attached to the most recently linked contact by timestamp.

File attachments on Leaf360 contacts, companies, or deals are downloaded and re-uploaded to HighLevel's file storage linked to the corresponding record. HighLevel file size limits apply (25MB per file). Files without an associated record are attached to the most relevant contact record.

Leaf360 tags migrate as HighLevel tags on the contact. Tags drive workflow triggers in HighLevel's Automation Builder, making tag migration critical for post-migration automation continuity. Duplicate tags are deduplicated during import. After migration, your team can create workflow rules that automatically apply tags based on opportunity stage changes, referral source values, or custom field updates, ensuring that existing automation logic carries forward without manual recreation.

Each Leaf360 deal pipeline becomes a HighLevel pipeline. Leaf360 lending stages map to HighLevel pipeline stages by name; stage order and probability values transfer as configured. HighLevel allows multiple pipelines per sub-account — each Leaf360 pipeline gets its own HighLevel pipeline with stage customization available post-migration.

Leaf360 automations are mortgage-specific and cannot be exported in a transferable format. FlitStack exports workflow definitions as a structured document listing triggers, conditions, and actions. Your team rebuilds these in HighLevel's Workflow Builder using the export as a blueprint. We recommend this step during the test migration window before the full cutover.