This report crosses NAble backup telemetry (157 devices with recent backup, 19 with active issues) with HubSpot deal data (115 deals, 18 won) to test whether your highest-value clients also have the strongest backup protection. Two data sources, one question: are you leaving your biggest revenue relationships exposed to data loss?
This report crosses NAble backup telemetry (157 devices with recent backup, 19 with active issues) with HubSpot deal data (115 deals, 18 won) to test whether your highest-value clients also have the strongest backup protection. Two data sources, one question: are you leaving your biggest revenue relationships exposed to data loss?
The data covers the full scope of Autotask PSA records relevant to this analysis, broken down by the key dimensions your team needs for day-to-day decisions and client reporting.
Who should use this: NOC teams, service managers, and MSP owners monitoring backup compliance
How often: Daily for operations, weekly for management review, monthly for client reporting
This report crosses NAble backup telemetry (157 devices with recent backup, 19 with active issues) with HubSpot deal data (115 deals, 18 won) to test whether your highest-value clients also have the strongest backup protection. Two data sources, one question: are you leaving your biggest revenue relationships exposed to data loss?
The overall backup success rate of 92.9% sits in a healthy range, but 19 devices with active backup issues represent real exposure. Those 19 devices are not spread evenly. Some companies carry multiple problem devices while others run clean. The question this report answers is whether the companies with the most backup issues also happen to be the ones generating the most revenue.
EVALUATE ROW(
"TotalDeals", [HubSpot - Deals Total],
"WonDeals", [HubSpot - Deals Won],
"BackupSuccessRate", [NAble - Backup Success Rate %],
"DevicesWithBackup", [NAble - Devices with Recent Backup],
"DevicesWithIssues", [NAble - Devices with Backup Issues]
)| Company | Devices Protected | Backup Issues | Success Rate | Status |
|---|---|---|---|---|
| Client Alpha | 26 | 2 | 100% | 2 issues |
| Client Beta | 17 | 3 | 94.4% | 3 issues |
| Client Gamma | 13 | 2 | 100% | 2 issues |
| Client Delta | 13 | 3 | 92.9% | 3 issues |
| Client Epsilon | 11 | 4 | 100% | 4 issues |
| Client Zeta | 9 | 1 | 81.8% | 1 issue |
| Client Eta | 9 | 0 | 81.8% | Clean |
| Client Theta | 9 | 0 | 100% | Clean |
| Client Iota | 8 | 0 | 80.0% | Clean |
| Client Kappa | 8 | 1 | 100% | 1 issue |
Client Epsilon carries the highest issue count at 4 devices with backup problems, despite showing a 100% success rate on the devices that do report. This suggests some devices may have stopped reporting entirely rather than failing visibly. Client Beta and Client Delta each carry 3 issue devices, and both sit below 95% success rate.
Three companies (Client Eta, Client Iota, and Client Zeta) show success rates around 80-82% but zero flagged issues. This gap between low success rate and no flagged issues typically means backup jobs are completing but with warnings or partial failures that do not trigger the issue counter.
The overwhelming majority of HubSpot deals (96 of 115) are not assigned to a specific company in the data model. Of the 18 won deals, 16 sit in the unassigned bucket. Only 2 companies have individually tracked won deals. This data gap is the primary obstacle in building a meaningful risk-weighted backup view.
Without company-level deal assignment, we cannot definitively rank which clients carry the most commercial value. The bridge between HubSpot and Autotask companies needs to be filled before this analysis can produce precise per-client risk scores.
EVALUATE TOPN(15,
SUMMARIZECOLUMNS(
BI_Autotask_Companies[company_name],
"DealsWon", [HubSpot - Deals Won],
"DealsTotal", [HubSpot - Deals Total],
"BackupSuccessRate", [NAble - Backup Success Rate %],
"DevicesWithBackup", [NAble - Devices with Recent Backup],
"DevicesWithIssues", [NAble - Devices with Backup Issues]
),
[HubSpot - Deals Won], DESC
)Companies with won deals AND active backup issues. Currently only identifiable at the aggregate level: 16 won deals sit alongside 3 issue devices in the unassigned pool. Once deal-to-company mapping improves, specific clients will surface here.
Client Lambda and Client Mu each have 1 won deal and no backup issues on record. These are the lowest-risk accounts from a data-loss perspective, though the absence of backup data could mean they are not monitored rather than fully protected.
Client Epsilon (4 issues), Client Beta (3 issues), and Client Delta (3 issues) all carry significant backup problems. Without HubSpot deal data linked to these companies, their commercial risk weight remains unknown. Any one of them could be a top-revenue client.
Client Alpha (26 devices, 100% success), Client Theta (9 devices, 100%), and several others run clean backups. Their commercial importance is unknown because deal data is not mapped, but their technical risk is low.
The risk matrix makes one thing clear: the data gap between HubSpot and the backup monitoring system is the biggest risk factor in this analysis. We know which companies have backup problems. We know which deals have been won. We cannot reliably connect those two facts at the company level for most of the portfolio.
Eight companies account for all 19 backup issue devices. Client Epsilon alone carries 21% of all issues despite having only 11 monitored devices. That is a 36% issue rate per device, far above the portfolio average. Client Beta and Client Delta each have 3 issues spread across larger device bases (17 and 13 devices respectively), which makes their per-device risk lower but their absolute exposure still significant.
88.9% of won deals (16 of 18) sit in the unassigned company bucket. Without mapping HubSpot deals to specific Autotask companies, it is impossible to identify which high-value clients have backup gaps. This is the single biggest blocker for operationalizing a risk-weighted backup view.
Client Epsilon (4 issues), Client Beta (3), and Client Delta (3) carry the highest concentration of backup problems. Any of these could be top-revenue clients. Without the deal mapping, every backup issue device carries unknown commercial risk.
Three companies show backup success rates between 80-82% but zero flagged issues. This pattern usually indicates partial backups or warnings that do not trigger the issue counter. These "silent failures" may be more dangerous than visible issues because nobody is investigating them.
The portfolio-wide backup success rate clears 90%, which puts overall backup health in a good range. 157 of the monitored devices have recent successful backup sessions. The problems are concentrated in specific companies rather than spread across the board.
1. Map HubSpot deals to Autotask companies through Bridge_All_Companies. This is the highest-return action from this report. Right now 88.9% of won deals cannot be attributed to a specific company. Start with any client that has an active deal in HubSpot and look for the matching company in Autotask by name. Each mapping you add makes the risk-weighted backup view more precise.
2. Investigate the 4 issue devices at Client Epsilon immediately. With the highest issue count and highest per-device failure rate (36%), this company represents the most concentrated backup risk in the portfolio. Check whether these devices have stopped reporting entirely or are actively failing. Fix or replace the backup agent on each one.
3. Audit the silent failure companies (80-82% success, zero issues). Client Eta, Client Iota, and Client Zeta all show sub-85% success rates without triggering backup issue alerts. Pull the last_28_days data for each device at these companies. Look for partial backups, timeout warnings, or backup jobs completing with errors that the issue counter does not flag.
4. Build a recurring "Backup Risk by Deal Value" dashboard page. Once the HubSpot-to-Autotask mapping reaches 10+ matched companies, create a Power BI page that plots deal value on one axis and backup issue count on the other. The DAX queries in this report are the foundation. Any company that lands in the top-right quadrant (high value, high issues) gets flagged for immediate remediation.
EVALUATE
TOPN(10,
FILTER(
SUMMARIZECOLUMNS(
BI_Autotask_Companies[company_name],
"DealsWon", [HubSpot - Deals Won],
"BackupIssues", [NAble - Devices with Backup Issues]
),
[DealsWon] > 0 && [BackupIssues] > 0
),
[BackupIssues], DESC
)The NAble Backup Success Rate measures the percentage of backup jobs that completed successfully across all monitored devices. It is calculated from the BI_NAble_Device_Statistic table using the last_28_days field. A 92.9% rate means roughly 93 out of every 100 backup attempts succeeded. The remaining 7% either failed, timed out, or completed with warnings.
HubSpot deals connect to BI_Autotask_Companies through Bridge_All_Companies using proxuma_company_id. When that mapping entry does not exist, the deal appears in the "unassigned" bucket. This is not a data quality issue in HubSpot itself; it means the bridge table has not been populated for those companies yet. Adding bridge entries is a manual mapping task that links company records across systems.
The NAble - Devices with Backup Issues measure counts devices in the BI_NAble_Device_Statistic table that have an active backup problem. This includes devices with failed backup sessions, devices where the backup agent is not responding, or devices where the last successful backup is older than the configured threshold. A device can have a high success rate historically but still show up as "issue" if its most recent session failed.
Start with the 18 won deals in HubSpot. For each one, identify the associated company name in HubSpot and search for a matching entry in BI_Autotask_Companies. When you find a match, create or update the Bridge_All_Companies record with the proxuma_company_id that links both systems. This can be partially automated through fuzzy name matching, but a manual review pass is recommended to catch naming differences between systems.
The success rate and issue count come from different calculations. Success rate looks at the ratio of successful jobs over total attempts in the last 28 days. The issue counter flags devices with specific active problems like failed sessions or agent non-response. A device that completes backups with warnings or partial success may drag the success rate down without triggering an issue flag. These "silent failures" warrant investigation because they represent data at risk without a visible alert.
Yes. The DAX queries in this report are production-ready and can run through the Power BI MCP server on a schedule. Once the HubSpot-to-Autotask company mapping covers 10+ companies with both deal data and backup telemetry, a monthly refresh would track how backup risk shifts relative to commercial value over time.
Connect Proxuma Power BI to your PSA, RMM, and M365 environment, use an MCP-compatible AI to ask questions, and generate custom reports - in minutes, not days.
See more reports Get started