Migrate from Leaf360 to Salesforce Sales Cloud

Leaf360 contacts map directly to Salesforce Contacts. Salesforce requires AccountId for most contact records — Leaf360 contacts without a primary company association get attached to a default 'Unassigned Account' record or are re-associated by a specified rule (most-recently-modified company by default).

Leaf360 leads with status 'new' or 'contacted' map to Salesforce Lead. The lead_status pick-list maps value-by-value — custom Leaf360 lead stages require explicit value mapping against Salesforce's default Lead Status values (New, Working, Nurturing, Closed — Converted, Closed — Not Converted).

Leaf360 companies map to Salesforce Account. Leaf360 parent-child company hierarchies (branch offices under a parent lender) map to Salesforce ParentId — the parent must be migrated before child accounts so the foreign key resolves on insert. Multi-company contacts collapse to one primary AccountId plus Account Contact Relations for secondary associations.

Leaf360 deals map to Salesforce Opportunities. Each deal's associated pipeline and stage map to an Opportunity StageName value scoped to the appropriate RecordTypeId. Deal amount, close date, owner, and description carry over as-is. Deals without an associated company link require an AccountId — FlitStack creates a placeholder Account or links to the contact's primary account.

Leaf360 pipeline stages map to Salesforce Opportunity StageName values value-by-value per record type. Stage probability and forecast category re-applied from Salesforce's stage metadata. Stage-entered timestamps preserved as custom datetime fields (e.g., Stage_Entered_Date__c) since Salesforce's standard stage-history tracking requires OpportunityHistory which is write-once and not populated by bulk API inserts.

Leaf360 call and email logs map to Salesforce Tasks with Type set to 'Call' or 'Email'. Leaf360 meeting records map to Salesforce Events with original start and end times preserved. Original timestamps, owners, and parent-record lookups (WhoId on Task for Contact/Lead, WhatId for Account/Opportunity) are maintained so activity timeline reporting works in Salesforce.

Leaf360 notes map to Salesforce Notes (the enhanced Notes object, not the legacy Note). Rich-text body content and title carry over. If the note references a specific deal or contact, the parent-record link is resolved to the migrated Salesforce ID. Notes without a valid parent record are attached to a placeholder parent flagged for admin review.

Leaf360 file attachments on records are downloaded and re-uploaded to Salesforce Files. Files are linked to the corresponding Salesforce record via ContentDocumentLink. Salesforce's default 25MB per-file limit applies — files exceeding this threshold are flagged for manual review or chunked upload.

Every Leaf360 custom property requires a corresponding custom field created in Salesforce before migration data loads. FlitStack delivers a custom-field creation manifest with the field label, API name (appended __c), data type mapping (string → Text, number → Number, date → Date, pick-list → Picklist), and default value for each custom property. Salesforce field-level security (FLS) is set to read-write for the migration profile during the load.

Leaf360 stores referral partner type (Agent, Broker, TPO, Past Client) as a native property on contact and company records. Salesforce has no built-in referral-source field. The value migrates as a custom pick-list field (Referral_Source__c) on Contact and Account — values are mapped one-to-one from Leaf360's pick-list options. If a new referral source type exists in Leaf360 that has no Salesforce equivalent, it is preserved as a custom pick-list value added during schema setup.

Leaf360 owner IDs are resolved to Salesforce User records by email address match. Users who exist in Leaf360 but not in Salesforce are flagged before migration — the team either invites them to Salesforce first or assigns their records to a designated fallback owner. No opportunity or contact lands in Salesforce without a valid OwnerId.

Leaf360 workflows, referral-triggered automations, and email sequences do not have a Salesforce equivalent. FlitStack exports the workflow definitions as a JSON reference document so your Salesforce admin can rebuild equivalent logic in Flow. The rebuild reference includes trigger conditions, action steps, and filter criteria captured from Leaf360's export.

Leaf360's Canopy TPO and wholesale channel data (loan type, TPO status, broker license number) maps to either a Salesforce custom object (for complex TPO relationship tracking) or a set of custom fields on the Account and Opportunity objects. FlitStack surfaces the mapping plan in the pre-migration schema review and your admin chooses the architecture before data lands.