Yardi Data Connect gives Yardi Voyager users a supported way to move governed Yardi data into Microsoft Power BI, combine multiple Voyager databases and outside sources, and automate data refreshes. It makes the most sense when your reporting problem has outgrown standard reports, not simply because leadership wants better-looking dashboards.
The potential time savings are real. In a Yardi customer example featuring Phipps Houses Services, two employees had been spending six to seven hours per week producing reports before the company moved the work into Data Connect and Power BI. Yardi also says Data Connect includes a starter pack with hundreds of customizable dimensions and measures. The catch is that better access to data does not automatically give you better reporting. You still need clean definitions, security, validation, and ownership.
What is Yardi Data Connect?
Yardi Data Connect is a data integration solution that connects Yardi Voyager with Microsoft Power BI.
Yardi describes it as a secure feed from Voyager into Power BI that can bring together multiple Voyager databases and additional data sources. It works with an organization’s existing Microsoft Azure and Power BI environment.
In practical terms, Data Connect creates a path between the operational data stored in Voyager and the analytical reports people build in Power BI.
Yardi Voyager → Data Connect → Power BI semantic model → dashboards and reports
Other data sources can join the model as well. That last point is one of the biggest reasons to use Data Connect.
If you only need information that already exists in Voyager, start by checking whether existing Yardi Voyager reports already answer the question. Adding Power BI does not automatically make a simple reporting problem better.
How does Yardi Data Connect work with Power BI?
Yardi Data Connect for Power BI separates operational processing from analytical reporting.
Voyager remains the source system. Your general ledger, properties, leases, tenants, vendors, residents, charges, receipts, and other operational records continue to live in the Yardi environment.
Data Connect makes selected data available for analysis through Power BI. Power BI then gives your team a place to define relationships, calculations, Key Performance Indicators (KPIs), filters, security rules, and visualizations around that data.
That sounds straightforward. The difficult part is usually not getting a chart onto the screen. It is deciding what the chart should mean.
The data model matters more than the dashboard
Suppose leadership wants portfolio occupancy. One team calculates occupancy using physical units. Another excludes model units. A third uses economic occupancy.
Power BI can calculate all three. It cannot decide which definition your company should use.
The same problem appears with Net Operating Income (NOI), delinquency, rent growth, renewal rates, budget variance, and dozens of other property management KPIs.
Before building a large BI model, document your KPI definitions before they become dashboard measures.
The problem is often not that the company lacks data. The problem is that different teams interpret the same data differently.
What does a Yardi Data Connect architecture look like?
1. Yardi Voyager
Voyager remains the operational foundation. Users continue posting transactions, managing properties, processing leases, running accounting workflows, and maintaining operational data there.
2. Data Connect
Data Connect provides the governed route between Voyager and Power BI. Yardi says it can aggregate information from multiple Voyager databases and other sources while automating data feeds and refresh schedules.
3. Outside data sources
This is where Data Connect starts to become more interesting than a standard Voyager report. You might need to combine Yardi information with:
- Budget data
- Market data
- Building systems
- CRM information
- Leasing data
- Utility information
- Investment data
- Other operational systems
If several outside applications contribute to the reporting environment, map your Yardi third-party integrations before building the Power BI model. Otherwise, Power BI can become another place where nobody knows which system owns which field.
4. The Power BI semantic model
The semantic model defines how the data fits together. It can contain dimensions such as:
- Property
- Entity
- Date
- General ledger account
- Region
- Property type
- Ownership group
It also contains the business measures used by reports. That model is the part you need to govern carefully.
A dashboard can change without breaking the underlying reporting logic. A poorly designed semantic model creates problems across every dashboard that uses it.
5. Reports and dashboards
Power BI reports sit at the end of the process. Executives may want a portfolio summary. Controllers may want financial detail. Regional managers may want property-level operating metrics. Asset managers may want performance by market, entity, or ownership group.
They can use different reports while relying on the same governed model. That is much stronger than maintaining five Excel workbooks that each calculate NOI differently.
Yardi Data Connect vs. standard Voyager reporting
Data Connect is useful, but it is not the answer to every reporting problem.
|
Reporting Need |
Better Starting Point |
Why |
| Standard financial statement | Voyager report | The report already exists close to the source |
| Standard operational report | Voyager report | Less infrastructure to maintain |
| One specialized Voyager report | YSR or custom report | Keeps a narrow requirement inside Voyager |
| Complex Voyager-only logic | YSR or SQL | Better fit for targeted extraction and calculation |
| Multiple Voyager databases | Data Connect | Supports centralized analysis |
| Voyager plus outside data | Data Connect | Brings several sources into one model |
| Executive Power BI dashboards | Data Connect | Supports reusable models and visualizations |
| Enterprise portfolio analytics | Data Connect | Better fit for governed cross-portfolio BI |
This distinction can save a lot of unnecessary work. A controller who needs one customized owner statement probably does not need a Power BI program.
The better starting point may be building a custom report in Yardi Voyager. The opposite is also true. If six departments export different Voyager reports every month, merge them with outside spreadsheets, and calculate portfolio KPIs separately, another custom report may only treat the symptom. That is when the architecture deserves a harder look.
How to set up Yardi Data Connect for Power BI
A good Yardi Data Connect for Power BI setup should begin before anyone opens Power BI Desktop.
Step 1: Define the business questions
Start with decisions, not visuals. Bad requirement: “We need a Power BI dashboard.” Better requirement: “We need regional managers to compare occupancy, delinquency, NOI, and budget variance across their assigned properties every Monday.”
The second version tells you something about the data, users, refresh frequency, security, and measures.
Step 2: List every source system
Identify every Voyager database and outside source that contributes to the report. Then identify the owner of each important field.
For example: Where does property square footage come from? Where does the regional hierarchy come from? Which source owns approved budgets? Which system determines whether a property is active?
Do not wait until two reports disagree to answer those questions.
Step 3: Define your common keys
Multiple systems need a consistent way to identify the same business entity. A property might be P1004 in Voyager and ATL-04 somewhere else. Power BI will not know they represent the same property unless you provide a mapping.
The same issue applies to properties, entities, general ledger accounts, vendors, regions, ownership groups, and reporting periods. Create those mappings deliberately.
Step 4: Decide where reporting logic belongs
Do not put every calculation into Power BI because Power BI can calculate it. Some logic belongs in Voyager. Some belongs in SQL. Some belongs in the Power BI semantic model.
For complex data extraction and validation requirements, understanding Yardi SQL scripting can help you decide where the transformation should happen. The goal is simple. One important business rule should not have five different implementations.
Step 5: Start with a small model
Do not try to expose every field and every KPI during phase one. Start with a limited set of measures the business already trusts.
For a financial model, that might include revenue, operating expenses, NOI, budget variance, and accounts receivable. For an operating model, you might begin with occupancy, delinquency, leasing, or work orders.
Get those right before adding another 100 measures.
Step 6: Reconcile the numbers
This is the step dashboard projects often rush. Suppose the Power BI dashboard shows NOI of $12.4 million. The trusted Voyager report shows $12.1 million. Do not accept the difference because “Power BI calculates it differently.” Find the difference.
Before rewriting a formula, compare:
- The property list
- The accounting period
- Account mappings
- Entity rollups
- Posted and unposted activity
- Inactive property handling
- Inclusion and exclusion logic
A beautiful dashboard that does not reconcile is still a bad report.
Step 7: Define ownership
Before launch, assign actual owners for failed refreshes, KPI definitions, new measures, security changes, workspace permissions, source mappings, report requests, validation, and documentation.
“IT owns Power BI” is not enough. Who in IT? Who approves a new NOI definition? Who confirms a regional manager’s property list? Who investigates when a dashboard stops tying to Voyager? Answer those questions before users depend on the reports.
How does Yardi Data Connect security work?
Security should be part of the architecture, not something you add before launch. Yardi says Data Connect carries Voyager property-level security into the reporting environment and adds row-level and workspace-level Power BI protections.
Voyager property-level security
Suppose a regional manager can access 25 properties in Voyager. Moving the same information into Power BI should not suddenly give that manager access to the other 175 properties in the portfolio. Your security design needs to preserve those boundaries.
Power BI row-level security
Power BI uses Row-Level Security (RLS) to restrict which rows a user can see. You might map one regional manager to Region A and another to Region B while both use the same report.
One detail matters here. According to Microsoft’s Power BI row-level security guidance, RLS applies to users assigned the Viewer workspace role. Admins, Members, and Contributors have broader model permissions, so RLS does not apply to them in the same way.
That is not a minor configuration detail. You can build perfect RLS rules and still expose more data than intended if you assign users the wrong workspace role.
Do not copy bad Voyager security into Power BI
There is another problem worth challenging. What if the existing Voyager security model is already messy?
If users have accumulated property access over several years, automatically carrying that model into Power BI can reproduce the problem instead of solving it. Review the access model first.
A reporting project is a good time to identify stale access, overly broad roles, and property assignments that nobody can explain.
What are the best Yardi Data Connect reporting use cases?
Executive portfolio dashboards
This is one of the clearest fits. Leadership can view portfolio-level KPIs, then filter by region, property, ownership structure, or asset class without rebuilding the report.
Financial and operational reporting together
Finance and operations often work from separate reports. Data Connect can support a model where financial outcomes sit beside operational drivers.
- NOI and occupancy
- Revenue and leasing
- Delinquency and collections
- Repair spending and work order activity
- Budget variance and operating metrics
That helps people move from “What changed?” to “Why did it change?”
Multiple Voyager databases
Organizations with several Voyager databases can use Data Connect to support a consolidated reporting model. This is especially useful when leadership needs one portfolio view but operational teams still work in separate environments.
Voyager plus external data
This is where Data Connect can become much more valuable than a traditional Voyager report. You can analyze Yardi data alongside information that lives somewhere else. That might include market benchmarks, building data, investment information, or another operating system.
Reporting automation
If employees spend hours every week exporting, merging, formatting, and rebuilding the same report, the process deserves scrutiny. Do not automate a bad report simply because it is repetitive.
First ask whether people still need the report. Then ask whether the calculation is correct. Then automate it.
Advanced analytics
Data Connect can also support more advanced analysis once the basic reporting model works. Once the model is governed and trusted, teams can extend the same Power BI environment into forecasting and other analytical use cases.
We would not start there. If your monthly NOI dashboard still does not reconcile, a predictive model is not your next priority.
Where Yardi Data Connect projects go wrong
Starting with dashboard design
The first workshop should not be about colors and charts. Start with business questions, sources, definitions, and users. Visual design comes later.
Treating Data Connect as a magic reporting layer
Data Connect gives you access to data. It does not resolve unclear accounting logic, inconsistent property structures, bad mappings, or competing KPI definitions. Those problems still belong to your organization.
Pulling too much data
More data can make a BI model worse. Every table, field, relationship, and measure creates something else to understand and maintain. Use the data you need to answer defined questions.
Ignoring validation
A Power BI number should have a path back to a trusted source. For important financial measures, somebody should be able to explain why the number agrees with Voyager. If nobody can do that, the metric is not ready for an executive dashboard.
Forgetting about the people who maintain it
The person who builds the first model may not maintain it forever. Document mappings, KPI definitions, security, source ownership, and change processes. The long-term reporting problem is usually governance, not dashboard creation.
When is Yardi Data Connect more than you need?
Data Connect can be the wrong answer. That is important to say.
If you need one standard report, use the standard report. If you need one custom Voyager report, build the report. If you need a complicated Voyager-only extraction, SQL or Yardi SQL Reports (YSR) may solve the problem with much less infrastructure.
If your organization does not have anyone who will own Power BI after launch, adding Data Connect may create another system that slowly becomes unreliable.
The case for Data Connect gets stronger when you have several of these conditions at once:
- Multiple Voyager databases
- Repeated Excel manipulation
- Several reporting audiences
- External data sources
- Portfolio-level KPIs
- A company-wide Power BI strategy
- Repeated disagreements over reporting logic
- A need for governed access across properties
If you are still trying to determine whether the requirement belongs in Voyager, SQL, YSR, or Power BI, a Yardi consultant should help define that boundary before you license or build more technology.
FAQs
What is Yardi Data Connect?
Yardi Data Connect is a secure integration solution that connects Yardi Voyager data with Microsoft Power BI. It supports reporting across multiple Voyager databases and can incorporate additional data sources. Companies can use it to build centralized Power BI models, dashboards, KPIs, and analytics without relying entirely on recurring manual exports.
Does Yardi Data Connect work with Power BI?
Yes, Yardi Data Connect works specifically with Microsoft Power BI as its business intelligence reporting environment. Yardi says organizations can use their existing Microsoft Azure and Power BI environment, automate Voyager data feeds, and begin with a starter pack containing hundreds of customizable dimensions and measures.
Does Yardi Data Connect replace Yardi Voyager reports?
No, Yardi Data Connect does not replace Yardi Voyager reports. Standard Voyager reports remain the better choice for many accounting and operational questions. Data Connect becomes more useful when the company needs Power BI dashboards, multiple Voyager databases, external sources, reusable portfolio KPIs, or a broader analytical model.
How often does Yardi Data Connect refresh data?
Yardi Data Connect supports automated data feeds and refresh schedules between Voyager and Power BI. Yardi does not publish one universal refresh frequency on its public product page. Your reporting team should choose a refresh pattern that matches the business need instead of assuming every dashboard needs continuously changing data.
Is Yardi Data Connect secure?
Yardi Data Connect uses Voyager property-level security together with Power BI row-level and workspace-level controls. Your implementation still needs careful role design. In Power BI, workspace permissions matter because row-level security applies differently to Viewers than to users with broader editing roles.
Can Yardi Data Connect combine multiple Voyager databases?
Yes, Yardi Data Connect can combine data from multiple Voyager databases into a common Power BI reporting environment. The reporting team still needs consistent definitions for properties, accounts, entities, dates, and KPIs. Combining databases does not automatically resolve differences in how each database was configured.
How much does Yardi Data Connect cost?
Yardi does not publish standard Data Connect pricing on its public product page. A realistic budget should consider the Yardi licensing quote plus the internal or consulting effort required for setup, data modeling, security, validation, dashboard development, documentation, and ongoing Power BI ownership.
Before you build another dashboard, get these seven things right
Data Connect is valuable when it solves a genuine reporting architecture problem. It becomes expensive complexity when a company adopts it before defining the problem.
Before moving forward, make sure you can answer seven questions:
- What business decisions should the dashboards support?
- Which systems own the source data?
- How will properties, entities, accounts, and dates map across sources?
- Who owns each KPI definition?
- Which numbers will you use to validate the model against Voyager?
- Who should see each property or portfolio?
- Who will maintain the model after launch?
If those answers are clear, Data Connect can give your team a much stronger foundation for portfolio reporting. If they are not clear, start there.
ND Consulting works with property management teams on Yardi custom reporting and analytics, including reporting strategy, data validation, SQL, YSR, and Power BI-related reporting requirements.
If you are deciding whether your reporting problem needs Data Connect, a custom Voyager report, SQL, or a smaller fix, contact ND Consulting before adding another reporting layer. The right solution is the one that gives your team trusted numbers with the least unnecessary complexity.
