Migrate from Real Estate 7 to Twenty CRM

Real Estate 7 contacts and leads map directly to Twenty People records. The contact's primary company link becomes a relation to a Twenty Companies record. We preserve the contact's original create date as a custom field since Twenty's createdAt is set at migration time. Email and phone are mapped directly. Owner resolution happens by email match to Twenty Workspace Members.

Real Estate 7 agency and brokerage company records map to Twenty Companies. Company name, domain (website), industry, employee count, and address fields map directly. If Real Estate 7 stores parent-child company hierarchies, we map those using Twenty's self-referential relation on the Companies object. Multi-contact companies in Real Estate 7 become one Twenty Companies record with multiple linked People records.

Real Estate 7 deals tied to property listings become Twenty Opportunities with a link to a property custom object. The deal name typically derives from the property address or listing reference. Deal amount maps to Opportunity amount. Pipeline stage from Real Estate 7 requires value mapping to Twenty's Opportunity stage pick-list values — we capture the original Real Estate 7 stage name as a custom field for reporting continuity.

Real Estate 7's property listing data (address, price, bedrooms, bathrooms, square footage, listing status, property type) migrates to a Twenty custom object named 'Property'. This object links to the People record (as the listing contact or buyer) and optionally to the associated Opportunity. We create the custom object definition in Twenty before migration and establish the relation fields during the import phase.

Real Estate 7's hot/warm/cold lead scoring migrates as a custom numeric field (Lead_Score__c) on the Twenty People object. If the source stores a numeric score (0-100), we preserve the raw number. If it uses categorical scoring, we preserve it as a custom select field with the original category values. This field is for reference — Twenty has no native behavioral scoring.

Real Estate 7 tasks and follow-up reminders map directly to Twenty Tasks. Task title, due date, completion status, and assigned owner (resolved by email match) transfer intact. Tasks linked to specific contacts or deals in Real Estate 7 get linked to the corresponding People or Opportunity record in Twenty. Original create timestamps are preserved as a custom field.

Notes from Real Estate 7 — including call notes, email body content, and general record notes — migrate as Twenty Notes. Notes are linked to the parent record (People, Companies, or Opportunities) using Twenty's relation model. Original note timestamps and note author (owner) are preserved. Rich-text formatting is converted to plain text where necessary.

Real Estate 7 activity records (logged calls, sent emails, scheduled meetings) become Twenty Notes with a note type indicator and original timestamp. Meeting details include date and duration where available. Activity owner is resolved by email match to Twenty Workspace Members. We create a custom 'Activity_Type__c' field on Notes to distinguish call, email, and meeting records.

Files attached to Real Estate 7 records — property images, contract documents, PDF reports — are downloaded and re-uploaded to Twenty Notes linked to the parent record. File size limits apply (Twenty's upload limit). Inline images in notes are extracted and stored as attachments. File metadata (original filename, upload date) is preserved as note content.

Real Estate 7 pipeline stages (e.g., 'New Lead', 'Showing Scheduled', 'Offer Made', 'Under Contract', 'Closed') map to Twenty Opportunity stage values. We perform value-by-value mapping — your Real Estate 7 stage names become Twenty stage pick-list values. Stage-enter timestamps from Real Estate 7 are preserved as custom datetime fields on each Opportunity for historical reporting.

Real Estate 7 users and deal owners are resolved by email match against Twenty Workspace Members. If a Real Estate 7 user has no matching Workspace Member email, their records are assigned to a fallback owner or flagged for manual assignment before migration. Owner history (who owned a deal at each stage) is preserved as custom fields on the Opportunity record.

Real Estate 7 WordPress custom fields (agent ID, listing source, referral channel, mortgage pre-approval amount) are audited before migration. Each custom field is mapped either to a corresponding custom field on the target Twenty object or to a custom field on the Property custom object. Field type transformation is applied as needed (e.g., text to number, date string to date field).