Migrate from Leaf360 to Microsoft Dynamics 365 Sales

Leaf360 Contact maps directly to Dynamics 365 Sales Contact. Leaf360 stores loan_officer as a contact property; this resolves to the Contact's OwnerId via email match. Leaf360 contact-level loan_status values route to the Contact's custom LoanStatus__c field. Records without a primary company land on a default placeholder Account.

Leaf360 contacts flagged as referral partners (referral_source = 'Partner') migrate as Dynamics 365 Sales Contacts but also receive Connection records linking them to the loan officer Contacts they referred. The Connection record type 'ReferredBy' is created in the destination before migration runs.

Leaf360 Company maps to Dynamics 365 Sales Account. Property_address on a Leaf360 company migrates as a custom Address field on the Account. Leaf360 company hierarchies (parent/child) map to Account.ParentAccountId. Multi-company contacts collapse to a primary AccountId plus Account Contact Relationships in Dynamics 365 Sales.

Leaf360 Deal maps to Dynamics 365 Sales Opportunity. The deal's loan_amount maps to Opportunity.Amount, closedate maps to Opportunity.CloseDate, and dealname maps to Opportunity.Name. The LoanOfficer__c custom field stores the originating loan officer name. Each Deal's pipeline in Leaf360 maps to a Business Process Flow in Dynamics 365 Sales.

Leaf360's pipeline object becomes a Dynamics 365 Sales Business Process Flow (BPF). Each Leaf360 stage in the pipeline (Pre-Approval, Processing, Underwriting, Clear to Close, Funded) becomes a BPF stage with its own stage name and step requirements. The BPF is pre-created before data lands so Opportunities can attach to it on ingest.

Leaf360 loan_status pick-list values (Pre-Approval, Processing, Underwriting, etc.) map value-by-value to Dynamics 365 Sales Opportunity StageName pick-list values. We apply probability weights per stage from your existing Leaf360 stage configuration. Stage-transition timestamps from Leaf360 are preserved as custom datetime fields on the Opportunity.

Leaf360 custom fields — identified via the custom-fields API — are enumerated, typed, and mapped to Dataverse custom columns. loan_type and property_address typically land on Opportunity; preapproval_date lands on Contact or Opportunity depending on where Leaf360 stored it. Sales Professional setups are limited to 15 custom tables; Sales Enterprise allows unlimited custom columns per table.

Leaf360 engagement records (call, email, meeting, note) map to Dynamics 365 Sales activity tables: PhoneCall, Email, Appointment, and Note respectively. Original timestamps, owner (resolved by email), and the Regarding lookup back to the parent Contact or Opportunity are preserved during migration.

Leaf360 file attachments on records migrate as Dynamics 365 Sales Annotations. The file is downloaded from Leaf360, uploaded to Dataverse document storage, and attached to the matching Contact, Account, or Opportunity record. File size limits (default 128MB per annotation in Dataverse) are enforced; files exceeding the limit are flagged for manual handling.

Leaf360 referral_source properties on deals and contacts create referral relationships that map to Dynamics 365 Sales Connection records. A Connection with type 'ReferredBy' links the referral partner Contact to the referred loan Contact or Opportunity. Connection records require the Connections Hub solution to be enabled in the Dynamics 365 Sales environment before migration.

Leaf360 automations (lead routing rules, drip sequences, task-creation triggers, SLA timers) are not migrated. FlitStack exports your Leaf360 workflow definitions as a structured JSON document that your Dynamics 365 admin can use as a reference to rebuild equivalent automations in Dynamics 365 Sales Workflow or Power Automate. The rebuild is a separate services engagement.

Leaf360 reports and dashboards do not migrate. The underlying data (contacts, accounts, opportunities, activities) migrates completely, so rebuilding reports in Dynamics 365 Sales or Power BI starts from the same data. We provide a data dictionary of migrated fields so your BI team can reconnect existing Power BI reports to the Dataverse tables.