Migrate from Leaf360 to Freshsales

Leaf360 borrower contacts map directly to Freshsales Contacts. Email, name, phone, address, job title, and custom loan metadata transfer. Leaf360 contacts without a primary company land as Freshsales Contacts without an AccountId — your team assigns accounts after migration or during a follow-up cleanup pass.

Leaf360 loan officer contacts that represent your internal team map to Freshsales Users (agents). We resolve by email match against Freshsales user accounts. Unmatched loan officer records land as Contacts with a custom Loan_Officer__c field so the relationship is preserved even when no Freshsales user account exists yet.

Leaf360 companies and mortgage broker organizations map to Freshsales Accounts. Account name, domain/website, industry, employee count, and annual revenue transfer directly. Parent-child company hierarchies in Leaf360 map to Freshsales Parent Account field — parent records must migrate first to avoid broken lookups.

Leaf360 referral records have no direct Freshsales equivalent. We collapse them into Freshsales Deals with the referral source preserved as a custom field (Referral_Source__c) and the referral partner contact linked via the deal's contact association. Referral pipeline stage values map to Freshsales Deal Stage pick-list values per configured pipeline.

Leaf360 referral pipeline stages (e.g., Prospect, Pre-Approved, Submitted to LOS, Funded) map to Freshsales Deal Stage values value-by-value. Each Leaf360 pipeline requires its own Freshsales pipeline so stage pick-list values are scoped correctly. Probability and forecast category re-applied based on Freshsales pipeline configuration.

Leaf360's LOS Data Sync is a mortgage-specific custom field storing the integration status with loan origination systems. Freshsales has no native equivalent — we create a custom text or pick-list field (LOS_Data_Sync_Status__c) on the Contact and/or Deal object depending on where the sync data lives in your Leaf360 setup.

Leaf360's Visual App inside Follow Up Boss stores visual pipeline data and follow-up status linked to specific contacts. Freshsales does not have a native Visual App equivalent. We create custom fields (Visual_App_Status__c, Follow_Up_Boss_ID__c) on Freshsales Contacts to preserve this data for reference and future re-integration.

Leaf360 tasks with scheduling, prioritization, and status tracking map to Freshsales Tasks. Task subject, due date, priority, status, and owner transfer directly. Owner resolved by email match against Freshsales users. Standalone tasks not linked to a contact or deal land as Freshsales Tasks without a parent record.

Leaf360 collaboration notes and @mentions on contacts and deals migrate to Freshsales Notes. Original timestamps, note body content, and author information transfer. Rich-text formatting is preserved where the source format is compatible. Notes without a parent record migrate as standalone Freshsales Notes.

Leaf360 document attachments on borrower contacts and referral records re-upload to Freshsales Files. File name, content type, size, and parent record association preserved. Freshsales enforces a 25MB per file limit — files exceeding this are flagged for manual handling before the migration runs.

Leaf360 workflow automations, task triggers, and notification rules do not migrate to Freshsales. The automation logic is platform-specific and cannot be auto-translated. We export Leaf360 workflow definitions as a JSON reference document that your Freshsales admin uses to rebuild equivalent automation in Freshsales' Automation Rules and Sequences tools.

Leaf360's connections to Follow Up Boss, Arive, Lending Pad, and other third-party tools do not transfer. Each integration must be re-established in Freshsales — either through Freshworks Marketplace apps, native integrations, or API-based custom work. We provide an integration inventory checklist as part of the migration plan.