Migrate from Real Geeks to Freshsales

Real Geeks lead records migrate 1:1 into Freshsales Leads. Freshsales Lead object accommodates first name, last name, email, phone, address, and all standard contact fields natively. Real Geeks urgency and timeframe fields migrate as custom pick-list fields since Freshsales has no native urgency or buying-timeframe field. Owner assignment resolves by email match to Freshsales users.

Real Geeks does not expose a separate companies object — company data lives as fields on each lead record. FlitStack extracts unique company names during the export phase, deduplicates them, and creates Freshsales Account records. Each lead then links to its primary Account via the Account lookup. Leads sharing the same company name collapse to a single Account with multiple linked leads.

Real Geeks status values — Active, In Escrow, Closed Escrow, Dead, Cancelled — have no direct Freshsales equivalent. We create a custom pick-list field (Real_Estate_Status__c) on the Freshsales Lead and map each value by name. Teams using the Pro/Enterprise pipeline model may opt to convert 'Closed Escrow' records to Won Deals and 'Cancelled' records to Lost Deals with reason capture.

Real Geeks tracks deal-like records (active leads with an associated property transaction) as part of the lead record. FlitStack identifies leads with a meaningful deal association — e.g., those in In Escrow or Closed Escrow status — and creates Freshsales Deals linked to the lead's Account and Contact. Deal name, amount, close date, and owner map from Real Geeks lead fields to Freshsales Deal fields.

Real Geeks does not expose a formal pipeline object with configurable stages via its API — deal stage is stored as a status field on the lead. For Freshsales, we create a Sales Pipeline with stages that mirror the Real Geeks lifecycle: New Lead → Contacted → In Escrow → Closed Escrow (Won) / Dead (Lost). Each stage maps to a Freshsales Deal Stage value. Teams on Pro/Enterprise can add additional stages post-migration.

Real Geeks saved searches act as dynamic filters that agents use to segment their database. Freshsales has Views and Advanced Filters but no direct saved-search migration. We capture the filter criteria (status, urgency, source, date range) as a JSON blob in a custom text field (Saved_Search_Criteria__c) and document the equivalent Freshsales View setup for the admin to recreate.

Real Geeks tracks lead origin — website, Facebook, PPC, Zillow, Realtor.com — in a source field on the lead record. This maps directly to Freshsales Lead Source pick-list. Custom lead sources in Real Geeks require value-mapping on the Freshsales side to ensure the pick-list covers all source variants.

Real Geeks tag field stores comma-separated agent-applied labels on leads. Freshsales supports native Tags on Leads, Contacts, Accounts, and Deals. Tags migrate as-is. Freshsales applies tags to the record type — no transformation needed. Duplicate tags (case variations) are normalized during migration.

Real Geeks notes field on lead records migrates as Freshsales Notes attached to the corresponding Lead. Each note preserves the original text content and timestamp. If the note references another lead or property, the cross-reference is noted in the note body for manual follow-up.

Real Geeks assigns each lead to a user (agent or admin). FlitStack resolves the owner by matching the Real Geeks owner email against Freshsales user emails. Unmatched owners are flagged in a pre-migration report — the team either invites them to Freshsales first or assigns their records to a fallback owner. No record lands in Freshsales without a resolved owner.

Freshsales CreatedDate is set to the migration run timestamp, not the original lead creation date. To preserve historical reporting continuity, we store the original Real Geeks create date in a custom datetime field (Original_Create_Date__c) on the Freshsales Lead. This allows agents to sort and report on true lead age after migration.

Real Geeks custom lead detail fields added via CRM settings migrate as Freshsales custom fields on the Lead object. Field types are preserved — text to text, pick-list to pick-list, number to number. Lookup-type custom fields in Real Geeks that reference other Real Geeks records are flagged for manual review since cross-record references do not translate directly to Freshsales lookups.