Migrate from Real Geeks to Microsoft Dynamics 365 Sales

Real Geeks Lead maps 1:1 to Dynamics Lead. Core contact fields (name, email, phone, address) migrate directly. Real estate status values (In Escrow, Closed Escrow) require custom picklist creation in Dynamics before migration. Owner resolution by email match against Dynamics users.

Dynamics 365 has no native urgency classification. We create a custom picklist field (Urgency__c) on the Lead table and map Real Geeks urgency values (Cold, Warm, Hot, Contacted, Not Contacted) plus any custom urgency values the team has added in Real Geeks.

Real Geeks statuses (Active, Cancelled, In Escrow, Closed Escrow, Dead) do not map to Dynamics out-of-box Lead Status. We create a custom RealEstateStatus__c picklist and map each value explicitly. Dynamics native Status field uses standard values (New, Contacted, Qualified) for workflow triggers.

Real Geeks timeframe (how long until buy/sell: Immediately, 1 Week, 2-4 Weeks, etc.) has no Dynamics equivalent. We create a custom picklist Timeframe__c and preserve the exact source values. This field supports lead prioritization reporting, enables Power Automate triggers based on urgency windows, and can be used in Dynamics views to surface leads nearing critical time thresholds.

Real Geeks tags are freeform labels for lead categorization. Dynamics does not have a native tags object. We create a multi-select Text field (Tags__c) and store comma-separated values. Teams using tags for segmentation should consider rebuilding as Azure AD security groups or Dynamics lead queues post-migration.

Real Geeks owner ID resolves by email match to Dynamics 365 user record. Unmatched owners are flagged before migration; the team either provisions a Dynamics license and Azure AD account for them or assigns records to a fallback owner. No record lands without an OwnerId, ensuring that all migrated leads maintain proper assignment, audit trails, and security role enforcement in the target environment.

Real Geeks captures property search queries, listing views, and saved listings as lead activities. Dynamics has no native property-activity entity. We create a custom PropertyActivity__c table with fields for PropertyAddress, SearchQuery, ActivityType, and timestamp so the history is queryable in Dynamics reports.

Real Geeks lead notes map to Dynamics Annotation records attached to the Lead. Rich-text formatting, inline images, and hyperlinks are preserved where possible, maintaining the original context of agent observations. Note owner and create timestamp migrate with the record for audit continuity. Post-migration, annotations are searchable in Dynamics, and Power Automate can trigger follow-up tasks based on note content, enabling continued collaboration without manual re-entry.

Dynamics CreatedOn is set at migration time. We preserve the original Real Geeks created date as a custom datetime field (OriginalCreateDate__c) on the Lead so historical reporting shows accurate lead age from source system. This field enables time-based pipeline analysis, helps identify trends in lead acquisition rates, and supports compliance reporting that requires the original submission timestamp. Power BI templates can reference OriginalCreateDate__c for trend dashboards.

Real Geeks lead sources (Website, Zillow, Realtor.com, PPC, Referral, etc.) map to Dynamics leadsourcecode picklist. Custom source values not in the Dynamics default list are stored in LeadSourceDetail__c as text for full fidelity. This dual-field approach preserves granular source attribution and enables segmentation in Dynamics views and Power BI reports. Power Automate flows can reference leadsourcecode or LeadSourceDetail__c to trigger source-specific follow-up sequences, ensuring consistent routing for each inbound channel.