Migrate from Rezora to Pipedrive

Rezora agents are not a Pipedrive native object. We map each agent to a Pipedrive User (so the agent can log in and own records) plus agent-specific properties (license number, role, brokerage affiliation) stored as custom fields on the agent's own Person record. Email addresses are used for user matching — agents without Pipedrive accounts are flagged before migration so invitations can be sent first.

Rezora contacts map directly to Pipedrive People. Standard fields (name, email, phone, address, job title) migrate 1:1. The contact's affiliated agent ID becomes the Pipedrive OwnerId via email lookup. Rezora's marketing-subscription status maps to a custom field since Pipedrive has no native marketing-contact billing distinction.

Rezora companies (brokerages, real-estate firms) map to Pipedrive Organizations. Fields including company name, domain/website, industry, employee count, and annual revenue migrate directly. Parent-company or franchise hierarchy in Rezora maps to Pipedrive's org parent-field — circular references are flagged before migration.

Rezora allows a contact to be associated with multiple companies (common for agent-to-brokerage relationships). Pipedrive People have a single primary org_id. We migrate the most-recently-modified association as primary and surface additional associations as a custom field (Additional_Organizations__c) for manual cleanup.

If Rezora stores listing or transaction data as a custom object or custom fields on contacts/companies, we migrate it to Pipedrive Deals. Pipedrive's Pipeline + Stage structure handles listing status (Active, Under Contract, Closed) as stage groups. Each unique listing-status value becomes a Pipedrive stage via value mapping.

Rezora listing status values (e.g., Active, Under Contract, Pending, Closed) map to Pipedrive Stages within a Pipeline. Pipedrive allows up to 50 stages per pipeline — Rezora setups with more than 50 unique stage names require consolidation into a single pipeline with logical stage groupings, documented in the migration plan.

Rezora call logs (agent calls to contacts) migrate as Pipedrive Activities with type=call. Original timestamps, duration, and agent-owner are preserved. Calls are linked to the target Person or Deal via Pipedrive's activity person_id and deal_id fields.

Rezora email logs (sent from agent to contact via the platform) migrate as Pipedrive Activities with type=email. Subject line, body content, and timestamp are preserved. Pipedrive stores email content as activity notes; full email thread reconstruction requires the email integration to be reconnected post-migration. This ensures that all communication history is accessible within each contact's timeline for reference.

Rezora meeting records (property showings, client appointments) migrate as Pipedrive Activities with type=meeting. Start time, end time, location, and description are preserved. The meeting is linked to the relevant Person or Deal by matching on contact name and timestamp. Multiple participants from Rezora are captured as additional attendee information in the activity notes for complete historical reference.

Rezora notes on contacts or companies migrate as Pipedrive Activity records with type=note. Rich-text formatting is flattened to plain text. Attachments to notes are downloaded and re-uploaded to Pipedrive Files and linked to the parent record. Original note creation dates are preserved as custom fields to maintain the historical context of when each note was originally captured in Rezora.

Rezora's core feature — drip campaigns, branded email templates, and automated sequences tied to distribution lists — has no Pipedrive equivalent. Pipedrive's Campaigns add-on handles outbound email tracking but not drip automation. We export campaign and sequence definitions as a structured JSON reference document so your Pipedrive admin can rebuild sequences in Pipedrive Automations or a connected tool like Zapier or Make.

Rezora file attachments (property images, listing documents, branded templates) are downloaded and re-uploaded to Pipedrive Files. Files are linked to the parent record (Person, Organization, or Deal) using Pipedrive's file upload API. There is a 32MB per-file limit in Pipedrive — files exceeding this are flagged for manual handling.

Rezora custom fields (property type, listing ID, mortgage status, agent commission tier, etc.) must be pre-created in Pipedrive before migration. Pipedrive generates a random 40-character hash key for each custom field — we capture these keys during field creation and use them in the bulk-load API calls. Rezora field types (text, number, date, picklist) map to Pipedrive's corresponding field types (varchar, numeric, date, enum).