Migrate from Leaf360 to Twenty CRM

Leaf360 People records — including loan officers, borrowers, referral partners, and real estate agents — migrate directly to Twenty People objects. Core contact details such as name, email address, phone number, and job title transfer over intact. Property address, loan officer assignment, and referral source data migrate as custom fields on the Twenty People record. The migration preserves the relationship between contacts and their associated company records via companyId linking, which requires the company data to be loaded first in the import sequence.

Leaf360 Companies representing lenders, real estate brokerages, and title companies migrate to Twenty Companies objects. Standard fields including company name, domain, industry classification, employee count, and annual revenue map directly without transformation. The company-to-person relationship is preserved through the companyId foreign key on the Twenty People record, which references the corresponding Companies object after the Companies table is populated first to ensure referential integrity during the import process.

Leaf360 Deals — mortgage applications, purchases, refinances — migrate to Twenty Opportunities. Leaf360's mortgage-specific pipeline stages (Application Submitted, Underwriting, Approval, Clear to Close, Closed) map to Twenty Opportunities StageName values. Stage history stored in custom datetime fields. Loan amount, property address, and loan type migrate as custom fields.

Leaf360 Notes attached to People, Companies, or Deals migrate to Twenty Notes and maintain their association to the parent record through the foreign key relationship. Rich-text formatting is preserved where Leaf360's export format supports it, ensuring that bold text, bullet points, and hyperlinks carry over intact. Original creation timestamps and author information are migrated as separate metadata fields, allowing teams to preserve the complete audit trail for compliance and reference purposes after the migration completes.

Leaf360 call logs, email tasks, and to-dos migrate as Twenty Tasks, preserving the activity history for each contact and company record. Call-specific metadata including call type (inbound, outbound, follow-up), call outcome, and call duration in minutes map to custom fields on the Task object in Twenty. Tasks maintain their parent relationship through the fortyId and relatableId fields, linking each task to its associated People, Company, or Opportunity record for complete contextual visibility within the migrated dataset.

Leaf360 custom properties on People, Companies, and Deals translate to Twenty custom fields. Field type (text, number, date, select) is replicated. Pick-list values from Leaf360 become Twenty select options. All custom fields must be created in Twenty Settings > Data Model before the CSV import runs.

Leaf360's referral source property on People records — tracking where borrowers came from (agent referral, website, direct) — migrates as a custom select field (Referral_Source__c) on Twenty People. Pick-list values are carried over as-is. Real estate partner referrals from Leaf360's FUB/Arive integrations surface as Activity records if the integration data is accessible via export.

Loan files, disclosure documents, and other attachments stored in Leaf360 are re-uploaded to Twenty's file attachment system and linked to the parent People or Opportunity record. Twenty's file size limits apply. Inline images in notes are downloaded and re-hosted as Twenty Files.

Leaf360 owner records (loan officers, admins, team members) become Twenty Workspace Members. Owner resolution on migrated records uses email matching — the Leaf360 owner email must match a Twenty Workspace Member email. Unmatched owners flagged before migration so records can be assigned to a fallback owner.

Leaf360 workflows, automated triggers, marketing sequences, and drip campaigns do not migrate. FlitStack exports the workflow definitions as a reference document so your Twenty admin can rebuild them in Twenty's workflow builder or via API-based automation tools. Plan time for this configuration work — it is not included in the data migration scope.