Migrate from Rezora to Salesforce Sales Cloud

Rezora contacts map directly to Salesforce Contacts. Every Rezora contact requires an AccountId in Salesforce — if the contact has no associated Company in Rezora, we attach to a default 'Unassigned Account' record. Agent-owned contacts preserve OwnerId via email match to Salesforce users.

Rezora contacts marked as unsubscribed or inactive route to Salesforce Lead rather than Contact. The Lead preserves email, name, phone, and company with a custom Rezora_Status__c field indicating the source subscription state. Salesforce Lead Status pick-list is populated from Rezora's contact state.

Rezora Company objects map to Salesforce Account records. Company name maps to Account.Name, domain and website map to Account.Website. If Rezora companies have parent-child relationships (brokerage to franchise office), we map to Account.ParentId for hierarchy preservation. Multi-address company records are flattened to the primary billing address.

Rezora property listings have no Salesforce CRM equivalent — we create a Property__c custom object with fields for listing address, price, status, and agent lookup to the Contact record. The custom object links to the listing agent via a lookup relationship.

Rezora email campaigns map to Salesforce Campaign records. Campaign Name, start date, and end date transfer directly. Campaign Type is set to 'Email' since Rezora campaigns are exclusively email-based. Historical send statistics including opens, clicks, and bounce rates are preserved in Salesforce Campaign statistics fields where supported.

Rezora engagement events such as email opens, link clicks, and unsubscribes translate to Salesforce Task records with Subject indicating event type and Description holding engagement metadata including click URLs. For CRM-level tracking, CampaignMember records capture which Rezora contacts received which campaign emails and their member status.

Rezora drip campaigns and nurture sequences are automation logic with no Salesforce CRM equivalent. We export drip campaign definitions including step order, delay days, email template references, and conditional branching rules as a structured JSON document. Your Salesforce admin or consultant rebuilds using Salesforce Flow with Schedule-Triggered flows and Send Email actions.

Rezora email templates are HTML assets tied to campaign logic. We export template content and embedded images as a ZIP archive. Salesforce Email Templates must be rebuilt manually because text, HTML, and dynamic merge field syntax differ between platforms. Merge field formats ({!Contact.FirstName} vs Rezora's {{first_name}}) require manual conversion.

Rezora agents are user records in the platform. Migration resolves Rezora agent emails against Salesforce User records — matched agents receive OwnerId assignment on their contacts and campaigns. Unmatched agents are flagged in a pre-migration report so you can invite them to Salesforce before migration begins.

Rezora contact groups (static lists) map to Salesforce Campaigns. Dynamic Rezora contact segments based on engagement behavior require custom logic in Salesforce — we preserve the segmentation criteria including filter conditions and behavioral triggers as CampaignDescription text for your admin to implement using Salesforce reports or Flow.

Rezora attachments on contacts or companies are downloaded and re-uploaded to Salesforce Files using the ContentDocument and ContentVersion data model. File size limits apply — Salesforce default allows 25MB per file. Inline images embedded in email templates are extracted and hosted as Salesforce CRM content attachments.

Rezora social media posts have no Salesforce CRM standard object equivalent — we create a Social_Post__c custom object with fields for social platform, post content, publish date and time, reach metrics, and related contact lookup. This preserves social engagement history for reporting continuity across your migration.