Migrate from Real Geeks to Pipedrive

Real Geeks Lead maps directly to Pipedrive Person. Core contact fields (name, email, phone, address) transfer as standard Person fields. The Person object in Pipedrive holds all primary contact information; multiple phones and addresses are supported via the phones and addresses sub-objects.

Real Geeks stores company name as a text field on the Lead record. In Pipedrive, companies are stored as Organization records with a separate Person.OrganizationId lookup. We create one Organization per unique company_name value during migration, then link the Person to it. Leads without a company_name get a placeholder Organization or land as Persons without an organization link.

Real Geeks urgency values (Cold, Warm, Hot, Contacted, Not Contacted, plus any custom values) map to a Pipedrive custom pick-list field on the Person object. We preserve all source values exactly and flag any custom urgency tiers that do not have a direct Pipedrive equivalent for admin review.

Real Geeks lead status (Active, In Escrow, Closed Escrow, Cancelled, Dead) does not map cleanly to Pipedrive's Lead or Person objects. We create a Deal record per active lead to capture the pipeline stage — status becomes a custom field on the Deal, and Close date is set to the estimated close based on timeframe field. Closed Escrow and Cancelled leads create Deals at the Won or Lost stage.

Real Geeks timeframe values (Immediately, 1 Week, 2-4 Weeks, 30 Days, 60 Days, 90 Days, 3-6 Months, 6-12 Months, 1 Year Or More) map to a custom pick-list on the Pipedrive Deal. Pipedrive Deal has a close_date field — we estimate close_date from the timeframe value, flagging records where manual review of the actual buy/sell timeline is needed.

Real Geeks tags migrate as a comma-separated custom field on the Pipedrive Person. Pipedrive's native tag feature applies to all object types and can be re-applied manually after migration. Custom tag mapping (grouping tags into categories) is handled as a value transformation during the migration run.

Real Geeks lead notes transfer as Pipedrive Activity records with type=note. Original note timestamps and owner assignments are preserved. Multiple notes per lead become multiple Activity records linked to the same Person. Rich-text formatting in Real Geeks notes is converted to plain text for Pipedrive compatibility.

Real Geeks tracks lead source (website, Facebook, Zillow, Realtor.com, API, etc.) as a field on the Lead. This transfers as a custom text or pick-list field on the Pipedrive Person. Source is critical for real estate teams attributing inbound lead quality to marketing channels — we preserve it on every record.

Real Geeks API exposes activity events (property searches, IDX views, form submissions, outgoing notifications) as structured events. We map these to Pipedrive Activities by type: property view events become Tasks, scheduled follow-ups become Tasks with due dates, and call activities (if tracked in Real Geeks) become Call activities. Each Activity links to the originating Person record with the original event timestamp preserved.

Real Geeks drip campaigns have no Pipedrive equivalent. We export campaign names, enrollment dates, and completion status as a custom text field on the Person record — not as active Pipedrive sequences. Pipedrive Sequences use a different trigger model (manual or deal-stage triggers) and must be rebuilt from the exported campaign definitions.

Real Geeks internal lead ID is stored as a custom field on the Pipedrive Person for traceability. This ID enables delta-run de-duplication, support lookups, and reconciliation against the Real Geeks source during the cutover window. It is referenced but not displayed to end users.

Pipedrive sets CreatedDate at the time of import. Original Real Geeks create timestamps are preserved as a custom datetime field on the Person so historical reporting (e.g., lead age, time-in-pipeline) is accurate from day one in Pipedrive. This preserves lead aging metrics, campaign response times, and activity recency calculations that depend on the original creation date rather than the import date.