Migrate from Funnel Leasing to Twenty CRM

Funnel prospects map directly to Twenty People. Each prospect's name, email, phone, and contact details migrate as standard People fields. Owner resolution happens by email match against Twenty workspace members — unmatched owners flag before migration runs so you can invite users first.

Funnel prospects who have submitted a rental application get a companion Twenty Opportunity created automatically. The Opportunity links to the People record and carries the deal name, amount (monthly rent), and Funnel pipeline stage as the initial Opportunity stage in Twenty.

Funnel company records represent property management companies, landlords, or other organizations in the Funnel system. These records map directly to Twenty Companies with name, website, industry, phone, and address fields migrating as standard Company fields. Funnel's parent-company hierarchy — where one company can be the parent of other companies — translates to Twenty's Parent Company link on the Companies object, preserving organizational structure in the new CRM.

Funnel's property entity (apartment buildings, communities) has no native equivalent in Twenty's standard schema. We create a Property custom object in Twenty with fields for address, unit count, property type, and a relation to the parent Company. If your team prefers to keep property data embedded, we use Company custom fields instead.

Funnel deal pipelines map to Twenty Opportunities. Each pipeline stage in Funnel (Inquiry, Tour, Application, Lease Signed) becomes a Twenty Opportunity stage value. The Funnel deal amount — typically the monthly rent or lease value — migrates as the Opportunity amount. Stage-entered timestamps are preserved as custom datetime fields for reporting continuity.

Funnel's lease agreements have start date, end date, monthly payment, and security deposit — none of which map to Twenty's standard Opportunity fields. We create a Lease custom object in Twenty with lease start, lease end, monthly rent, deposit amount, and status pick-list (Active, Expired, Renewal Pending), linked to the People (tenant) and Company (property) records.

Funnel's omnichannel activity log — calls, emails, meetings, and text messages — maps to Twenty Tasks. The Task type field carries the original channel (Call, Email, Meeting, SMS). Original timestamps, owners, and parent-record links (People, Company, or Opportunity) are preserved on the Task record.

Funnel notes attached to prospect, company, deal, or lease records migrate as Twenty Notes with all content preserved. Rich-text formatting — bold, italic, bullet points, tables — converts to Twenty's supported formatting. Notes that contain lease-specific data like terms, rent amounts, or property details get those values embedded as plain text within the Note body, ensuring all contextual information from Funnel carries over into Twenty's Notes object intact.

Funnel's custom prospect properties (routing preference, source channel, referral code) become custom fields on the Twenty People object. Each custom field must be created in Twenty's Settings → Data Model before the CSV import runs — the migration plan surfaces all custom property names and their data types for pre-creation.

Funnel owners assigned to prospects or deals resolve by email match against Twenty workspace members. Funnel's team structure (regional managers, leasing agents) maps to Twenty Workspace Members. If a Funnel owner has no matching Twenty user, records are assigned to a fallback owner you designate before migration.

Funnel attachments (rental applications, ID documents, lease PDFs) have no native storage equivalent in Twenty's base import. We download files to a managed storage location and store a link in a custom URL field on the related People or Lease record. You can migrate the files separately into your preferred document storage.

Funnel's AI leasing workflows, follow-up sequences, and chatbot logic do not have a migration path. We export the workflow definitions (trigger conditions, action steps, timing rules) as a reference JSON file so your Twenty admin can rebuild equivalent automations in Twenty's workflow builder.