Latest · Leasing tech

Fix Your PMS Integration Order Before You Fix Anything Else

September 2, 2026

Your PMS should be the last system you plug in, not the first.

Almost nobody builds it that way. Someone signs the CRM contract. Someone else signs the ILS feed agreement. A third person picks a chatbot because it demoed well. Every vendor gets pointed straight at the PMS, because that's supposedly where the truth lives. Six months later nobody agrees on unit availability, lead source, or which lease is actually signed.

That's not a data quality problem.

That's integration debt, and you took it on the day you let three vendors write to the same system with no order of operations.

Here's how it actually breaks. Your ILS feed writes availability into the PMS on one schedule. Your CRM pulls from the PMS on a different schedule. Your website pulls from the CRM, or sometimes straight from the ILS, depending on which integration your web vendor actually built versus which one they sold you. Now you've got three clocks that never sync, and every mismatch gets blamed on "bad data" when it's really a timing problem nobody designed for.

The fix isn't a project plan. Project plans are for people with a PMO and a spare quarter. You have neither. What you need is a connection order, and it matters more than people think.

Connect in this sequence.

PMS to CRM, first and only. Nothing else touches the PMS directly until that pipe is solid and you've watched it survive a full leasing cycle, not a week. This is the relationship that decides whether a lead turns into a lease, so it needs to be right before anything else leans on it.

Second: CRM to your website and any lead-routing tool. Not the PMS to your website. Your site should never talk to the PMS directly if you can help it, because then you've got two systems both insisting they're the real source of availability, and they will drift apart like roommates who stopped talking.

Third, and only third: your ILS feeds. Route them through the CRM or one integration layer, not straight into the PMS from five vendors at once. If Zillow, Apartments.com, and your local ILS are all writing availability independently, you've built the exact three-clock mess above, just with five clocks now arguing with each other.

Here's what I wouldn't do: let every vendor's "certified integration" talk you into connecting everyone to everyone. Vendors will swear their integration is plug-and-play because that's the line that closes the deal. It might even be true and still be the wrong architecture for your stack. Two systems can connect just fine and still both be wrong to own the same data. A working connection isn't the same thing as a good decision. It's just a functional one.

One thing to actually do this month: pick your single system of record for unit availability and write it down where your team can see it. Not "the PMS is generally the source of truth." The real answer, on paper, exceptions named. If two systems can both claim to be right about a vacant unit, you'll eventually lease it twice, or lose it from every feed at once. Neither makes for a good Tuesday.

Portfolio size decides how much of this you can get away with. A single 200-unit asset can survive some sloppiness, because a human notices the mismatch fast. A 40-property portfolio can't. Nobody's watching every feed by hand, and the errors compound across markets before anyone catches them. The bigger you scale, the more the connection order matters, not less.

None of this needs new software. It needs someone deciding which system is allowed to talk to which other system, and holding that line even when a vendor says their integration would be so much easier if you just let it write directly to everything.

That request is almost never about your data. It's about their implementation timeline.

Source: