Migrate from Property Raptor to Twenty CRM

Property Raptor's Contact object maps directly to Twenty's People object. The primary email field serves as the unique identifier for deduplication and linking records across the migration. Standard Contact fields such as name, email, phone, and address components map one-to-one. No junction table handling is required unless the Contact has multiple primary Account associations, in which case FlitStack flags the record for admin review to determine the preferred primary link.

Property Raptor Account maps to Twenty Company with a straightforward field-by-field translation. Account.Name maps to Company.name, Account.Industry maps to Company.industry via pick-list value mapping for industry codes, and Account.Phone maps to Company.phone. Parent-child account hierarchies in Property Raptor, where a parent Account can have child Accounts, are preserved via the self-referential companyId relation field in Twenty. All Account records must exist before dependent Contact records are linked via AccountId.

Property Raptor Opportunity maps to Twenty Opportunity with stage and amount preserved. Opportunity.Amount maps to Opportunity.amount, Opportunity.CloseDate maps to Opportunity.closeDate, and Opportunity.StageName maps to a custom pick-list field that mirrors the original pipeline stage names from Salesforce. OwnerId resolves by matching the owner's email address to a corresponding Twenty Workspace Member record, creating an Assignee link on the migrated Opportunity.

Property Raptor inherits Salesforce's Lead object. Leads that have not converted land in Twenty as People with a custom 'Is_Lead__c' checkbox set to true. Converted Leads that created a Contact and Account are already represented by those records and do not duplicate.

Property Raptor's custom Property object — tracking property address, type, status, price, and bedrooms — migrates as a Twenty custom object named 'Property'. All custom fields on Property__c are re-created in Twenty's Settings → Data Model before the migration run. The propertyId reference on Listing__c updates to point to the new custom object.

Listing records (which associate a Property with a Contact for an active listing agreement) migrate as a Twenty custom object named 'Listing' with a relation field to the Property custom object and a relation field to the People record of the agent or owner. Listing status pick-list values are mapped value-by-value to Twenty custom select options.

Enquiry records capturing inbound leads from PropertyFinder, Bayut, Rightmove, or Zoopla migrate as a Twenty custom object named 'Enquiry' linked to the People record of the enquirer. The enquiry source (portal name) migrates as a custom select field; the enquiry timestamp becomes a date field on the custom object.

Viewing appointments linking a Property to a People record (the prospect) migrate as a Twenty custom object named 'Viewing' with date/time fields, status, and relation links to the Property and People objects. Viewing outcomes (Attended, Cancelled, No-show) map as select options.

Property Raptor's Task object (call logs, to-dos, follow-up reminders) maps directly to Twenty Task. Task.Subject → Task.title, Task.ActivityDate → Task.dueDate, Task.Status → Task.status, and Task.OwnerId resolves by email match. Completed tasks retain their status and preserve the original completion date.

Property Raptor Event records (viewings, inspections, client meetings) map to Twenty Task records with a 'meeting' type indicator in a custom field, preserving start and end datetime, location, and the related People or Property link. This keeps all activity in Twenty's unified Task view.

Property Raptor files stored in Salesforce Files are downloaded and re-uploaded as Twenty attachments on the related People, Company, or Opportunity record. The original Salesforce ContentDocument URL is stored in a custom reference field (Original_File_URL__c) for audit purposes. Files exceeding Twenty's attachment size limit are flagged for manual re-upload.

Every custom field on every object in Property Raptor is re-created in Twenty before migration runs. FlitStack delivers a schema setup plan listing each custom field, its Twenty field type, and any pick-list value mapping required. This plan is handed off before the migration executes so Twenty's data model is complete and ready for import.