Dezrez to HubSpot
Dezrez is a UK estate agency software suite. Its Rezi CRM covers properties, people, groups, viewings, offers and documents.
Dezrez data can move into HubSpot, landing mainly in Sales Hub. 0 of 6 mapped objects move directly; 3 items need manual work and 1 do not move. Plan roughly 3-5 weeks for a small move and 10-16 weeks for a large one.
Migration checklist for Dezrez
Three phases, specific to this system. Tick steps off as you go.
Before
0 of 5 doneDuring
0 of 5 doneAfter
0 of 5 doneWhat will it take?
No price list: cost follows volume, custom objects and how much logic must be rebuilt. Answer four quick questions for a planning range.
The three scenarios
Small migration
<10k contacts/properties
Single branch.
Mid migration
10k-100k
Multiple branches and a custom Property object.
Large migration
100k+
Large document volumes and a continuing integration.
What moves the number
Timeline ranges are planning estimates, not a quote. A partner confirms scope after discovery.
Access, mapping and limits
Start with how data leaves Dezrez: what you need to get in, what lands in HubSpot, and what will not.
REST (Rezi API, Swagger 2.0)
Dezrez-issued API client credentials and the agencyId; requests also use a Rezi-Api-Version header.
Choose your route
How will you move the data?
No native connector was found.
- You need: Dezrez-issued API client credentials and the agencyId; requests also use a Rezi-Api-Version header.
- Permission: To confirm
Native imports often bring over only some data, so check coverage per object in the mapping below.
Export each object, clean it, then import it into HubSpot.
- Rezi REST API (properties, people, groups, events, offers, documents)
- DezrezOne XML / Rezi JSON property feeds used for website imports
Limits: To confirm
Migration and sync tools can move more than a plain import. Confirm which objects each one supports before you choose.
Best when volume is high, custom objects are many or automation is heavy. That is the Large scenario: 10-16 weeks, usually phased.
Talk to a partnerWhere each object lands
In Dezrez
In HubSpot
Hover or tap anything on the left to see where it lands.
| Source object | In HubSpot | Moves | Notes |
|---|---|---|---|
| People (applicants, buyers, sellers, landlords) | Contacts | partial | The API returns name, group memberships, marketing preferences and custom fields. Role-based segmentation needs mapping. |
| Groups (households and companies) | Companies | partial | Groups cover both households and companies, so they need splitting into Companies or Contact associations. |
| Properties | Custom objects | partial | Properties have sales and lettings roles. Properties would typically map to a custom object, which is an analyst suggestion. |
| Offers / sales and lettings roles | Deals | partial | Offers and roles are exposed through the API and would be rebuilt as Deals. |
| Viewings, appointments, notes (timeline events) | Meetings | partial | Property and group timelines can be read through the events endpoint. Notes would go to Notes. |
| Documents (certificates, offer documents, pictures) | Files | manual | Document links are returned and some require authentication, so files must be downloaded separately. |
What to expect
These are out of scope per the analyst note and should stay in the property system.
Document links are stored with an authentication flag and are not fetched in bulk.
Dezrez custom fields and roles have no direct HubSpot equivalent.
Rezi Post mail templates are not portable.
Export the preference fields and set HubSpot marketing contact status and subscription types before any send.
Keep Dezrez IDs as unique properties on every HubSpot record and map role types explicitly.
Keep Dezrez as the listing system of record and sync only the CRM objects.
Data governance and compliance
Decide what is allowed to move before anything is exported. Tick each gate once it is agreed.
How we researched this page
How much to trust each section, and where it comes from.
The Rezi API and its objects are documented publicly, with some detail coming from third-party summaries. I found no HubSpot-specific connector or migration doc. Export paths, limits, certifications and residency are unconfirmed.
Sources
Related migrations
Frequently asked questions
How do I migrate Dezrez to HubSpot?
1. Request API credentials and agencyId from Dezrez, and confirm the Rezi-Api-Version header to use. 2. Pull the Swagger document from api.dezrez.com and list the objects in scope. 3. Decide which system owns listings, syndication and client accounts. 4. Inventory custom fields, tags and marketing preference fields.
What does not move from Dezrez to HubSpot?
MLS, portal syndication feeds and trust/client-money accounting. Plan to rebuild or retire these.
How long does a Dezrez to HubSpot migration take?
Small (<10k contacts/properties): 3-5 weeks. Mid (10k-100k): 6-10 weeks. Large (100k+): 10-16 weeks. These are planning estimates, not a quote.
What access do I need to export from Dezrez?
Dezrez-issued API client credentials and the agencyId; requests also use a Rezi-Api-Version header.
What compliance issues apply when moving Dezrez data?
Check: Identity and AML check documents and Client money data (keep in the accounting system). Agree consent, retention and access rules before exporting.
Moving Dezrez into HubSpot?
A network of 153+ tiered HubSpot partners and 1,800+ accounts of experience. Tell us what you are moving and which hub matters most.
Talk to a partner