Migrate from Leadrat CRM for Real Estate to Twenty CRM

Leadrat leads map directly to Twenty People. Every lead record — including name, email, phone, source, and status — becomes a People record in Twenty. Owner resolution happens via email match against Twenty Workspace Members. Leads without an email receive a generated placeholder address to allow import, flagged for manual verification.

Leadrat contacts (the contact sub-type distinct from leads) map to Twenty People with the same field-level mapping as leads. If a Leadrat contact and lead share the same email address, FlitStack deduplicates them into a single Twenty People record during import, preserving all activity history from both source records.

Leadrat company records map to Twenty Companies. Company name, website, industry, phone, address, city, state, country, and postal code migrate directly. Parent-child company hierarchies in Leadrat map to the Twenty Companies relation field where available. Multi-company associations on a single Leadrat contact collapse to the primary company link in Twenty.

Leadrat deals map to Twenty Opportunities. Deal name, amount, stage, close date, pipeline name, owner, and creation timestamps migrate. Stage names in Leadrat (e.g., New Lead, Site Visit, Negotiation, Closed Won) map to Twenty Opportunity stage values via a value-mapping table. The mapping preserves stage-enter timestamps as custom datetime fields in Twenty for reporting continuity.

Leadrat's built-in property object — which tracks property name, type, status, price, location, bedrooms, bathrooms, and area — migrates to a Twenty custom object named 'Property'. All standard property fields become custom fields on the Property object. The property record links to the People record (prospect/buyer) and the Opportunity record (deal) via Twenty's relation fields. The custom object and all fields must be pre-created in Twenty Settings → Data Model before the migration import runs.

Leadrat projects (development or building projects linked to multiple properties) migrate to a Twenty custom object named 'Project'. Project fields — project name, developer, launch date, status, and associated properties — become custom fields on the Project object. The Project object links to multiple Property records via Twenty's one-to-many relation, and to Companies records representing the developer or builder.

Leadrat tasks (follow-up reminders, site-visit tasks, call-back tasks) map to Twenty Tasks. Task title, description, due date, assignee (via email resolution), status, and linked record (People or Opportunity) migrate. Completed status and completion timestamps are preserved. Tasks without a linked record import as standalone Twenty Tasks.

Leadrat meeting logs and site-visit records — which include date, attendees, property visited, outcome, and notes — migrate to Twenty Notes attached to the relevant People and Property records. The note body captures the full site-visit summary. Date and attendee information is embedded in the note text for traceability since Twenty lacks a native meeting object.

Leadrat call logs (call direction, duration, disposition, date) migrate as Twenty Tasks with Type='Call'. The task subject carries the call direction and contact name; the task description holds the call notes and disposition. Original call date and duration are preserved as custom datetime and number fields on the task record.

Leadrat file attachments on leads, deals, or properties are re-uploaded to Twenty Notes as file attachments. If the attachment is a property brochure or floor plan, it attaches to the corresponding Property custom object record. Standard file size limits for Twenty's storage backend apply; oversized files are flagged for manual handling.

Leadrat lead status values (New, Follow Up, Qualified, Lost, Converted) have no direct equivalent in Twenty's standard People object. A custom select field named 'Lead_Status__c' is created on People and populated with the source status values during migration for reporting continuity.

Leadrat lead source (Facebook, Google Ads, Portal, Referral, Walk-in, etc.) migrates as a custom select field 'Lead_Source__c' on the Twenty People object. Portal-specific source values (Bayut, Property Finder) that have no equivalent in Twenty are preserved as-is in the custom field with a note that Zapier/Make integrations can be used to route portal leads to the correct source value post-migration.