{
  "slug": "yardi-voyager",
  "url": "https://apps.sectorgrowth.com/integrations/yardi-voyager/",
  "name": "Yardi Voyager",
  "vendor": "Yardi Systems",
  "aliases": [
    "Voyager",
    "Yardi",
    "Yardi Voyager Senior Housing",
    "Voyager 7S"
  ],
  "website": "https://www.yardi.com/products/yardi-voyager/",
  "category": {
    "slug": "property-and-senior-living",
    "name": "Property and senior living",
    "url": "https://apps.sectorgrowth.com/categories/property-and-senior-living/"
  },
  "summary": "Yardi Voyager holds the prospect, the resident and the unit behind a licensed SOAP interface nobody sees before they sign for it.",
  "answer": "No. A search of the HubSpot App Marketplace for Yardi returns nothing at all as of September 2026. Voyager speaks SOAP through a licensed interface rather than a public REST API, so every route is a build, and the shape that works puts a lakehouse between the two systems. Expect an enterprise programme rather than a connector, and expect the interface, not HubSpot, to set the limits.",
  "nativeApp": {
    "status": "none",
    "verifiedAt": "2026-09-22"
  },
  "api": {
    "style": "soap",
    "auth": "soap",
    "webhooks": "no",
    "changedSince": "partial",
    "sandbox": "yes"
  },
  "objects": [
    {
      "source": "Prospect",
      "hubspot": "deal",
      "direction": "two_way",
      "key": "Yardi prospect id held in a custom HubSpot property",
      "notes": "Status sets the stage on creation only, so staff movements are never overwritten."
    },
    {
      "source": "Prospect contact",
      "hubspot": "contact",
      "direction": "two_way",
      "key": "Yardi contact id, never the email address",
      "notes": "Families share inboxes, and a returning enquiry can arrive on a new contact id."
    },
    {
      "source": "Resident",
      "hubspot": "contact",
      "direction": "to_hubspot",
      "key": "Yardi contact id, carrying unit, status and move-in date"
    },
    {
      "source": "Property",
      "hubspot": "custom",
      "direction": "to_hubspot",
      "key": "Yardi property code",
      "notes": "A routing table decides which properties sync at all, and it is the first gate."
    },
    {
      "source": "Prospect activity",
      "hubspot": "engagement",
      "direction": "two_way",
      "key": "Activity reference recorded in an append-only ledger",
      "notes": "Yardi accepts activities only on prospects the integration itself created."
    },
    {
      "source": "Move in, move out and transfer",
      "hubspot": "engagement",
      "direction": "to_hubspot",
      "key": "Event id plus the event date"
    }
  ],
  "approaches": [
    {
      "kind": "custom",
      "fit": "recommended",
      "why": "A SOAP interface with no event stream, vendor-scoped write rules and maintenance blackouts needs staged pipelines, watermarks and ledgers. A lakehouse holds the raw XML, the cleaned rows and the sync state in one place that survives a replay."
    },
    {
      "kind": "ipaas",
      "fit": "possible",
      "why": "A platform with a real SOAP connector can carry a narrow one-way feed, such as new enquiries into the portal. It has nowhere to hold the identity ledger that keeps a resident from being created twice."
    },
    {
      "kind": "native",
      "fit": "avoid",
      "why": "Nothing exists to install. The marketplace lists no app named for Yardi, and Voyager publishes no public API for a packaged tool to sit on."
    }
  ],
  "effort": {
    "discoveryHours": [
      20,
      40
    ],
    "buildHours": [
      300,
      450
    ],
    "buildBand": "300 to 450 hours",
    "typicalElapsed": "8 to 14 weeks"
  },
  "pattern": "polling-watermark",
  "faqs": [
    {
      "q": "Is there a Yardi app in the HubSpot App Marketplace?",
      "a": "No. Searching a HubSpot portal's marketplace for Yardi returns no results at all, not even fuzzy matches. Yardi publishes its interface specifications to licensed clients through its Client Central portal rather than on a public developer site, so there is no public API for a packaged connector to build on."
    },
    {
      "q": "How does an integration read data out of Yardi Voyager?",
      "a": "Through a licensed interface, called over SOAP against a web services installation dedicated to that client. Access is granted as part of an interface agreement, and the entity that agreement creates is attached per property, so a property nobody attached returns nothing at all and raises no error."
    },
    {
      "q": "Why can a Yardi integration not key contacts on email?",
      "a": "Because email is not an identity in senior living. A couple shares an address, an adult child appears against several residents, and a person who enquires twice can be opened under a second contact id. Keying every upsert on the Yardi contact id makes the record stable even when every other field about the person changes."
    },
    {
      "q": "Can HubSpot move a Yardi prospect through its funnel?",
      "a": "No. There is no operation in the interface that writes a prospect's status, so nothing on the HubSpot side can advance a prospect in Yardi. Deal stages in HubSpot are therefore set once, on creation, from the prospect status at that moment, and staff movements after that are never overwritten by a later run."
    },
    {
      "q": "What can an integration write back into Yardi?",
      "a": "New enquiries as prospects, edits to contact fields that are proven to store, and activities recording marketing emails and form submissions. Contact writes are read, merge and write, so untouched fields are never blanked. Phone numbers go in as bare digits, because formatted numbers are accepted and silently discarded."
    },
    {
      "q": "Why are some Yardi activities rejected by the interface?",
      "a": "Because activity write-back is scoped to the vendor that created the prospect. An integration can attach activities to leads it created and not to prospects that arrived another way. There is also one initial contact activity per prospect, so later form submissions have to be written under a different category."
    },
    {
      "q": "How fresh is Yardi data once it reaches HubSpot?",
      "a": "Hours, not seconds. There is no event stream, so inbound runs on a schedule measured in hours and outbound on an hourly cycle, with both standing down inside the platform's maintenance window. Anyone who needs a record in the portal within seconds of a change in Voyager is asking the wrong system for it."
    },
    {
      "q": "What does a Yardi Voyager and HubSpot programme take in hours?",
      "a": "Twenty to forty hours of discovery and three hundred to four hundred and fifty hours of build. That covers prospects, contacts, residents, properties, activity history and move events inbound, enquiry and activity write-back outbound, the ledgers that keep both idempotent, and a rehearsal against the test environment before anything touches live."
    }
  ],
  "sections": [
    {
      "depth": 2,
      "text": "Why teams connect Yardi Voyager to HubSpot",
      "anchor": "#why-teams-connect-yardi-voyager-to-hubspot",
      "url": "https://apps.sectorgrowth.com/integrations/yardi-voyager/#why-teams-connect-yardi-voyager-to-hubspot"
    },
    {
      "depth": 2,
      "text": "What syncs",
      "anchor": "#what-syncs",
      "url": "https://apps.sectorgrowth.com/integrations/yardi-voyager/#what-syncs"
    },
    {
      "depth": 2,
      "text": "Architecture",
      "anchor": "#architecture",
      "url": "https://apps.sectorgrowth.com/integrations/yardi-voyager/#architecture"
    },
    {
      "depth": 2,
      "text": "Three ways to connect",
      "anchor": "#three-ways-to-connect",
      "url": "https://apps.sectorgrowth.com/integrations/yardi-voyager/#three-ways-to-connect"
    },
    {
      "depth": 2,
      "text": "What breaks and how we prevent it",
      "anchor": "#what-breaks-and-how-we-prevent-it",
      "url": "https://apps.sectorgrowth.com/integrations/yardi-voyager/#what-breaks-and-how-we-prevent-it"
    },
    {
      "depth": 3,
      "text": "Silent acceptance by the interface",
      "anchor": "#silent-acceptance-by-the-interface",
      "url": "https://apps.sectorgrowth.com/integrations/yardi-voyager/#silent-acceptance-by-the-interface"
    },
    {
      "depth": 3,
      "text": "Record ids that repeat across environments",
      "anchor": "#record-ids-that-repeat-across-environments",
      "url": "https://apps.sectorgrowth.com/integrations/yardi-voyager/#record-ids-that-repeat-across-environments"
    },
    {
      "depth": 3,
      "text": "A renamed stage breaking the mapping",
      "anchor": "#a-renamed-stage-breaking-the-mapping",
      "url": "https://apps.sectorgrowth.com/integrations/yardi-voyager/#a-renamed-stage-breaking-the-mapping"
    },
    {
      "depth": 3,
      "text": "A history pull starving the portal",
      "anchor": "#a-history-pull-starving-the-portal",
      "url": "https://apps.sectorgrowth.com/integrations/yardi-voyager/#a-history-pull-starving-the-portal"
    },
    {
      "depth": 2,
      "text": "Our approach",
      "anchor": "#our-approach",
      "url": "https://apps.sectorgrowth.com/integrations/yardi-voyager/#our-approach"
    }
  ],
  "caseStudies": [
    "https://apps.sectorgrowth.com/case-studies/yardi-voyager-hubspot-microsoft-fabric/"
  ],
  "guides": [
    "https://apps.sectorgrowth.com/guides/choose-a-hubspot-integration-approach/"
  ],
  "builtBySectorGrowth": true,
  "status": "published",
  "verifiedAt": "2026-09-22",
  "updatedAt": "2026-09-25",
  "authors": [
    {
      "name": "Prash",
      "role": "Lead of Technical Integrations and AI Solutions"
    }
  ],
  "sources": [
    {
      "title": "Welcome to Yardi Client Central",
      "url": "https://clientcentral.yardi.com/"
    },
    {
      "title": "CRM API | Timeline events",
      "url": "https://developers.hubspot.com/docs/guides/api/crm/extensions/timeline"
    },
    {
      "title": "CRM API | Contacts",
      "url": "https://developers.hubspot.com/docs/reference/api/crm/objects/contacts"
    },
    {
      "title": "API usage guidelines and limits",
      "url": "https://developers.hubspot.com/docs/developer-tooling/platform/usage-guidelines"
    }
  ]
}