Migrate from Rezora to Freshsales

Rezora contacts without a deal association route to Freshsales Contacts with their full engagement history. Rezora contacts linked to a campaign that represents an active opportunity split into Freshsales Leads by lifecycle stage: Subscriber and Lead stages map to Freshsales Lead; MQL, SQL, Customer, and Evangelist stages route to Freshsales Contact.

Rezora companies map 1:1 to Freshsales Accounts. The company name maps to Account Name, domain maps to Website, industry maps to Industry pick-list (value-by-value), and employee count maps to Number of Employees. Rezora parent-child company hierarchies preserve using Freshsales Parent Account lookup.

Rezora campaigns have no Freshsales equivalent — a campaign is a multi-agent marketing container, not a CRM object. We migrate campaign membership as Freshsales Tags on the Contact record and surface the campaign name as a reference field. Active drip sequences from the campaign map to Freshsales Sales Sequences (Pro plan) as a rebuild reference document.

Each Rezora campaign-member record — tracking whether a contact received, opened, or clicked a campaign email — migrates as a Freshsales Sales Activity of type Email. The original campaign name and send timestamp are stored in the activity description so engagement history is preserved for reporting continuity.

Rezora property listings with price, status, and address translate to Freshsales Accounts enhanced with custom fields for listing price (Number), property status (pick-list: Active, Under Contract, Sold, Off-Market), and listing type (pick-list: Residential, Commercial, Land, Lease). If the brokerage manages active deals per property, each listing also generates a Freshsales Deal.

Rezora agents resolve to Freshsales users by email match. Granular material-access permissions in Rezora (which campaigns an agent can access) cannot translate to Freshsales — we flag this as a post-migration configuration item for your admin to address via Freshsales profile and sharing rules.

Rezora email templates store HTML content with merge fields tied to contact and property objects. Freshsales has an email template editor but the merge-field syntax differs. We export Rezora templates as HTML blobs with field annotations so your admin can recreate them in Freshsales using the {{contact.first_name}} and {{account.name}} syntax.

Rezora documents attached to contacts or campaigns re-upload to Freshsales Files. The original file name and upload date are preserved as metadata. Freshsales file storage limits per plan (2–100GB per user) should be verified before migration if your instance has large media assets.

Rezora drip sequences and automated workflows have no Freshsales equivalent that preserves the original multi-step logic. We export the Rezora workflow definition (step triggers, delays, branch conditions, and email IDs) as a JSON reference document. Your Freshsales admin uses this to rebuild using Freshsales Workflows (basic, all plans) or Sales Sequences (Pro plan).

Rezora agent groups (used to restrict which agents see which campaigns and contacts) map to Freshsales Sales Teams. A Sales Team groups multiple users under a shared territory or brand. Rezora's material-level restrictions require post-migration configuration via Freshsales profile sharing rules.

If Rezora stores a separate lead record type for early-stage prospects not yet in a campaign, those map directly to Freshsales Leads. The Rezora lead score maps to Freshsales Lead Score (custom Number field) or Freddy AI scoring if your plan includes it.

Rezora engagement events (email open, click, listing view, form submission) map to Freshsales Sales Activities of type Custom. Each activity records the contact, timestamp, and engagement type as the subject line, giving your team a complete activity timeline on the Freshsales Contact record.