How REITs do cross-portfolio reporting when properties use different PMS systems
Yardi in Boston, Realpage in Phoenix, Entrata in Denver, and one board deck that has to agree with itself. Here is how the portfolio becomes one dataset, with every number traced to the system it came from.
Connect lands Yardi, Realpage, Entrata, AppFolio and 126+ other proptech systems in a warehouse you own, each in its own shape. Data Map then makes them one portfolio, with the same property, unit and resident recognised across every PMS and one definition of every metric. Every report downstream reads the same dataset, and every figure names the system it came from.
For REITs and large operators the problem is not that each PMS lacks reporting. Each PMS reports in its own schema, so a unit in Yardi is a different shape from a unit in Realpage, and occupancy means three different things on three dashboards. Combining the exports by hand produces errors, and wiring a BI tool to each PMS produces a maintenance burden. One warehouse and one definition per metric, and the board deck reads from the same dataset as the asset manager's dashboard.
One definition
Three systems. One number.
Each PMS carries its own reading of occupancy. Once the three land in your warehouse, Data Map holds the one definition your business signed off, and every report, dashboard and answer uses it.
- Boston · PMS Occupancy leased units ÷ total units
- Phoenix · PMS Occupancy occupied units ÷ rentable units
- Denver · PMS Occupancy physical, excluding down units
- Board deck reads the warehouse DefinitionSource
- BI dashboard reads the warehouse DefinitionSource
- Answer in Claude or Copilot through Propexo MCP DefinitionSource
Three approaches to cross-portfolio REIT reporting
Each approach has real tradeoffs. Here is the breakdown.
Manual aggregation
- What it is
- CSV exports from each PMS, combined in Excel or Google Sheets by analysts
- Ongoing maintenance
- High. Analyst hours every reporting cycle
- Data freshness
- Monthly or quarterly at best
- One schema across PMS platforms
- Manual and error-prone, no single schema
- Who can ask a question
- Whoever has the spreadsheet open
- Cost profile
- Low upfront, high ongoing labor
BI tool with direct connectors
- What it is
- Tableau or Power BI connected to each PMS API or database directly
- Ongoing maintenance
- Medium. Connector upkeep, auth refreshes, schema drift
- Data freshness
- Varies by connector, often delayed
- One schema across PMS platforms
- Partial, connector by connector, no unified schema across PMS
- Who can ask a question
- Whoever has a BI seat
- Cost profile
- Mid-range, engineering time ongoing
The Propexo Platform
- What it is
- Connect lands every PMS in one warehouse you own. Data Map gives the portfolio one set of records and one definition per metric. Your BI tool reads one dataset.
- Ongoing maintenance
- Low. Propexo keeps the connectors running when a vendor changes its API
- Data freshness
- Synced on a configurable schedule per source, with no export to run
- One schema across PMS platforms
- Data Map links the same property, unit and resident across every PMS and holds one definition of every metric
- Who can ask a question
- Anyone you approve, in Claude, Copilot or your BI tool, with the definition and the source on the answer
- Cost profile
- Subscription. No connector upkeep on your side
Ask
What can the board ask once every PMS agrees?
Portfolio occupancy by the definition the business signed off, with the system each property's figure came from. Delinquency across three PMS platforms in one table, and turn cost by market against budget. Questions that used to wait on an analyst's export become ordinary queries against one dataset.
Through Propexo MCP the same questions can be asked in plain language in the AI tool the asset manager already has open, and the answer carries its definition and its source, so a figure that reaches an investor can be traced back to the record it came from. The question set is the one you approve, and the connection is read-only.
Where the answer calls for action, an agent runs the job across every PMS from the same records. A lease audit or a delinquency follow-up applies the same policy at a Yardi property and an Entrata property, and you decide which actions run on their own and which wait for a signature. See Agents for how an agent runs.
How it gets done
How to set up cross-portfolio reporting with the Propexo Platform
Five steps, with the reconciliation that used to be your data team's job done by Data Map.
-
Identify every PMS in the portfolio
Map which properties run Yardi, Realpage, Entrata or another system. The number of platforms sets how much reconciliation Data Map has to do, and how many conflicting definitions of occupancy the business has been living with.
-
Choose a warehouse destination
Pick Snowflake, BigQuery, Databricks or another destination in the catalog, in an account you own. If you do not want to run one, Propexo can run a managed Snowflake warehouse for you, for an added fee, still in your name.
-
Land each PMS with Connect
Connect provides pre-built connectors for Yardi, Realpage, Entrata, AppFolio and 126+ other proptech systems. Each connector handles authentication, pagination, rate limits and a vendor's API change, and each system lands in its own shape, so a figure can always be traced back to the record it came from.
-
Make it one portfolio with Data Map
Data Map recognises the same property, unit, lease and resident across every PMS and links the records, with a confidence score on every link and the sources left as they were. Then it holds one definition of every metric, so occupancy, delinquency and days to turn mean the same thing in every report.
-
Point your BI tool, and your AI tools, at one dataset
Tableau, Power BI, Looker or Sigma reads one dataset that spans every property and every PMS. Through Propexo MCP, the questions you approve can be asked in Claude or Copilot as well, and each answer carries its definition and its source.
Why generic ELT doesn't solve this
Fivetran, Airbyte and Stitch are built for mainstream SaaS such as Salesforce, Workday and HubSpot. They do not have native connectors for Yardi, Realpage or Entrata. Building custom connectors on those platforms means learning each PMS API's non-standard auth flows, proprietary pagination and schema drift patterns, and most data teams that attempt it end up spending more time maintaining connectors than answering portfolio questions.
Connect lands Yardi, Realpage, Entrata, AppFolio and 126+ other proptech systems in a warehouse you own, each in its own shape. Data Map then makes them one portfolio, with the same property, unit and resident recognised across every PMS and one definition of every metric. Every report downstream reads the same dataset, and every figure names the system it came from.
Frequently asked questions
How do REITs do cross-portfolio reporting when properties use different PMS systems?
Land every PMS in one warehouse with Connect, let Data Map link the same property, unit and resident across them and hold one definition of every metric, and point the BI tool at that one dataset. There are no direct PMS integrations to maintain, and the whole portfolio reads from one consistent dataset.
Can REITs use Fivetran or Airbyte to connect Yardi and Realpage to a warehouse?
Fivetran and Airbyte do not have native connectors for Yardi, Realpage or Entrata. Building custom connectors on those platforms takes engineering time up front and ongoing maintenance after. Connect provides these connectors pre-built and keeps them running when a vendor changes its API.
What data does Propexo sync from Yardi, Realpage and Entrata?
Operational data such as units, leases, residents, charges, work orders, leasing activity and payments, depending on what each PMS exposes through its API. Each source lands in its native structure. Data Map then links the matching records across sources and holds the governed definitions, so the portfolio can be queried as one.
Do we still have to model the schema ourselves?
No. Reconciling a unit in Yardi with a unit in Realpage, and agreeing what occupancy means, is what Data Map does. Your team signs off the definitions, and the matching rules for property data are already built. If you would rather model in dbt on the raw tables, they are in your warehouse too.
Can an agent act on what the report finds?
Yes. An agent runs one job across every PMS from the same records. A lease audit, a move-out reconciliation or a delinquency follow-up applies the same policy at a Yardi property and an Entrata property, and you decide which actions run on their own and which wait for a signature.
Which data warehouses does Propexo support?
Snowflake, BigQuery, Databricks and the other destinations in the catalog, in an account you own. Propexo can also run a managed Snowflake warehouse for you, for an added fee, in your name.