Migrate your Real Geeks data

The primary object in Real Geeks. We export all standard fields (first_name, last_name, email, phone, address, created timestamp, status, urgency, timeframe, notes, tags) via CSV export or the Leads API. Custom lead detail fields are mapped as custom properties in the destination.

Names, email, phone, and address are standard fields in Real Geeks and map 1:1 to most destination CRMs. At least one identifier is required per lead; we validate this before import and flag records missing all contact information.

Real Geeks uses system statuses (Active, Cancelled, In Escrow, Closed Escrow, Dead) and allows custom statuses. We map each status to the closest equivalent in the destination CRM and document custom values during scoping so nothing is silently dropped.

Urgency (Cold, Warm, Hot, Contacted, Not Contacted) and timeframe (Immediately through 1 Year Or More) are dropdown fields with optional custom values. We map system values to destination picklist options and flag any custom values that need new picklist items created.

Activity data — every property a lead viewed and every search criteria they saved — is available via the Real Geeks Activities API but is NOT included in the native CSV export. We pull this via API when the customer requests a full behavioral history, but it requires a separate endpoint call per lead and may be throttled on large datasets.

Real Geeks tracks how many saved searches each lead has performed. We export this as a numeric field and as associated search criteria records where available. Not all destination CRMs have a native saved-search concept; in those cases, we store criteria as a custom text field per lead.

Lead sources (website, Zillow, Realtor.com, Incoming Leads API, etc.) are recorded as a standard field. We preserve this as an attribution or origin field in the destination CRM to maintain reporting continuity.

Drip campaign logic — the rules, timing, and content of automated follow-up sequences — lives inside Real Geeks and is not exportable. We export which campaigns a lead is enrolled in as a tag or list membership, but the automation rules themselves must be rebuilt in the target platform.

Tags are a list-of-strings field on leads. We map tags directly as tags or labels in the destination CRM. Custom tag sets are preserved as-is; no transformation is required.

Users (agents) are exportable via the Admin settings. We map assigned agents to owner fields in the destination. Permissions, role hierarchies, and account-level settings do not transfer and must be reconfigured manually.

Real Geeks allows custom fields beyond the standard set. During scoping we retrieve the full field schema from the Real Geeks account and map each custom field to either a matching destination field or a new custom field we create during import.

Real Geeks does not expose attachments or documents via its public API or CSV export. Any files stored within lead records (images, contracts, forms) must be exported manually by the customer or will not transfer.