Migrate from Leaf360 to HubSpot

Leaf360 borrowers map directly to HubSpot contacts. The contact's primary company (leaf360_company_id) resolves to a HubSpot company via lookup before the contact record is written. Borrowers without a primary company in Leaf360 create standalone HubSpot contacts. All contact records retain their original Leaf360 create dates for historical reporting continuity.

Leaf360 companies map to HubSpot companies. Referral partner companies and borrower employer companies are treated as the same HubSpot company object. HubSpot's company hierarchy (parent/child) is available for multi-office brokerages if Leaf360 stores parent relationships. Company phone, address, and industry fields map directly to HubSpot standard company properties.

Leaf360 loans-as-deals map to HubSpot deals. The Leaf360 deal represents the mortgage application; the HubSpot deal represents the same deal in the pipeline. Loan-specific fields migrate as custom deal properties. The deal name is constructed from the borrower name and property address for straightforward identification in HubSpot.

Each Leaf360 pipeline (e.g., Purchase, Refinance) becomes a HubSpot deal pipeline. HubSpot pipelines are independent stage-scope containers — stage pick-list values are scoped per pipeline, matching Leaf360's stage scoping. The pipeline name and all stage labels are preserved exactly as they appear in Leaf360 to maintain operational familiarity.

Leaf360 stages (Pre-Approval, Processing, Underwriting, Clear to Close, Funded, Denied) map to HubSpot deal stage values via value-by-value mapping. We preserve the stage-entered timestamp as a HubSpot custom datetime field on the deal. Each stage transition is logged with the original Leaf360 timestamp to support pipeline velocity reporting.

HubSpot has no native referral partner association object. We create a custom text property (Referral_Partner__c) on the Contact to store the referral partner's name. For referral status tracking, a custom pick-list property (Referral_Status__c) on the Company stores whether the company is an active referral partner.

Leaf360 loan officers stored as contacts map to HubSpot users (owner field on deals and contacts). If the loan officer is both a user and a contact, we create both a HubSpot user (for ownership) and a contact record (for referral tracking). Owner resolution uses email match against HubSpot users.

HubSpot has a native engagements model for logging calls, emails, meetings, and notes. All Leaf360 activities migrate with original timestamps, owners (by email match), and parent-record links to the corresponding HubSpot contact or deal. Engagement type and direction (inbound/outbound) are preserved where available in Leaf360.

Leaf360 file attachments on deals and contacts re-upload to HubSpot Files. Files are linked to the corresponding contact, company, or deal record. File size limits (25MB per file in HubSpot) are enforced; files exceeding the limit are flagged for manual handling.

Leaf360 custom objects map 1:1 to HubSpot custom objects if the destination portal is on HubSpot Enterprise. Custom objects require pre-creation in HubSpot Settings and at least one required field. Associations between custom objects and contacts/companies need HubSpot association types configured before migration.

HubSpot's native lifecycle_stage property tracks contact state (Subscriber, Lead, MQL, SQL, Customer, Evangelist). If Leaf360 tracks a custom borrower lifecycle (Lead, Active Loan, Paid Off, Refinance Prospect), we create a custom pick-list property (Borrower_Status__c) to preserve the full state model.