Migrate from Rezora to HubSpot

Standard contact fields (name, email, phone, address) map directly to HubSpot's built-in contact properties. Rezora contacts without a primary agent assignment land in HubSpot with no owner until agent resolution completes and your team confirms the fallback owner assignment.

Rezora agents become HubSpot users (owner records) matched by email address. Their agent profile data — name, email, phone, brokerage affiliation — also creates a Contact record so the agent's own profile is searchable in HubSpot alongside regular contacts.

Each Rezora contact's primary agent link resolves to the corresponding HubSpot user by email match. That HubSpot user becomes the contact's owner for sales visibility and territory routing. Secondary agent assignments surface as a custom multi-value contact property or linked note for reference.

Rezora company records (brokerages, property management firms) map directly to HubSpot Companies with name, website, phone, address, and industry all transferring. Parent-child company hierarchies in Rezora translate to HubSpot's parent company association field, with the parent record requiring migration first.

Rezora listings or property records that associate with brokerages become HubSpot Companies with a custom property identifying them as listings, or a custom object (HubSpot Enterprise tier) with a company association field to preserve the brokerage-to-listing relationship.

Rezora drip sequences cannot migrate to HubSpot workflows because they use fundamentally different trigger and action models. We export drip sequence definitions as a structured reference file so your team has a complete rebuild blueprint without manually re-documenting every sequence step.

Rezora stores per-contact engagement data: last_email_opened_date, last_click_date, total_opens, total_clicks. These translate to HubSpot custom number and date properties on the Contact record so historical engagement informs future sales outreach and follow-up prioritization.

The Rezora campaign or source that first generated a contact maps to HubSpot's original source data field plus a custom property recording the specific Rezora campaign name, enabling segmentation and reporting across the full contact history.

Any custom fields on Rezora contacts beyond standard fields migrate as HubSpot custom contact properties with property types preserved: text stays text, number stays number, date stays date, and pick-list values map value-by-value to maintain all custom field logic post-migration.

Files attached to Rezora contacts or companies are downloaded from Rezora and re-uploaded to HubSpot Files, then associated back to the corresponding contact or company record using HubSpot's file association tools. HubSpot's 25MB per-file limit applies during re-upload.

Notes attached to Rezora contacts or companies migrate as HubSpot engagement notes with original timestamps and owner preserved across both platforms. Rich-text formatting is maintained where Rezora supports it, ensuring notes retain their original appearance and readability.

Scheduled social posts and social media calendar data have no HubSpot equivalent at the CRM level and cannot be transferred automatically. These must be rebuilt manually in HubSpot's social publishing tool or maintained in a separate social management platform post-migration.