Integration Products | Campaign Creators

Yardi Voyager HubSpot Integration | Campaign Creators

Written by Campaign Creators | Nov 17, 2026, 2:19:01 PM
Integration Assessment
Integration Assessment · Real Estate

Yardi Voyager × HubSpot

How a residential or commercial operator running Yardi Voyager can bring prospects, guest cards, residents, leases, units and commercial tenants into HubSpot, and how HubSpot inquiries can land in Voyager as guest cards for the leasing team.

Standard Interface Partnership ProgramILS and guest card (MITS)Commercial API (OSCRE)Residential and commercialWeb service interfacesLicensed by Yardi
Platform ownerYardi Systems
Integration typeCustom build on Yardi interfaces
Primary directionVoyager → HubSpot, guest cards both ways
FeasibilityBuildable, access licensed by Yardi
API accessGated API
01 — Summary

Does Yardi Voyager integrate with HubSpot?

Yardi Voyager runs the property: units, leases, residents, commercial tenants and the accounting behind them. HubSpot is where an operator markets its communities and spaces, nurtures prospects and reports on the full journey from first inquiry to renewal.

API access
Open APIOpen with conditionsGated API

Documentation and credentials come only through the vendor, under a license, partner agreement or customer login.

Gated API. Yardi licenses each interface type with a Data Exchange Agreement and an annual fee. Interface specifications come with the license.

Based on the vendor's public documentation. Access terms are confirmed with the vendor and the client in discovery.

Voyager exposes guest cards, resident and commercial data through licensed interfaces, so HubSpot can follow every prospect and tenant from inquiry to renewal.

Campaign Creators assessment

Yardi connects Voyager to outside applications through its Standard Interface Partnership Program. The interfaces Yardi lists include an ILS and guest card interface (MITS compliant, with bi-directional web methods), a Commercial API (a web service that exports commercial data), and Master Data, Receivables, Maintenance and Screening APIs. CC builds the HubSpot integration on these web service interfaces. Two things set the pace: each interface is licensed by Yardi under a Data Exchange Agreement, and the field list needs sign-off because Voyager holds resident, financial and screening data. Yardi's own HubSpot integration is for Yardi Kube, its coworking platform, not Voyager.

Scorecard
Data richnessHigh
API accessLicensed by Yardi
Public docsLimited
Build complexityMod–High

Ratings are CC judgments from Yardi's public interface materials. Interface specifications are shared by Yardi with licensed parties, so web methods, field paths and limits are confirmed during discovery.

Strength

Standard, two-way guest card flow

The ILS and guest card interface follows the MITS standard and supports bi-directional web methods. A HubSpot inquiry can become a Voyager guest card, and Voyager leasing activity can come back to HubSpot.

Plan for

Fair housing and screening boundaries

Leasing automation touches fair housing rules. The client's counsel reviews targeting and messaging rules, and screening and credit data stay in Voyager.

Gate

Interface licensing comes first

Yardi licenses each interface type with an annual fee and a Data Exchange Agreement. The licensing route for the client's build is agreed with Yardi before any build starts.

02 — API modules

Which Yardi Voyager APIs does the integration use?

Seven Yardi interfaces or products are relevant to HubSpot. Three carry the integration, one supports it, and three are scope decisions or stay inside Yardi.

Core

ILS and guest card interface

Standard interface · MITS compliant

Prospects and guest cards with their leasing activity. Yardi describes bi-directional web methods, so the flow runs both ways.

  • HubSpot inquiries create Voyager guest cards
  • Tours and leasing events return to HubSpot
  • Marketing source carried for attribution
Core

Master Data API

Standard interface · properties, units, residents

The property, unit and resident records behind each community. Which interface carries resident and lease detail for this client is confirmed with Yardi.

  • Properties and units for HubSpot records
  • Residents with lease start, end and move dates
  • Confirm the exact interface in discovery
Core

Commercial API

Web service · export · OSCRE standard

A web service interface that exports commercial property, unit and tenant data, built on the OSCRE standard with Yardi extensions.

  • Commercial tenants become HubSpot companies
  • Lease expirations drive renewal deals
  • Read-only export into HubSpot
Enrichment

Maintenance API

Standard interface · service requests

Work order and service request status, used to time resident satisfaction surveys and service follow-up in HubSpot.

  • Completed work order triggers a survey
  • Request category and completion date only
  • No repair notes copied into HubSpot
Stays in Yardi

Receivables API

Standard interface · MITS based

Charges, payments and ledgers remain in Voyager. Resident balances are not marketing data.

  • No ledgers or payment data in HubSpot
  • Collections stay in Yardi workflows
  • At most a renewal-eligibility flag, if approved
Scope decision

Screening API

Standard interface · MITS based

Applicant screening, credit and background results stay in Yardi. HubSpot receives only an application stage, never a result or a reason.

  • Off by default
  • Application submitted and lease signed as stages
  • Counsel signs off what HubSpot may hold
Confirm access

Investment Manager

Separate Yardi product · investor portal

For operators that also run Yardi's investment management product, investor contacts could support investor relations email in HubSpot. It is a separate product with its own access.

  • Optional later phase
  • Investor contacts and communication preferences only
  • Performance and distribution data stay in Yardi
03 — Framework

How does the Yardi Voyager HubSpot integration work?

Voyager stays the system of record for properties, units, leases, residents and accounting. HubSpot becomes the system of record for marketing, prospect nurturing and the leasing and renewal pipelines. A CC-built integration layer calls the licensed Yardi web services on a schedule, matches records, applies the data rules and writes to HubSpot in batches.

Yardi Voyager
ILS and guest cardprospects, tours, leasing events
Resident and unit dataresidents, leases, units, properties
Commercial APIcommercial tenants, leases, spaces
Maintenanceservice request status
CC integration layer
Secure intakelicensed interface user, credentials in a vault
Sync modulesone per Yardi interface
Identity resolverYardi codes · email · phone
Data filterdrops screening, ledger, restricted fields
HubSpot writerbatch upserts, error replay
HubSpot
Contactsprospects, residents, tenant contacts
Companiescommercial tenants
Listings and Property objectsunits and communities
Lease (custom object)dates, status, renewal window
Deals, workflows & reportsleasing and renewal pipelines
Yardi Voyager → HubSpot (primary flow)HubSpot → Yardi Voyager (new guest cards from HubSpot inquiries)
Principle

Each record has one owner

Voyager owns units, leases, residents, rents and accounting. HubSpot owns campaigns, early inquiries and pipeline stages until a guest card exists in Voyager.

Principle

Store what the team acts on

HubSpot keeps lease dates, unit details and leasing stages. Ledgers, screening results and documents stay in Voyager.

Principle

Fair housing is part of the build

Targeting, lists and automated messages are reviewed against the client's fair housing policy. Counsel decides; CC builds to that decision.

04 — Process

What does Yardi Voyager HubSpot integration setup involve?

Each phase ends on a gate the client signs off before the next begins. Inbound sync goes live first; guest card write-back follows once matching is trusted.

1

Discovery & licensing

Confirm which Voyager modules the client runs (residential, commercial or both), which teams will use HubSpot, and the licensing route for each Yardi interface in scope.

Gate to next phaseInterfaces in scope licensed, or a dated plan to license them
2

Credentials & test database

Set up the interface user and test database access with Yardi and the client, and complete the client's security review of the integration layer.

Gate to next phaseTest data read from each licensed interface
3

Data rules & fair housing review

Agree match rules, the HubSpot field list and record ownership. The client's counsel reviews lead routing, list criteria and automated messages against its fair housing policy.

Gate to next phaseSigned field list, match rules and counsel review
4

HubSpot data model

Create the Property and Lease custom objects, activate Listings for units, add properties, association labels and the leasing and renewal pipelines in a HubSpot sandbox.

Gate to next phaseSchema approved and created in sandbox
5

Build sync modules

Build guest card, resident, unit and commercial sync modules with matching, data filtering, batch writes and an error replay queue.

Gate to next phaseSandbox sync reconciles to Voyager counts per property
6

Backfill & guest card write-back

Load current residents, active leases, units and open guest cards. Then switch on HubSpot-to-Voyager guest card creation for agreed forms.

Gate to next phaseCounts reconcile to Voyager reports within an agreed tolerance
7

Workflows, parallel run & launch

Build inquiry follow-up, tour reminder, renewal and survey workflows with sends paused, run two weeks in parallel, then switch on.

Gate to next phaseFive consecutive days with no unresolved sync errors
05 — Data mapping

What does the Yardi Voyager HubSpot integration sync?

Field names describe Voyager data in plain terms. Yardi shares interface specifications with licensed parties, so each field path is confirmed during the credentials phase.

Yardi Voyager fieldHubSpot propertyObjectDirectionNotes
Guest cards & prospects · ILS and guest card interface
Prospect IDyv_prospect_idContact↔ BothMatch key. Written back when HubSpot creates the guest card.
First and last namefirstname, lastnameContact↔ BothFill blanks; HubSpot edits stay in HubSpot.
Email, phoneemail, phoneContact↔ BothMatch keys after the prospect ID.
Property of interestAssociation to PropertyContact↔ BothYardi property code on the Property record.
Desired move-in dateyv_desired_move_inContact↔ Both
Desired bedrooms, rent rangeyv_desired_bedrooms, yv_max_rentContact↔ BothPreferences the prospect stated. Confirm field paths in discovery.
Marketing sourceyv_marketing_sourceContact↔ BothHubSpot original source mapped to the Voyager source list.
Leasing events (contact, tour, application)Custom event: Leasing activityContactYV → HSOne timeline event per Voyager event.
Leasing stagedealstageDealYV → HSInquiry, tour, application, lease signed. Stage only, no screening outcome.
Residents & leases
Resident (tenant) codeyv_resident_codeContactYV → HSPrimary key once a prospect becomes a resident. Unique.
Lease start and end datesyv_lease_start, yv_lease_endLeaseYV → HSDrive the renewal window.
Move-in and move-out datesyv_move_in, yv_move_outLeaseYV → HSNotice-to-vacate triggers a retention workflow.
Lease statusyv_lease_statusLeaseYV → HSCurrent, notice, past, future.
UnitAssociation to ListingLeaseYV → HSLease linked to the unit record.
Household membersAssociation label: HouseholdContactYV → HSOnly adults on the lease, confirm in discovery.
Properties & units
Property code and nameyv_property_code, namePropertyYV → HSCommunity or building. Unique code.
Property address and typeaddress fields, yv_property_typePropertyYV → HSResidential or commercial.
Unit codeyv_unit_codeListingYV → HSUnique within the property.
Unit type, bedrooms, square feetlisting propertiesListingYV → HSMapped to HubSpot listing properties.
Unit status and available dateyv_unit_status, yv_available_dateListingYV → HSVacant, notice, occupied.
Market renths_priceListingYV → HSAdvertised rent only.
Commercial tenants & leases · Commercial API
Commercial tenantname, yv_tenant_codeCompanyYV → HSTenant code is the match key.
Tenant contactsemail, firstname, lastnameContactYV → HSAssociated to the tenant company.
Suite / spaceAssociation to ListingLeaseYV → HSSpace leased by the tenant.
Lease expirationyv_lease_endLeaseYV → HSOpens a renewal deal at an agreed lead time.
Leased areayv_leased_areaLeaseYV → HSSquare footage on the lease.
Maintenance · Maintenance API
Work order completedCustom event: Work order completedContactYV → HSTriggers the satisfaction survey.
Request categoryyv_last_request_categoryContactYV → HSCategory only, no notes.
06 — Auth & API

How are authentication and API limits handled?

Access to Voyager is licensed per interface. Values Yardi does not publish are marked for confirmation.

TopicYardi VoyagerHubSpot
Access modelStandard Interface Partnership Program: a Data Exchange Agreement and annual license fee per interface type. Yardi lists two years in business and three mutual Voyager clients for vendor partners. The route for a client-owned build is agreed with Yardi.Self-serve in the client portal. Custom objects need an Enterprise hub; Listings must be activated.
InterfacesWeb service interfaces: ILS and guest card (MITS, bi-directional web methods), Commercial API (export, OSCRE), Master Data, Maintenance, Receivables and Screening APIs.REST APIs: CRM objects, listings, custom objects, associations, custom events.
AuthenticationAn interface user set up in Voyager, with the database and property access Yardi enables for the license. Confirm in discovery.Private app access token or OAuth 2.0 public app, scoped per object.
FreshnessRequest and response web methods. CC polls on a schedule agreed per interface. Push notifications not published; confirm with Yardi.Writes are immediate; batch endpoints handle volume.
Rate limitsNot published. Confirm with Yardi.Per-10-second burst and daily limits by subscription tier.
Test environmentYardi provides a development sandbox to Standard Interface vendors.HubSpot sandbox account for build and testing.
Sensitive dataResident, ledger and screening data. The integration drops screening results, ledgers and identity numbers.Sensitive data properties on Enterprise; field-level permissions by team.
07 — Issues & opportunities

What should you plan for, and what does the integration unlock?

Severity reflects impact on the SOW, not technical difficulty alone.

Challenges to plan for

Interface licensing sets the timelineHigh

Each Yardi interface is licensed separately with an annual fee. Make licensing a client-owned dependency in the SOW, with a date for each interface.

Fair housing reviewHigh

Lead routing, list criteria and automated messages must follow fair housing rules. CC flags each decision; the client's counsel decides. This is not legal advice.

Screening and credit data stay outHigh

HubSpot holds an application stage, never screening results, credit data or decision reasons. The data filter drops these fields before anything reaches HubSpot.

Limited public documentationMedium

Yardi shares interface specifications with licensed parties, not publicly. Budget a discovery spike to confirm web methods, field paths and limits per interface.

Residential and commercial differMedium

Residential leasing centers on people and units; commercial leasing centers on tenant companies and spaces. Each needs its own match rules and pipeline.

Polling, not pushLow

The interfaces are request and response. Schedules are set per interface so HubSpot is current enough for each workflow without exceeding agreed call volumes.

Opportunities in HubSpot

Inquiry to lease in one viewHigh value

Every HubSpot campaign, form and email connects to the Voyager guest card, tour and signed lease, so marketing spend can be judged by leases, not clicks.

Renewals worked earlyHigh value

Lease end dates open renewal deals and resident outreach at an agreed lead time, before notice to vacate.

Commercial lease expirations as pipelineHigh value

Leasing teams see every commercial expiration as a dated renewal deal on the tenant company, with contacts and history attached.

Resident satisfaction after serviceMedium value

A completed work order triggers a short HubSpot survey, and low scores open a ticket for the property team.

Unit availability in marketingMedium value

Available units and dates on HubSpot listing records feed lists and emails for prospects whose stated preferences match.

Portfolio reportingMedium value

Leasing velocity, source performance and renewal rates by property meet in HubSpot dashboards alongside campaign data.

Core journey

From first inquiry to renewal.

The integration follows one person or tenant through the leasing cycle. Each step has one system of record, and HubSpot shows the whole path.

  1. Inquiry: a HubSpot form or campaign creates the contact and a Voyager guest card.
  2. Tour and application: Voyager leasing events update the HubSpot deal stage, with no screening detail.
  3. Lease and move-in: the resident code, unit and lease dates land on HubSpot records.
  4. Renewal: the lease end date opens a renewal deal and resident outreach at an agreed lead time.
08 — Property schema

Which HubSpot properties does the integration create?

All custom properties use the yv_ prefix in a Yardi Voyager property group. Lease and Property are custom objects; units use HubSpot Listings.

Internal nameLabelObjectTypeSource / logic
yv_prospect_idYardi Prospect IDContactSingle-line textGuest card key; unique
yv_resident_codeYardi Resident CodeContactSingle-line textResident (tenant) code; unique
yv_desired_move_inDesired Move-In DateContactDate pickerStated on the guest card
yv_marketing_sourceYardi Marketing SourceContactDropdownVoyager source list, mapped from HubSpot source
yv_property_codeYardi Property CodePropertySingle-line textVoyager property code; unique
yv_unit_codeYardi Unit CodeListingSingle-line textUnit code within the property
yv_unit_statusUnit StatusListingDropdownVacant, notice, occupied
yv_lease_startLease StartLeaseDate pickerFrom lease record
yv_lease_endLease EndLeaseDate pickerFrom lease record; drives renewal
yv_lease_statusLease StatusLeaseDropdownCurrent, notice, past, future
yv_tenant_codeYardi Tenant CodeCompanySingle-line textCommercial tenant key; unique
yv_leased_areaLeased AreaLeaseNumberSquare footage, commercial leases
09 — Scope builder

Interactive scope builder

Choose the interfaces and fields for this engagement and the direction each one syncs. Required fields are the keys each sync module cannot run without. Copy the summary into the SOW or a reply to the client.

Scope summary

0Fields
0Inbound
0Write-back
Yardi Voyager × HubSpot Integration Assessment · Designed by Campaign Creators, Elite HubSpot Solutions Partner

Yardi Voyager HubSpot integration FAQ

Does Yardi Voyager integrate with HubSpot?

Yes, through a custom build on Yardi’s licensed interfaces. Yardi’s own HubSpot integration is for Yardi Kube, its coworking platform, not Voyager, so Campaign Creators builds on the Standard Interface Partnership Program web services, including the MITS-compliant ILS and guest card interface and the Commercial API. Each interface is licensed by Yardi under a Data Exchange Agreement with an annual fee.

What data syncs between Yardi Voyager and HubSpot?

Prospects and guest cards, leasing events and stages, residents with lease and move dates, properties and units, and commercial tenants with lease expirations flow from Voyager into HubSpot contacts, companies, listings and custom Property and Lease objects. HubSpot inquiries create Voyager guest cards, and completed work orders can trigger satisfaction surveys. Ledgers, payments and screening results stay in Voyager.

Which system owns which data?

Each record has one owner. Voyager owns units, leases, residents, rents and accounting. HubSpot owns campaigns, early inquiries and pipeline stages until a guest card exists in Voyager, while screening results, ledgers and documents stay in Voyager.

What does setting up the Yardi Voyager HubSpot integration involve?

Seven phases, each closed by a client sign-off: discovery and licensing, credentials and test database, data rules and a fair housing review by the client’s counsel, HubSpot data model, building the sync modules, backfill and guest card write-back, and workflows with a two-week parallel run before launch. Inbound sync goes live first; guest card write-back follows once matching is trusted.

How long does the integration take and what does it cost?

Timeline and cost depend on the Yardi interfaces, Voyager modules (residential, commercial or both) and fields in scope, and on Yardi’s licensing for each interface. Campaign Creators confirms these in discovery and provides a fixed scope before the build starts.