Migrate your Leaf360 data

Leaf360 stores borrower and referral contact records with standard fields (name, phone, email, address). We migrate Contacts 1:1, preserving any custom properties mapped during scoping. Email and phone formatting is harmonised to E.164 where needed.

Company/Account records represent real estate brokerages, lenders, or employer organisations linked to Contacts. We migrate Companies with their associated contact links intact.

Deals represent active loan applications or referral transactions. Leaf360 organises Deals into Pipeline stages. We migrate Deals with their stage, owner, value, and close date preserved. Stage names vary by customer configuration and may require mapping at the destination.

Leaf360 supports configurable Pipeline stages reflecting the mortgage workflow (e.g., Application, Processing, Underwriting, Clear to Close, Funded). Stage names are customer-defined. We preserve the full stage list and map them to equivalent stages in the destination CRM, flagging any stages that have no direct equivalent.

Inbound referral leads from real estate agents and partners are a primary object in Leaf360. We migrate Leads with source attribution, referral partner link, and status. Where the destination CRM uses a unified Contact object, we merge and preserve lead source as a custom property.

Task records represent follow-up actions tied to Deals or Contacts. We migrate Tasks with assignees, due dates, status, and descriptions preserved.

Activity history (calls, emails, notes) attached to Contacts or Deals is migrated as a chronological log. We preserve the full activity body, timestamp, and owner.

Loan officers and team members are stored as Users with roles. We map Users to corresponding Owner/User records in the destination, flagging any inactive users that should be archived rather than migrated as active.

Referral Partners are a distinct entity type in Leaf360 linking real estate agents to Deals and Leads. We migrate the partner record and its association log. Where the destination CRM does not have a native partner object, we create a Company or Contact record and flag it for reference.

Leaf360 supports custom fields on Users and Contents (as documented in their API). We enumerate all custom fields during scoping and map each to its destination equivalent, creating new fields in the destination if none exists.

Integration configurations (Follow Up Boss, Lending Pad, CanopyTPO, Arive) are platform-specific OAuth connections that cannot be exported and must be re-established manually in the destination. We document each active integration during discovery so the customer can reconnect them post-migration.

Documents and files attached to Deals or Contacts are migrated as downloadable references. We preserve file names, upload dates, and associations, but file content must be extracted via the API or direct database read and re-uploaded to the destination.