Migrate from Rezora to HighLevel

Rezora contacts map 1:1 to HighLevel contacts. We preserve the original create date as a custom datetime field since HighLevel sets CreatedAt at import time. Email serves as the unique identifier for de-duplication and owner matching. We also retain any custom field values for continuity.

Rezora agents are matched to HighLevel users by email address. If an agent email has no corresponding HighLevel user, we assign records to a fallback owner or flag for user creation before migration. Sub-account assignment requires admin decision on partitioning strategy.

Rezora campaign group memberships migrate as HighLevel tags on the contact record. Each group name becomes a tag. Multi-group membership on a single contact creates multiple tags. Tag names exceeding HighLevel's 40-character limit get truncated with a suffix flag for manual review.

Rezora drip campaigns contain sequence steps, delays, and content templates. These export as a structured reference document. HighLevel workflows must be manually rebuilt using this document — we cannot auto-convert drip logic because HighLevel's trigger-and-action model differs structurally from Rezora's campaign-sequence model.

Rezora email templates carry HTML content and merge fields. HighLevel has no native template library for migrated email content. We export templates as reference notes attached to the contact or as a standalone reference document for manual rebuild in HighLevel's workflow email actions.

Rezora company records (brokerages) map to HighLevel companies. Company-agent relationships are preserved via contact-to-company association in HighLevel. Multiple agents under one brokerage in Rezora become multiple contacts associated with one HighLevel company. We also map the brokerage's primary address and phone number to the company record for completeness.

Real estate listing data in Rezora (property details, addresses, MLS numbers) migrates to a HighLevel custom object named Listings. We map listing fields to custom fields on the custom object and create a lookup relationship to the contact or company record that owns the listing.

Rezora social media posts per campaign and agent have no direct HighLevel equivalent. HighLevel does not natively publish to social channels. We export social post history as a reference document for manual rebuild using a third-party social scheduling tool or HighLevel's webhook integrations.

Email opens, clicks, and engagement events from Rezora's campaign tracking surface as activity records in HighLevel. We migrate engagement counts as custom number fields on the contact and full activity logs as notes for sales context continuity. This preserves historical engagement data.

Rezora lead nurture sequences with time-based delays and content steps export as a structured reference document. HighLevel workflows rebuild these as time-based triggers with corresponding email and task actions. The sequence logic must be manually configured in HighLevel's workflow builder.

Rezora access restrictions per agent and campaign require manual translation to HighLevel's sub-account and role permissions. Teams needing multi-tenant isolation use HighLevel sub-accounts; single-office teams use role-based access within one account. We provide a mapping worksheet that lists each Rezora permission set and its recommended HighLevel equivalent for straightforward review.