Migrate from Real Estate CRM to Twenty CRM

Real Estate CRM contacts map directly to Twenty's People object, which stores name, email, phone, job title, address fields, and a companyId relation linking each person to its associated company. Owner assignments from Real Estate CRM resolve by matching the owner email to Twenty workspace members before record insertion, preserving the original createdAt and updatedAt timestamps as custom datetime fields for audit continuity.

Real Estate CRM company records map to Twenty's Companies object, which holds the company name, domain/website, industry, employee count, annual revenue, and a full address compound field (street, city, state, postal, country). If the source includes custom pick‑list values for industry, FlitStack creates matching select options in Twenty before import, ensuring clean mapping without manual correction.

Real Estate CRM deals map to Twenty Opportunities. Each Opportunity links to a Company via companyId and optionally to a Person via peopleId. Stage names require value-by-value mapping because Real Estate CRM pipeline stages and Twenty Opportunity stages rarely share identical labels.

Real Estate CRM pipeline stages become a custom Select field on the Twenty Opportunity object. Each source stage label maps to a defined Twenty select option. Stage probability values are stored as a separate custom Number field for reporting continuity.

Real Estate CRM may use lifecycle stage or lead status to track where a contact sits in the sales funnel. Twenty has no native equivalent, so FlitStack creates a lifecycle_stage__c custom Select field on the People object with the exact values from the source system.

Notes from Real Estate CRM migrate to Twenty Notes, linking each note to a People or Company record via targetId and targetObjectName. Rich‑text formatting is retained when the source export provides HTML; plain text imports without formatting loss. Any source‑only metadata (e.g., note category) is stored as a custom text field on the Twenty note for future reference.

Real Estate CRM tasks and to‑dos migrate to Twenty Tasks, attaching to a People, Company, or Opportunity via the linkableObjects array. Task status (open/done), due date, and assignee are resolved by matching the assignee email to a Twenty workspace member; unresolved assignees are flagged for team‑level remediation. Original createdAt timestamps are preserved as a custom datetime field for historical tracking.

Many Real Estate CRM setups include a Property or Listing custom object holding address, listing type, price, status, and agent assignment. This maps to a Twenty Custom Object named 'Property' — fields map individually and the object links to the relevant Company or Opportunity.

Transaction records from Real Estate CRM — including commission amount, close date, buyer/seller party, and property reference — migrate to a Twenty Custom Object named 'Transaction'. Foreign keys to People and Company are resolved using email and domain lookup keys respectively, ensuring referential integrity before the transaction rows are inserted. Any source‑specific fields not present in Twenty's standard schema become custom fields defined during schema design.

Real Estate CRM owner IDs map to Twenty workspace members by email address lookup. Unmatched owners are flagged before migration — the team either invites those users to Twenty first or assigns records to a designated fallback workspace member. Source owner IDs are preserved as a custom field for audit.

File attachments stored in Real Estate CRM are exported to a local file store and delivered alongside the migration package. Twenty's file upload is a UI-based operation — FlitStack provides a file manifest so your team can re-associate attachments to the correct records post-migration.

Real Estate CRM may log call records, email threads, and meeting history as engagement objects. Twenty's activity model is simpler — calls and meetings are not native record types. FlitStack preserves the text content of recent engagement records as Notes on the relevant People record; historical activity is flagged as a rebuild candidate in Twenty.