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.
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.
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.
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.
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.
Leasing automation touches fair housing rules. The client's counsel reviews targeting and messaging rules, and screening and credit data stay in Voyager.
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.
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.
Prospects and guest cards with their leasing activity. Yardi describes bi-directional web methods, so the flow runs both ways.
The property, unit and resident records behind each community. Which interface carries resident and lease detail for this client is confirmed with Yardi.
A web service interface that exports commercial property, unit and tenant data, built on the OSCRE standard with Yardi extensions.
Work order and service request status, used to time resident satisfaction surveys and service follow-up in HubSpot.
Charges, payments and ledgers remain in Voyager. Resident balances are not marketing data.
Applicant screening, credit and background results stay in Yardi. HubSpot receives only an application stage, never a result or a reason.
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.
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.
Voyager owns units, leases, residents, rents and accounting. HubSpot owns campaigns, early inquiries and pipeline stages until a guest card exists in Voyager.
HubSpot keeps lease dates, unit details and leasing stages. Ledgers, screening results and documents stay in Voyager.
Targeting, lists and automated messages are reviewed against the client's fair housing policy. Counsel decides; CC builds to that decision.
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.
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.
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.
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.
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.
Build guest card, resident, unit and commercial sync modules with matching, data filtering, batch writes and an error replay queue.
Load current residents, active leases, units and open guest cards. Then switch on HubSpot-to-Voyager guest card creation for agreed forms.
Build inquiry follow-up, tour reminder, renewal and survey workflows with sends paused, run two weeks in parallel, then switch on.
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 field | HubSpot property | Object | Direction | Notes |
|---|---|---|---|---|
| Guest cards & prospects · ILS and guest card interface | ||||
| Prospect ID | yv_prospect_id | Contact | ↔ Both | Match key. Written back when HubSpot creates the guest card. |
| First and last name | firstname, lastname | Contact | ↔ Both | Fill blanks; HubSpot edits stay in HubSpot. |
| Email, phone | email, phone | Contact | ↔ Both | Match keys after the prospect ID. |
| Property of interest | Association to Property | Contact | ↔ Both | Yardi property code on the Property record. |
| Desired move-in date | yv_desired_move_in | Contact | ↔ Both | |
| Desired bedrooms, rent range | yv_desired_bedrooms, yv_max_rent | Contact | ↔ Both | Preferences the prospect stated. Confirm field paths in discovery. |
| Marketing source | yv_marketing_source | Contact | ↔ Both | HubSpot original source mapped to the Voyager source list. |
| Leasing events (contact, tour, application) | Custom event: Leasing activity | Contact | YV → HS | One timeline event per Voyager event. |
| Leasing stage | dealstage | Deal | YV → HS | Inquiry, tour, application, lease signed. Stage only, no screening outcome. |
| Residents & leases | ||||
| Resident (tenant) code | yv_resident_code | Contact | YV → HS | Primary key once a prospect becomes a resident. Unique. |
| Lease start and end dates | yv_lease_start, yv_lease_end | Lease | YV → HS | Drive the renewal window. |
| Move-in and move-out dates | yv_move_in, yv_move_out | Lease | YV → HS | Notice-to-vacate triggers a retention workflow. |
| Lease status | yv_lease_status | Lease | YV → HS | Current, notice, past, future. |
| Unit | Association to Listing | Lease | YV → HS | Lease linked to the unit record. |
| Household members | Association label: Household | Contact | YV → HS | Only adults on the lease, confirm in discovery. |
| Properties & units | ||||
| Property code and name | yv_property_code, name | Property | YV → HS | Community or building. Unique code. |
| Property address and type | address fields, yv_property_type | Property | YV → HS | Residential or commercial. |
| Unit code | yv_unit_code | Listing | YV → HS | Unique within the property. |
| Unit type, bedrooms, square feet | listing properties | Listing | YV → HS | Mapped to HubSpot listing properties. |
| Unit status and available date | yv_unit_status, yv_available_date | Listing | YV → HS | Vacant, notice, occupied. |
| Market rent | hs_price | Listing | YV → HS | Advertised rent only. |
| Commercial tenants & leases · Commercial API | ||||
| Commercial tenant | name, yv_tenant_code | Company | YV → HS | Tenant code is the match key. |
| Tenant contacts | email, firstname, lastname | Contact | YV → HS | Associated to the tenant company. |
| Suite / space | Association to Listing | Lease | YV → HS | Space leased by the tenant. |
| Lease expiration | yv_lease_end | Lease | YV → HS | Opens a renewal deal at an agreed lead time. |
| Leased area | yv_leased_area | Lease | YV → HS | Square footage on the lease. |
| Maintenance · Maintenance API | ||||
| Work order completed | Custom event: Work order completed | Contact | YV → HS | Triggers the satisfaction survey. |
| Request category | yv_last_request_category | Contact | YV → HS | Category only, no notes. |
Access to Voyager is licensed per interface. Values Yardi does not publish are marked for confirmation.
| Topic | Yardi Voyager | HubSpot |
|---|---|---|
| Access model | Standard 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. |
| Interfaces | Web 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. |
| Authentication | An 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. |
| Freshness | Request 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 limits | Not published. Confirm with Yardi. | Per-10-second burst and daily limits by subscription tier. |
| Test environment | Yardi provides a development sandbox to Standard Interface vendors. | HubSpot sandbox account for build and testing. |
| Sensitive data | Resident, ledger and screening data. The integration drops screening results, ledgers and identity numbers. | Sensitive data properties on Enterprise; field-level permissions by team. |
Severity reflects impact on the SOW, not technical difficulty alone.
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.
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.
HubSpot holds an application stage, never screening results, credit data or decision reasons. The data filter drops these fields before anything reaches HubSpot.
Yardi shares interface specifications with licensed parties, not publicly. Budget a discovery spike to confirm web methods, field paths and limits per interface.
Residential leasing centers on people and units; commercial leasing centers on tenant companies and spaces. Each needs its own match rules and pipeline.
The interfaces are request and response. Schedules are set per interface so HubSpot is current enough for each workflow without exceeding agreed call volumes.
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.
Lease end dates open renewal deals and resident outreach at an agreed lead time, before notice to vacate.
Leasing teams see every commercial expiration as a dated renewal deal on the tenant company, with contacts and history attached.
A completed work order triggers a short HubSpot survey, and low scores open a ticket for the property team.
Available units and dates on HubSpot listing records feed lists and emails for prospects whose stated preferences match.
Leasing velocity, source performance and renewal rates by property meet in HubSpot dashboards alongside campaign data.
The integration follows one person or tenant through the leasing cycle. Each step has one system of record, and HubSpot shows the whole path.
All custom properties use the yv_ prefix in a Yardi Voyager property group. Lease and Property are custom objects; units use HubSpot Listings.
| Internal name | Label | Object | Type | Source / logic |
|---|---|---|---|---|
| yv_prospect_id | Yardi Prospect ID | Contact | Single-line text | Guest card key; unique |
| yv_resident_code | Yardi Resident Code | Contact | Single-line text | Resident (tenant) code; unique |
| yv_desired_move_in | Desired Move-In Date | Contact | Date picker | Stated on the guest card |
| yv_marketing_source | Yardi Marketing Source | Contact | Dropdown | Voyager source list, mapped from HubSpot source |
| yv_property_code | Yardi Property Code | Property | Single-line text | Voyager property code; unique |
| yv_unit_code | Yardi Unit Code | Listing | Single-line text | Unit code within the property |
| yv_unit_status | Unit Status | Listing | Dropdown | Vacant, notice, occupied |
| yv_lease_start | Lease Start | Lease | Date picker | From lease record |
| yv_lease_end | Lease End | Lease | Date picker | From lease record; drives renewal |
| yv_lease_status | Lease Status | Lease | Dropdown | Current, notice, past, future |
| yv_tenant_code | Yardi Tenant Code | Company | Single-line text | Commercial tenant key; unique |
| yv_leased_area | Leased Area | Lease | Number | Square footage, commercial leases |
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.
Based on public documentation. Each item marked for confirmation is verified with Yardi during the credentials phase.
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.
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.
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.
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.
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.