HubSpot for Real Estate: The Listings Object Nobody Advertises

HubSpot has an industry page for real estate. It describes the general platform applied to property work: lead capture from multiple sources, nurturing by buyer stage, reporting from first contact to closed deal, and integrations with Zapier, Slack, Microsoft Teams, Zoom and Google Search Console.

What that page does not mention is the thing a brokerage would most want to know about: HubSpot has a documented object called Listings.

It appears in the import documentation, alongside Appointments, Courses, Services, Products, Orders and Carts, with Name as its required property. It is not a custom property you build, it is an object type with its own records. The marketing page for real estate never names it.

That gap is the useful finding here, and it points at the two decisions a real-estate team actually has to make with HubSpot.

Why Real Estate Breaks A Normal CRM Setup

Three features of property work make the standard contacts-companies-deals shape awkward, and all three are relationship problems rather than feature problems.

One person changes role over time. Today's buyer is next year's seller. In a CRM that treats a contact as a single row with a lifecycle stage, that history either overwrites itself or gets split into two records.

The cycle is long and quiet. Months, sometimes years, between first contact and closing, with long periods of nothing. Pipelines designed for a ninety-day sales cycle report badly on it.

Referrals are the pipeline. The relationship between a past client and a new lead is the most valuable data a brokerage holds, and it is a relationship between two contacts, not between a contact and a company.

HubSpot can model all three. The capability that does it is gated.

The Tier Answer Is Unusually Clear Here

Two capabilities decide this. Both sit at the same place.

Association labels. HubSpot lets you associate records on any tier, including free. What it does not let you do below Professional is label those associations. The documentation states that "A Professional or Enterprise subscription is required to use custom association labels"^[1].

For most businesses that is a nicety. For a brokerage it is the product. It is the whole point. Labelling one contact as Buyer on this deal and Seller on that one, or marking a referrer and the contact they referred as a labelled pair, is how the referral graph becomes queryable rather than anecdotal. Without labels you have associations that say two people are connected and nothing that says how.

Custom reports. They do not exist on Free or Starter. You get 10 dashboards with 50 standard reports each. A brokerage question such as which referral sources produced closings over the last eighteen months is not a standard report.

So for real estate specifically, the usual advice to start cheap and grow is weaker than elsewhere. The capability that makes HubSpot fit the work begins at Professional, which is $90 a seat a month on annual billing with a one-time mandatory onboarding fee of $1,500.

What An Individual Agent Should Do Instead

For one person the picture changes completely.

HubSpot's free tier is a genuinely usable CRM for a solo agent: two users, 15 deal pipelines, 50 automation workflows with restricted triggers and actions, 500 calling minutes, 10 dashboards, one personal meeting link, 3 email templates and the full mobile app, with no time limit.

For an agent managing a personal book of business, that covers contact management, a pipeline per transaction type, scheduling and follow-up automation. The limits that will eventually bite are the two-user ceiling and the HubSpot branding on anything a client sees.

Starter at $7 a seat a month removes the branding and raises email templates to 10,000 and meeting links to a thousand. It does not raise capacity: calling minutes, workflows, pipelines, lead scores and dashboards are all identical to free. For a solo agent whose only complaint is the logo, that is a reasonable $84 a year. For a brokerage expecting more capability, it is a step that does not arrive anywhere.

Setting Up Listings Properly

Since the Listings object is documented but not advertised, here is what the documentation actually says you can do with it.

Listings is importable, with Name as the required column, and it behaves like other objects: records, properties, and associations to contacts, companies and deals. That means a listing can be associated with the seller, with interested buyers, and with the deal it eventually becomes, rather than living as a text field on a deal record.

Three mechanics from the import documentation matter when you load existing listings.

Associate in the same file where you can. Put identifiers for both records in one row. To associate one listing with several interested contacts, repeat the row with a different contact identifier each time.

Include a unique identifier or you will get duplicates. The documentation is explicit that without one, imports create duplicate records instead of associating them. Record ID works for any object.

Line items do not update deal amounts. If you plan to track commission as line items against a deal, importing them will not populate the deal amount. That has to be done by editing the line items or associating them inside HubSpot afterwards, and for a brokerage tracking gross commission income it is the sort of thing you find out in a forecast report rather than in a setup guide.

MLS, Honestly

HubSpot's real-estate page says the platform works with real-estate software, CRM systems and many MLS platforms through native integrations and APIs.

That phrasing is doing real work and it is worth parsing. "Through native integrations and APIs" means the connection exists where someone has built it, either as a marketplace app or through development against the API. It does not mean HubSpot ships MLS connectivity.

The practical consequence for a brokerage: before committing, name your MLS and check for an existing integration by name, rather than relying on the category claim. If it does not exist, the work is a development project, and the API access that implies is a reason to price the tier on API headroom as well as on features.

The Vendor's Case Study, Labelled

The real-estate page leads with one customer: Rever, a brokerage the page describes as online-to-offline, in Vietnam. The claims are specific. That Rever "increased revenue by 600% in ten months with HubSpot Smart CRM"^[2], generated "1,500 additional leads per month"^[3] after implementing the platform, and "increased traffic by 100% in 3 months"^[4].

These are vendor claims about one customer in one market, and we have no measurement of them. We quote them because they are specific enough to be useful in a sales conversation: ask what the baseline was, over what period, and what else changed in the business during those ten months. A 600% revenue increase in a growing brokerage in a growing market is not attributable to a CRM without a lot more detail than a case study carries.

It is also the only customer named on that page, which is itself informative about the depth of the vertical.

The Import Plan For An Existing Book Of Business

Moving a brokerage onto HubSpot is mostly a data exercise, and the documentation is specific enough to plan it properly.

Order matters. Contacts and companies first. Then listings, then deals, then line items and activities. Deals require that their Pipeline and Deal stage values match options that already exist in the account, so build the pipelines before importing anything that references them.

Required columns, per object. Contacts need Email. Companies need Name or Company domain name. Listings need Name. Deals need Deal name, Pipeline and Deal stage. Tasks need Task title and Due date.

File rules. A .csv, .xlsx or .xls file, one sheet only, a header row matching property names, fewer than 1,000 columns, and UTF-8 encoding if any names carry accents. A paid subscription accepts files up to 512 MB and 10 million rows a day; free tools cap at 20 MB and 500,000 rows a day.

Two traps worth naming. Blank cells are ignored, so an import never clears an existing value, which matters when you are cleaning a messy book rather than loading a fresh one. And the Company domain name property accepts values only to the top-level domain, so anything after it is stripped automatically.

Historical activity. If you are importing past calls, meetings and notes, include Activity date. Without it, every historical activity is dated to the moment of the import, which destroys exactly the timeline a long sales cycle needs.

Pipelines For Buyer-Side, Seller-Side And Rentals

Both Free and Starter allow 15 pipelines, which is more than a brokerage needs and more than most set up.

Three is usually the right number. Buyer-side, seller-side, and rentals or property management if you do that work. Separating them matters because the stages genuinely differ, and a single blended pipeline produces a forecast that describes neither.

The stage-naming rule is the one that decides whether the system survives contact with agents. Name stages after observable events rather than intentions. A stage called offer submitted is observable; a stage called warm is not. Over a cycle measured in months, a stage nobody can verify stops being updated within weeks, and every report built on it quietly becomes fiction.

Keep the list short enough that a live transaction moves at least monthly. If a deal can sit in one stage for a quarter, the stage is too wide to forecast with.

What To Automate First

Free and Starter both include 50 workflows, with restricted triggers and actions on Free. Fifty is not the constraint; picking the right first one is.

For a brokerage, the highest-value first automation is usually lead assignment on arrival, because it is verifiable: either the owner field fills in or it does not. The second is a long-cycle follow-up task sequence, since the common failure in property work is not losing leads but forgetting them for five months.

What to leave alone until Professional: anything that depends on labelled associations, since custom association labels require Professional or Enterprise, and anything that depends on a custom report to prove it worked.

Build one. Verify it for a week. Then build the next. An unverified automation in a CRM that agents already distrust is how a brokerage ends up running its real pipeline in a spreadsheet alongside the one it pays for.

What A Brokerage Should Settle Before Buying

Which object holds a property? Confirm that Listings is available on your intended tier and in your account, since it appears in import documentation rather than on the pricing page. Ask explicitly. Ask by name.

Can you label the relationships you care about? Buyer, seller, referrer, co-agent. If yes, you are on Professional or Enterprise. If you are being quoted Starter, the answer is no.

What is the real first-year cost? For a five-agent brokerage on Professional: $5,400 of software plus the $1,500 onboarding fee, so $6,900 in year one and $5,400 in year two.

Does your MLS have a named integration? Not a category claim. A name.

How will commission be recorded? If it is line items against deals, know in advance that the deal amount will not populate itself from an import.

Where This Fits, And Where It Does Not

It fits a brokerage that wants one system for marketing, lead capture, follow-up and transaction tracking, that has a reason to query its referral graph, and that can start at Professional rather than growing into it.

It fits a solo agent well at $0, for contact management and follow-up, with the understanding that the free tier is complete enough to use for a long time and branded enough to notice.

It fits less well where the requirement is deep MLS and transaction-management workflow out of the box. HubSpot's real-estate presence is the general platform plus a documented Listings object plus integrations, not a purpose-built brokerage system, and the honest version of that sentence is the one the vendor's own page avoids making.

And it fits badly where budget flexibility matters more than capability. The published offer is annual, and in the 100 Trustpilot reviews of hubspot.com we read and tagged, 34% concern contracts, auto-renewal or the inability to reduce commitment. A brokerage whose agent count moves with the market should establish the seat-reduction deadline in writing before signing, because that is the one term the price list does not describe.