Migrate from Real Geeks to Odoo CRM

Real Geeks Lead maps directly to Odoo crm.lead. The lead's contact fields (name, email, phone) create or match a res.partner record via partner_id many2one. Lead status and urgency values require custom field creation in Odoo or stage/value mapping. This mapping also preserves the original lead ID in a custom field for audit and de-duplication purposes.

Real Geeks contact information (first_name, last_name, email, phone, address) maps to Odoo res.partner. If the lead includes company data, partner records with company_type='company' are created first; individual contacts then link via parent_id. During migration, FlitStack AI checks for duplicate partner records by email and merges them when necessary to avoid duplication.

Real Geeks five status values (Active, Cancelled, In Escrow, Closed Escrow, Dead) map to Odoo crm.lead.stage_id. We create custom stages matching Real Geeks terminology. Cancelled and Dead leads can be set to inactive in Odoo or archived after migration. If your workflow requires further segmentation, additional stage fields can be introduced.

Odoo has no native urgency field. Real Geeks urgency values (Cold, Warm, Hot, Contacted, Not Contacted) migrate to a custom selection field x_urgency on crm.lead. Your team can map these to Odoo's priority field (stars) or keep as a separate selection.

Real Geeks timeframe field (Immediately, 1 Week, 2-4 Weeks, 30 Days, 60 Days, 90 Days, 3-6 Months, 6-12 Months, 1 Year Or More) maps to a custom selection field x_timeframe on crm.lead. This signals buying/selling readiness and is preserved for sales follow-up prioritization.

Real Geeks lead notes migrate to Odoo crm.lead.description, a text field. If notes contain structured data (call logs, appointment summaries), they appear as plain text in description. Rich-text formatting from Real Geeks is not preserved. You can later reformat the text in Odoo using its rich-text editor if desired.

Real Geeks tag list maps to Odoo crm.lead.tag_ids. Tags are matched by name — new tags are created in Odoo if no match exists. Tag consistency across leads is preserved. Multiple tags per lead are supported in both platforms. During migration, FlitStack AI also records the original tag IDs for future reference and de-duplication.

Real Geeks tracks which properties a lead viewed or saved. This data migrates as a custom text field x_property_interests on crm.lead, with the most recent property URLs listed in the description. Odoo has no native property-search tracking — this is preserved as reference data.

Real Geeks lead source data (website form, Zillow, Realtor.com, API import) maps to Odoo crm.lead.source_id. If the source string does not match an existing UTM source in Odoo, a new utm.source record is created. Source attribution is preserved for campaign reporting.

Real Geeks created timestamp migrates to Odoo crm.lead.create_date. Odoo's create_date is set by the database at insertion time — we override it with the original Real Geeks date so reporting continuity is maintained. Original create date is also stored in a custom field for audit.

Real Geeks last_modified timestamp maps to Odoo crm.lead.write_date. This preserves the last activity date in Real Geeks so your team can prioritize follow-up without relying on Odoo's activity logging alone. The write_date is set during the migration script and reflects the exact moment of the last change recorded in Real Geeks, ensuring continuity in reporting.

Real Geeks agent/owner assignment is resolved by matching agent email to Odoo res.users login. Unmatched owners are flagged before migration — your team either creates Odoo user accounts first or assigns records to a fallback user. No crm.lead lands without a user_id.

Real Geeks activity records (call logs, email sent, meeting notes) migrate to Odoo mail.message records linked to the crm.lead via res_id and model fields. Activity type, timestamp, and body content are preserved. Odoo native activity counts and next activity dates are set based on the most recent engagement.