Esti CRM to HubSpot
EstiCRM is a Polish CRM for real estate agencies and developers. It covers offers, statistics and reports, agent settlements and Excel export.
Esti CRM data can move into HubSpot, landing mainly in Sales Hub. 0 of 6 mapped objects move directly; 3 items need manual work and 2 do not move. Plan roughly 2-4 weeks for a small move and 8-14 weeks for a large one.
Migration checklist for Esti CRM
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
CSV-based.
Mid migration
10k-100k
API plus custom objects.
Large migration
>100k
Multi-office, heavy activity history.
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 Esti CRM: what you need to get in, what lands in HubSpot, and what will not.
REST/JSON (EstiAPI v1.5); the public doc describes property-offer endpoints
API ID and token issued from the Esti CRM account
Choose your route
How will you move the data?
No native connector was found.
- You need: API ID and token issued from the Esti CRM account
- 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.
- Excel export of data (vendor feature list)
- EstiAPI offer lists, including active, exported and archive offers, filterable by update date
- Vendor-run data migration service (inbound to EstiCRM)
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: 8-14 weeks, usually phased.
Talk to a partnerWhere each object lands
In Esti CRM
In HubSpot
Hover or tap anything on the left to see where it lands.
| Source object | In HubSpot | Moves | Notes |
|---|---|---|---|
| Property offers/listings | Custom objects | partial | EstiAPI exposes offers; there is no standard HubSpot equivalent, so a custom object is needed. |
| Clients/contacts | Contacts | manual | Presumably moved via Excel export or a vendor-supplied extract; API coverage is not confirmed. |
| Companies | Companies | manual | Not documented; confirm with the vendor. |
| Deals/transactions | Deals | manual | Not documented; confirm with the vendor. |
| Activities (presentations, viewings) | Meetings | manual | The vendor lists records of presentations and viewing confirmations; the export path is unknown. |
| Users/agents | Contacts | manual | Map to HubSpot owners and users manually. |
What to expect
No documented export; these must be rebuilt in HubSpot.
These are portal integrations, not CRM data.
Public docs only cover offers.
Configuration does not export.
HubSpot has no native property-listing object.
Request a full data dump and audit it against screens before cutover.
Confirm the current API version with the vendor.
Use CSV import or a custom script.
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.
Only a real-estate-focused Polish product (EstiCRM) was found. Vendor pages confirm an API with ID/token and Excel export, but the public API doc covers property offers. Contact, deal and activity export coverage is unconfirmed, and the object mapping is analyst inference.
Sources
Related migrations
Frequently asked questions
How do I migrate Esti CRM to HubSpot?
1. Request the API ID and token, and a full export from EstiCRM support. 2. Inventory entities: clients, offers, transactions, presentations, agent settlements. 3. Check which entities the Excel export covers, especially notes and activities. 4. Define custom objects for property offers.
What does not move from Esti CRM to HubSpot?
Automations, permissions and reports and Portal publication links (Otodom etc.). Plan to rebuild or retire these.
How long does a Esti CRM to HubSpot migration take?
Small (<10k): 2-4 weeks. Mid (10k-100k): 4-8 weeks. Large (>100k): 8-14 weeks. These are planning estimates, not a quote.
What access do I need to export from Esti CRM?
API ID and token issued from the Esti CRM account
What compliance issues apply when moving Esti CRM data?
Check: Financial transaction and settlement data and Possible ID and property-ownership data. Agree consent, retention and access rules before exporting.
Moving Esti CRM 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