What to check in a property management add-on before the PMS migration

What should an operating team check before a PMS migration?

Check three things before the legacy property management system (PMS) is shut off: whether the acquired manager holds years of its own operating records, whether the owner agreements and tenant-data rules allow any of it to be licensed, and whether a complete export is preserved. If those hold, the company may qualify for an introduction to SourceX.

A PMS cutover is the moment legacy history gets left behind. Old ledgers, work-order threads and leasing correspondence are often archived at best and deleted at worst. McKinsey's 2026 private markets report argues that operational value creation is now likely the primary source of PE returns, which is why integration-year decisions deserve a second look at what the old system actually holds.

Why does the migration window matter for property management add-ons?

The window matters because the people who understand the old system are still in the building and the export is still possible. Six months after cutover, the vendor contract has lapsed and the one coordinator who knew the report builder has left.

A property manager's records are unusually connected. A single maintenance event links a tenant request, a vendor dispatch, an owner approval above a spending threshold, an invoice and a ledger entry. That chain of cause and outcome is what AI developers training task-performing agents look for, and it barely exists on the public web.

Which records in a property manager are firm-owned and which are not?

Sort every record family into one of three buckets before anything else. The manager's own operating records can be candidates; owner and tenant records usually are not.

The manager should read its management agreements for confidentiality and data-ownership clauses. Some owners' contracts say all property records belong to the owner; others reserve operating data to the manager.

The ORBIT screen for property management add-ons

Run these five questions for each acquired manager. A clear no on any of them parks the company.

• Owner rights: do management agreements allow the manager to use or license operating records, or would owner consent be needed?
• Resident exclusions: can tenant-identifying fields be set aside so the licensable remainder is still useful?
• Breadth: are there records beyond the PMS, such as email, shared drives, accounting, maintenance apps and call logs?
• Interval: do the records cover several years, including archived platforms from earlier acquisitions?
• Team: does the company have 50+ full-time employees at peak (contractors excluded) and an authorized sponsor?

The company fit checker gives a preliminary, non-binding version of this screen without contact details, and the who qualifies page sets out the full baseline. Note that headcount is measured per company: a platform's combined staff does not make a small add-on eligible by itself.

When in the integration timeline should you raise it?

Raise it before the cutover date is fixed. After that, the cheapest moment to preserve an export has passed.

If several add-ons are on the same calendar, the guide to buy-and-build sectors shows where licensing tends to fit across them, and the 3PL WMS consolidation screen walks through a parallel system-retirement moment.

How does the introduction work without moving any data?

You make the introduction; you never touch the records.

1. Register as a partner, then send the add-on's CEO your referral link or submit the company through the referral form.
2. SourceX checks the company against the baseline on size, years of history, breadth of systems and rights.
3. The company's own IT lead lists each system, the years it covers and what can be exported. No tenant or owner file leaves the company at this stage.
4. Price and terms are agreed as one all-in figure; nothing binds the company until it signs.
5. Buyers review the inventory. Once a company is deal-ready they typically respond within about two weeks.
6. After signing and the company's authorization, redacted data is delivered and the company is paid.

Partners give basic fit information only and never export, upload or describe confidential records.

What should you say to the add-on's CEO?

Keep it short and free of promises. Raise it as part of integration housekeeping.

How do partner rewards work here?

Partners earn 25% of the eligible platform fees SourceX actually collects from the referred company's licensing deals, capped at $100,000 per referred company. The reward becomes payable only after the buyer pays and SourceX receives its fee; a lead, meeting or signed agreement alone does not trigger payment, and no reward is guaranteed. The reward is a share of SourceX's fee and is never deducted from what the company receives. Check your firm's policies on fees connected to portfolio companies before registering, and read the program terms before you rely on any detail.

When is this the wrong move for a property manager?

Skip or wait when any of these apply:

• Most records are tenant screening, payment or eviction files with no workable exclusion.
• Owner agreements claim all records and owners have not agreed.
• The legacy PMS was already switched off with no export.
• The acquired manager has under the program baseline of 50+ full-time employees at peak (contractors excluded).
• A prior owner already granted an AI-training license over the same records.

For a different kind of client-record boundary, see how the RCM roll-up guide separates client PHI from operating know-how.

Next step

Run one add-on through the ORBIT screen before its cutover date. If it passes, register as a partner and make the introduction, or have the owner apply directly at sourcex.si/apply with your referral link.