What happens to your ProjectData reports in Planner Premium?
They have to be rebuilt, and Planner Premium data is still reportable. Both of those are true, and hearing only one of them is how this becomes a surprise later.
A data source is not a report. Dataverse holds the data and Power BI can reach it. What does not survive is the schema every existing report was written against.
What still works
The reassuring half is real, and worth stating before the rest:
- The data itself, which lives in Microsoft Dataverse rather than disappearing
- Power BI, through the Dataverse connector rather than the Planner one
- The Dataverse Web API, a RESTful OData v4 endpoint, for custom integrations
- Power BI templates for Project for the web, published on GitHub, as a starting point
Nobody is losing their data. If your reporting is one dashboard somebody rebuilds in an afternoon, this is a non-event.
What has to be rebuilt
The word doing the work is rebuilt rather than migrated, and three separate things make it that rather than a repoint.
The schema is different, so nothing repoints
Reports were written against the ProjectData schema. Planner Premium exposes Dataverse tables with different names, shapes and relationships, so every report is authored again rather than pointed somewhere new. Microsoft states plainly that integrations relying on the ProjectData schema do not automatically translate.
There is no content pack
Planner Premium has no built-in Power BI content pack to stand a dashboard up quickly. A Microsoft moderator puts it directly: you configure the connection and apply templates manually. That is a project with a person assigned to it, not a setting.
Custom fields are not queryable
This is the one that surprises people. Custom fields are held as binary blobs inside the msdyn_project and msdyn_projecttask tables rather than as individual columns, so they cannot be queried as fields. The attributes a PMO added specifically in order to report on them are the attributes a report cannot reach.
Microsoft Graph is not a way around any of this. Its standard Planner endpoints do not expose premium data, so an integration written against Graph cannot see dependencies, resources, dates or custom fields. The supported route is the Dataverse Web API, which is itself OData v4, so you are leaving one OData feed for another with a completely different schema behind it.
The Dataverse connector, the absent content pack, the Graph limitation and the binary-blob custom fields are all from answers by Microsoft staff moderators on Microsoft Q&A, checked 25 August 2026. Microsoft ships Planner monthly, so check the current position before you plan around it.
Power BI on Onplana
Onplana serves a read-only OData feed that Power BI reads directly. It uses the ProjectData entity sets (Projects, Tasks, Assignments, Resources, TimesheetLines, TaskBaselines) and their column names, so a ProjectData dashboard is re-pointed at Onplana rather than rebuilt. In Power BI choose Get Data, then OData feed, and sign in with a reporting token. It is on every plan, including Free.
Two things still need work. A column Onplana has no equivalent for is absent, so a visual built on it needs changing. Custom fields come as rows in a separate CustomFieldValues set rather than as columns on Projects and Tasks, so a report that reads them needs one more step.
Ask the same of every vendor you evaluate: is it a live feed, or a scheduled export? Ask to see a dashboard refresh against their system before you believe it. How to connect Power BI.
What you get instead
Cross-project reporting is built in on every plan including Free, with CSV and Excel export, so the common case does not need a BI tool standing behind it at all. There is an OpenAPI-documented REST API if you want to build something of your own against a stable published schema.
The part that matters most for reporting is upstream of any of it: a custom field can be defined once for the whole organisation, so the same field with the same options exists on every project. That is what makes an attribute countable across a portfolio, and it is the thing per-plan fields cannot give you no matter what you connect to them.
Common questions
What happens to my existing ProjectData Power BI reports in Planner Premium?
They have to be rebuilt. Planner Premium data is still reportable, which is the part people are usually reassured by, but it lives in Dataverse under a different schema from the ProjectData feed your reports were written against. Rebuild is the accurate word rather than migrate or repoint.
Can Power BI connect to Planner Premium at all?
Yes, through the Microsoft Dataverse connector rather than the Planner connector. A Microsoft moderator confirmed it works but works differently: there is no built-in content pack, so you configure the connection and apply templates yourself. Power BI templates for Project for the web are published on GitHub and are a reasonable starting point.
Can I use Microsoft Graph instead?
Not for premium data. A Microsoft staff answer states that the standard Planner endpoints in Graph, /planner/plans and /planner/tasks, do not support accessing Planner Premium data, so dependencies, resource assignments, dates and custom fields are not reachable that way. The supported route is the Dataverse Web API, which is itself an OData v4 endpoint.
Can I report on my custom fields?
Not as fields. Microsoft Q&A describes them as binary blobs inside the msdyn_project and msdyn_projecttask tables rather than individual queryable columns. If your reporting depends on custom attributes, and for most PMOs that is the whole point of having them, test this specific thing early rather than discovering it after the cutover.
How much work is rebuilding the reports?
We are not going to give you a number, because it depends entirely on how many reports you have and how deep they go, and any figure quoted by a vendor who has not seen your estate is invented. What we would say is to count them before you plan the migration rather than after. The report inventory is the item most often discovered late, and it is rarely the smallest one.
What does Onplana do here?
Cross-project reporting is built in on every plan, including Free, with CSV and Excel export, and there is an OpenAPI-documented REST API if you want to build something yourself. Custom fields can be defined once for the whole organisation, which is what makes them countable across a portfolio rather than per-plan values that never reconcile.
Does Onplana work with Power BI?
Yes. Onplana serves a read-only OData feed on every plan, including Free, with the ProjectData entity sets and column names, so a ProjectData dashboard is re-pointed rather than rebuilt: Get Data, then OData feed, with a reporting token. A column Onplana has no equivalent for is absent, and custom fields come as rows in a separate CustomFieldValues set rather than as columns, so reports that use either need some changes.