Migrate from Real Geeks to Twenty CRM

Real Geeks lead contact records map directly to Twenty People. Every Real Geeks contact field (name, email, phone, address) populates the corresponding Twenty People field. The People record is the primary entity — Real Geeks does not separate contacts from leads; both live in the same Lead Manager object.

Real Geeks lead status values (Active, In Escrow, Closed Escrow, Dead, Cancelled) map to Twenty Opportunity stage pick-list values. The migration plan defines the stage mapping before import so status integrity is preserved. Closed Escrow and Dead map to Twenty's Closed Won and Closed Lost respectively. Cancelled maps to a custom Closed Cancelled stage if configured.

Real Geeks urgency tiers (Cold, Warm, Hot, Contacted, Not Contacted) and any custom urgency values added by the admin have no Twenty native equivalent. We create a custom select field (Urgency__c) on the People object in Twenty's Settings → Data Model before migration. Each urgency value in Real Geeks maps to the corresponding label in the new field.

Real Geeks timeframe (Immediately, 1 Week, 2-4 Weeks, etc.) signals buying readiness. Twenty has no native timeframe field on Opportunities. We create a custom select field (Buying_Timeframe__c) and map each Real Geeks value verbatim. CloseDate on the Twenty Opportunity captures the date dimension separately.

Real Geeks tags are free-form string identifiers attached to leads — no controlled vocabulary. We create a custom multi-select field (Lead_Tags__c) on People. All tags from a Real Geeks lead are collected and stored as selected values in the multi-select field, preserving the full tag set per contact.

Real Geeks notes on each lead transfer to Twenty Note records linked to the corresponding People record. The note body carries the full text content from Real Geeks. Notes are imported after People records exist so the foreign key resolves correctly during the migration run.

Real Geeks allows linking a lead to a company record (via the lead's company name field). Those company names are created as Twenty Company records first, then linked to People via companyId on the Person import. Real Geeks does not expose a separate Companies export — company data is inferred from the lead records.

Real Geeks owner assignment is stored as a user reference on each lead. We resolve owner email addresses against Twenty workspace members by email match. Unmatched owners are flagged before migration so your team can pre-invite them to Twenty. Leads without a resolvable owner assign to a designated fallback workspace member.

Real Geeks /activities API returns property search events, listing views, and outreach timestamps. Each activity maps to a Twenty Task (for outreach events: calls, emails, follow-ups) or a Note (for property search context). Tasks carry subject, due date, and assignee; Notes carry body text with the activity detail. Both link back to the relevant People record.

Any custom properties added to Real Geeks lead records (beyond the standard fields) are enumerated during the discovery phase. Each custom field is created in Twenty's Settings → Data Model before import, with the field type chosen to match the data (text, number, select, etc.). Custom field values transfer verbatim on migration.

Real Geeks tracks where a lead originated (website, PPC, referral, etc.). We capture this as a custom text or select field (Lead_Source__c) on the People record. If the source detail field is populated in Real Geeks, it populates alongside the primary source in the custom field for complete attribution.

Real Geeks stores a last communication date on leads. Twenty Tasks track follow-up activity but does not have a dedicated last-contacted date. We preserve the Real Geeks last communication date as a custom datetime field (Last_Contact_Date__c) on the People record for reporting continuity.