Migrate from Real Properties to Twenty CRM

Real Properties contacts map 1:1 to Twenty People records. Email, phone, job title, and address fields migrate as standard Twenty People fields. The contact's primary company link resolves to a Twenty Company record by domain match during the migration pass. If a matching Company record doesn't exist, the contact is flagged for manual resolution before the full migration run. Duplicate detection runs on email address to prevent duplicate People records in Twenty.

Real Properties company records map directly to Twenty Companies. Company name, domain/website, industry, employee count, and annual revenue migrate as standard Company fields. Parent-company hierarchies map to Twenty's Parent Company relation when configured. Companies without a parent company in the source map as top-level organizations. Industry pick-list values that don't match Twenty's default options are created as custom select options in the target workspace.

Real Properties property records require a custom object in Twenty. Property-specific fields including address components, price, square footage, property type, MLS number, bedrooms, and bathrooms migrate as custom fields on the Property custom object. The Property object links to a Company record for the listing brokerage and to Opportunities for deal associations. Your Twenty admin must create this custom object in Settings > Data Model before migration begins.

Real Properties deals map to Twenty Opportunities. Deal name, amount, stage, close date, and owner migrate directly as standard Opportunity fields. Pipeline stages map to Twenty Opportunity stage values on a value-by-value basis using the source pipeline name as the key. Probability percentages from Real Properties stage configuration re-apply to the corresponding Twenty stage values. Deals without a stage assignment are flagged for manual stage assignment before the migration run.

Real Properties links deals to properties through a junction relationship where one deal can involve multiple properties such as portfolio sales. In Twenty, the Property custom object receives a relation to Opportunity, and deal-property links migrate as Opportunity-Property relation records using the property's unique source system identifier. If a deal references multiple properties, FlitStack AI creates multiple relation records linking that single Opportunity to each Property record.

Real Properties pipelines with multiple configurable stages such as Prospecting, Showing, Offer, Under Contract, and Closed map to a Twenty Opportunity stage set. Stage names and probability percentages are mapped value-by-value using the source pipeline name as the grouping key. Forecast category assignments from Real Properties are preserved as a custom pick-list field on Opportunity since Twenty handles forecast categorization differently. Your Twenty admin configures the stage set in Settings > Opportunities before migration.

Real Properties notes and activity logs migrate as Twenty Notes attached to the relevant People, Company, Property, or Opportunity record based on the source record association. Original create timestamps and owner assignments are preserved as note metadata including the original author and creation datetime. Activity type classifications from Real Properties are stored as a custom select field on the Note object for reporting purposes. Notes without a valid parent record are flagged for manual attachment during migration.

Real Properties tasks migrate to Twenty Tasks linked to the parent record which may be a People, Company, Opportunity, or Property custom object. Due dates, assignees, and completion status are preserved including whether the task is open, completed, or cancelled. Open tasks fire as Twenty workflow triggers after migration completes. Overdue tasks retain their original due date for prioritization in Twenty's task view. Task subject lines map to the Task title field directly.

Real Properties owners resolve to Twenty Workspace Members by email match during the pre-migration resolution pass. Unmatched owners are flagged by name and email address so your team can invite them to Twenty first or assign a fallback user. Records without a valid owner after resolution assign to the fallback user specified in the migration plan. Owner resolution prevents orphaned records in Twenty where no Workspace Member is assigned.

Property photos, listing documents, and contract attachments migrate as Twenty file attachments on the relevant Property, Company, or Opportunity record. Files re-upload to Twenty's storage system from the source URL or local export; original filenames and MIME types are preserved in the attachment metadata. File size limits apply per Twenty's hosting configuration; files exceeding 25MB are flagged during the data audit and the original URL is stored in a custom text field for reference.

Real Properties custom fields on Property records migrate as custom fields on the Property custom object in Twenty. Field types map on a type-aware basis: text to text, number to number, pick-list to select, and date to date. Custom field API names are preserved from Real Properties for traceability in the migration audit log. Pick-list values from Real Properties are created as select options in Twenty. Required field settings are honored if the target field has a value in the source.

Real Properties custom fields on deals migrate as custom fields on Twenty Opportunities. Commission split percentage fields, referral source pick-lists, and contingency fields map with type-aware transformation to preserve data integrity. Field order and group labels from Real Properties are exported as a human-readable rebuild reference document so your Twenty admin can recreate the original field layout in the Opportunity layout editor. Pick-list values for referral source are created as custom select options matching the source values.