This article explains how we'll move your legacy custom reports to the new report builder, and what you need to do and by when.
The new report builder replaces the Classic Builder and legacy custom reports. We'll copy your legacy custom reports into the new report builder. At the end of the transition, we'll remove the Classic Builder and all legacy custom reports.
The transition runs in five phases and rolls out in batches, so not all customers move at the same time. We'll email all Administrators when the transition starts for your account.
What you need to do
Until we remove legacy reports from your account, you can open them to trigger their migration, share them with colleagues, and delete the ones you no longer need. After that, you can no longer do this. We'll email you the date, and the timeline below shows where it falls. To keep access to your reports, do the following as early as you can:
- Delete legacy reports you no longer use. Go to Analytics > Reports, select the reports, and delete them.
- Check that the reports you need have a migrated copy. If a legacy report has no copy yet, open it. The migration follows within 24 hours.
- Share reports with the colleagues who need them, and make sure those colleagues have access to the new report builder.
- Compare each migrated report with its legacy report, starting with the number of rows.
- If you use the Custom Reports API, plan your move to the Report API v2.
The sections below explain each step. Your role decides which steps apply to you.
Plan for each phase
Check your email for the dates that apply to you. We remove legacy reports in Phase 5, so the end of Phase 4 is your deadline for the steps above.
| Phase | What changes |
| 1. Announcement | Nothing changes in your reports yet. We'll announce that your reports and API will be migrated, and that the Classic Builder and legacy reports will be removed. |
| 2. Migration | We'll copy your legacy reports into the new report builder. Both builders will run side by side. |
| 3. Removal of the Classic Builder | You can no longer create legacy reports. You can still view and edit existing legacy reports. |
| 4. View-only | You can no longer edit legacy reports. You can still open and share them. This is the last phase before we remove legacy reports. |
| 5. Full deprecation | We'll remove all legacy reports from the report list. We'll also remove the Custom Reports API v1 endpoint. |
See what applies to your role
The steps are different for Administrators, employees with Classic Builder access, and customers who use the Custom Reports API.
Administrators
Throughout the transition, you should do the following:
- Make sure you get a migrated copy of the legacy reports you need. If you didn't create a report, share it with yourself. If a legacy report has no migrated copy yet, open it. The migration follows within 24 hours.
- Share legacy reports with the colleagues who need them. Only Administrators can share legacy reports.
- Open and share legacy reports that were created by employees who are no longer active, if you still need them. We'll only migrate these reports if they're shared with an active employee or an employee on leave.
- Give colleagues access to the new report builder if they only have Classic Builder access. Existing permissions don't carry over automatically. For steps, see Grant employees permission to create reports.
- Grant access to missing data when someone tells you that a migrated report shows less data than the legacy report.
- Delete legacy reports that nobody uses anymore.
- Tell the colleagues who use reports what to expect. You can use the message below.
- Report other issues to our Support team.
Bulk sharing isn't available yet, so you need to share each report individually.
Inform your colleagues
Use this message to tell your colleagues what to expect. Replace the placeholders in brackets with the dates from your email.
|
Subject: Action needed: our reports are moving to the new report builder Hi all, Personio is replacing the Classic Builder and legacy custom reports with the new report builder. We're copying our reports across, and the old ones will be removed at the end of the transition. What this means for you: You only see a report if you created it or if someone shared it with you. Please check Analytics > Reports for a migrated copy of the reports you use, and compare the number of rows with the old version. If a report you need is missing, or you can't see all the data, tell me by [date] so I can share it or grant access. Some numbers and column names differ between the old and new report builder. You can find the details in the Help Center article "Differences between the Classic Builder and the new report builder". The old reports can only be opened and shared until [date from Personio's email]. Thanks, |
Employees with Classic Builder access
Throughout the transition, you should do the following:
- Check whether the reports you need are in your report list as migrated reports. If a report is missing, ask an Administrator to share the legacy report with you before we remove legacy reports from your account. If the migrated copy already exists, its owner can share it with you.
- If you can't see all the data in a migrated report, ask an Administrator to grant you access to that data.
- Delete legacy reports that you created and no longer use.
- Report other issues to our Support team.
Customers who use the Custom Reports API
- Migrated reports aren't enabled for API access by default. In the Classic Builder, all reports were available through the API. In the new report builder, Administrators switch on API access for each report in the report list.
- Enable the migrated report for API access and update integrations to use the Report API v2 endpoints.
- We'll remove the Custom Reports API v1 endpoint together with the legacy reports on 30 June 2027. For setup steps, see Use the Report API v2.
Keep access to your reports
How access works in the new report builder
In the Classic Builder, everyone with Classic Builder access could open all legacy reports and see all of their data. In the new report builder, access is individual, and this applies to Administrators too. You only see a report if you created it or if someone shared it with you. What you see inside a report also depends on your own role and permissions.
Which reports we'll migrate
Migration creates a copy of the legacy report in the new report builder. The legacy report stays as it is. The migrated report is visible only to the person who created the legacy report and the people it was shared with.
- We'll migrate every legacy report that anyone in your company opened or edited in the last 12 months. Opens through the API count as well.
- You can't see in advance which reports we'll migrate, because there's no "last opened" date. The report list shows the last edited date. Any legacy report edited in the last 12 months will be migrated.
- If you're unsure, open the legacy report. It'll then be migrated within 24 hours. This works until we remove legacy reports from your account.
- We'll only migrate legacy reports created by an employee who's no longer active if they're shared with an active employee or an employee on leave.
- The migrated report will appear next to its legacy report in the report list, so you can compare them.
Edit the legacy report or the migrated report
If you save changes in a legacy report, we'll copy them to the migrated report within 24 hours. This stops as soon as someone edits the migrated report. After that, later edits in the legacy report aren't carried over. To avoid confusion, edit in one version only, ideally the migrated report.
How migrated reports are shared
The new report builder has three sharing levels:
| Level | What the person it is shared with can do |
| View | Read the report. The data shown depends on their own permissions. |
| Edit | Edit the report. |
| Owner's view | See exactly what the owner sees, even data their own role can't access, such as salaries. They can only view and export the report. With permissions for the new report builder, they can also make their own copy. |
Migrated reports will be shared with Owner's view. Recipients see the data the report creator could access in Personio at the point of migration. This includes data that a recipient's own role can't access, such as salaries, so review who a legacy report is shared with before it's migrated. This is the closest match to what people saw in the Classic Builder, but it can be less data.
- The migration includes the report owner and everyone the legacy report was directly shared with.
- The creator of the legacy report owns the migrated report and can edit, share, and delete it.
- To edit a view-only report, ask the owner for edit access.
- To see who a report is shared with, open the report and open the sharing option.
For general steps, see Share a report with other employees.
Check whether you still have access to a report
- Go to Analytics > Reports and look for a migrated copy next to the legacy report. If there's no migrated copy, check whether you created the legacy report or someone shared it with you. If so, open the legacy report. It'll be migrated within 24 hours.
- If you didn't create the report and it wasn't shared with you, ask the report creator or any Administrator to share it with you. Only Administrators can share legacy reports.
Check that migrated reports have all the data
A migrated report is shared with Owner's view. If the creator's general access is limited, the migrated report can show less data than the legacy report, for example fewer employees. Reports can also look different because the new report builder works differently.
- Check Differences between the Classic Builder and the new report builder to see if it explains what you see.
- If employees or data you expect are missing, tell the report owner or an administrator.
- An Administrator can grant access to the missing data.
Understand differences between the new and classic builder
Reports in the new report builder can show different numbers, rows, or column names than the legacy reports they were migrated from. This is expected. The most common example is headcount, which can be lower because the status is checked on the selected date.
For the full list and how to get the result you're used to, see Differences between the Classic Builder and the new report builder.