Propertybase to HubSpot
Real estate CRM. Salesforce Edition is a managed package inside a Salesforce org, and GO (now Lone Wolf Front Office) is a separate non-Salesforce product with its own API.
Propertybase data can move into HubSpot, landing mainly in Sales Hub. 2 of 6 mapped objects move directly (Contacts / leads / inquiries (buyers, sellers) and Accounts / agencies); 3 items need manual work and 3 do not move. Plan roughly 3-5 weeks for a small move and 10-20 weeks for a large one.
Migration checklist for Propertybase
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
<25k contacts, few listings
CSV import.
Mid migration
25k-150k contacts, listings and deals
Custom object, API-based loads.
Large migration
>150k contacts, multi-office
Phased rollout with integrations.
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 Propertybase: what you need to get in, what lands in HubSpot, and what will not.
Salesforce REST/Bulk API 2.0 (Salesforce Edition); separate API-key API (GO/Front Office)
Salesforce admin or integration user with API access, or a connected app. GO needs an API key.
The 'Weekly Data Export' permission, granted by default only to System Administrators.
Salesforce daily API limits scale with edition and licences. Exact numbers not verified.
Choose your route
How will you move the data?
No native connector was found.
- You need: Salesforce admin or integration user with API access, or a connected app. GO needs an API key.
- Permission: The 'Weekly Data Export' permission, granted by default only to System Administrators.
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.
- Weekly/scheduled CSV data export
- Salesforce Data Loader or CLI queries
- REST API
- Bulk API 2.0 for large jobs
- Change Data Capture
Limits: Salesforce daily API limits scale with edition and licences. Exact numbers not verified.
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-20 weeks, usually phased.
Talk to a partnerWhere each object lands
In Propertybase
In HubSpot
Hover or tap anything on the left to see where it lands.
| Source object | In HubSpot | Moves | Notes |
|---|---|---|---|
| Contacts / leads / inquiries (buyers, sellers) | Contacts | yes | These are Salesforce objects, so they export as CSV or via API. Keep the source ID as a custom property. |
| Accounts / agencies | Companies | yes | Standard Salesforce Account data. Mapping is category-level. |
| Listings / properties | Custom objects | partial | Rebuild as a custom object. MLS-sourced fields are licensed and display-restricted. |
| Offers / transactions / closings | Deals | partial | Deal pipelines and stages need redesign. Commission data may need custom properties. |
| Viewings / showings / activities | Meetings | partial | Tasks and events can be mapped to Meetings and Tasks. Mapping is not vendor-verified. |
| Notes and attachments | Notes | partial | The export can include documents and attachments. Re-attaching them to HubSpot records needs work. |
What to expect
These are licensed feeds and sync tools that stay outside HubSpot.
These are not portable and must be rebuilt as HubSpot workflows.
HubSpot is not a system of record for these, so retain them in a dedicated system.
Propertybase includes its own lead-capture and portal tools.
HubSpot has no native property object.
Salesforce reports do not transfer.
Check MLS rules first and keep MLS data read-only or outside HubSpot.
Store the source ID as a unique property and dedupe on email.
Run in parallel and decide the licence end date after validation.
Line up a System Administrator early.
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.
Export path is backed by Propertybase help pages and integration guides. There are no HubSpot docs for a Propertybase connector, and object mapping rests on category-level knowledge of Salesforce-based CRMs. Propertybase pba__ object names were not verified against vendor docs.
Sources
Related migrations
Frequently asked questions
How do I migrate Propertybase to HubSpot?
1. Confirm whether the firm is on Salesforce Edition or GO/Front Office. 2. Get a System Administrator with the Weekly Data Export permission. 3. Inventory pba__ custom objects and fields, and the record counts for each. 4. List MLS, syndication and trust accounting systems that will stay in place.
What data can move from Propertybase to HubSpot?
These objects move directly: Contacts / leads / inquiries (buyers, sellers) and Accounts / agencies. Check the mapping table for partial and manual items.
What does not move from Propertybase to HubSpot?
MLS feeds and listing syndication to portals, Salesforce automation, flows and package logic and Trust accounting and transaction compliance records. Plan to rebuild or retire these.
How long does a Propertybase to HubSpot migration take?
Small (<25k contacts, few listings): 3-5 weeks. Mid (25k-150k contacts, listings and deals): 6-10 weeks. Large (>150k contacts, multi-office): 10-20 weeks. These are planning estimates, not a quote.
What access do I need to export from Propertybase?
Salesforce admin or integration user with API access, or a connected app. GO needs an API key. The 'Weekly Data Export' permission, granted by default only to System Administrators.
What compliance issues apply when moving Propertybase data?
Check: Financial data in offers, commissions and trust accounting, Government ID or KYC documents in attachments and MLS licensed data. Agree consent, retention and access rules before exporting.
Moving Propertybase 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