| Purpose | Explain the retirement of the Occupancy (Legacy – Unsupported) report type and how to rebuild a report using the supported Occupancy report type. |
| Best for | Cloudbeds Insights Authors, property owners, system administrators, managers, and reporting or financial teams that previously used legacy occupancy reports. |
| Use this when | You need to understand what happened to a report that used Occupancy (Legacy – Unsupported) or recreate its configuration using the current report type. |
| Requirements | Cloudbeds Insights report-building capabilities and Author permission to create and save the replacement report. |
| Expected result | You can rebuild the required report using the supported Occupancy report type. |
| Limitations | Reports created with Occupancy (Legacy – Unsupported) cannot be converted or repointed to Occupancy. They must be rebuilt. |
Introduction
Cloudbeds retired the Occupancy (Legacy – Unsupported) report type on April 30, 2026. The retirement affected reports that had been manually created in Cloudbeds Insights using that legacy report type.
If you still need the information from a legacy occupancy report, create a new report using the supported Occupancy report type and rebuild the required fields, groupings, filters, and other settings.
Rebuild a legacy occupancy report
Review the old report configuration before creating its replacement. This helps you reproduce the reporting purpose without relying on the retired report type.
- Open the legacy report, if it is still available, and record its columns, group rows, group columns, filters, and formulated fields.
- Go to the Reports area in Cloudbeds Insights and create a new report.
- Select Occupancy as the report type.
- Add the fields, groupings, filters, and other settings needed for the replacement report.
- Save and run the new report. Review the results before using it for operational or financial decisions.
- If the legacy report had an email subscription, create a new subscription for the replacement report and remove any obsolete subscription.
For the complete report-building workflow, see How to create your own reports.
Frequently asked questions
Expand each question below to learn more about the retirement of Occupancy (Legacy – Unsupported) and how it affected reports.
What did Cloudbeds retire?
Cloudbeds retired the report type previously labeled Occupancy (Legacy – Unsupported). The supported report type is labeled Occupancy.
Who was affected?
The retirement affected customers who had created reports using Occupancy (Legacy – Unsupported) and still needed those reports or their results.
It did not affect reports that already used Occupancy.
Can my legacy report be converted to Occupancy?
No. A report created with Occupancy (Legacy – Unsupported) cannot be automatically converted, migrated, or repointed to Occupancy.
The two report types use different data structures and calculation logic. Create a new report and rebuild the configuration using Occupancy.
Which report type should I use?
Select Occupancy when creating the replacement report. Do not use a report type labeled as legacy or unsupported.
Why might the rebuilt report show different results?
Historical values may differ because the supported Occupancy report type uses updated capacity, inventory, and revenue handling.
Review the replacement report before using it as a direct comparison with results previously produced by the legacy report.
Did this affect Cloudbeds Reports or other Cloudbeds PMS areas?
No. The retirement applied only to reports that had been manually created using Occupancy (Legacy – Unsupported). Current Cloudbeds Reports, Cloudbeds PMS screens, and reports that already used Occupancy were not affected.
What should I do with a subscription for a legacy report?
Create a subscription for the rebuilt report. Remove any obsolete subscription associated with the legacy report so recipients do not depend on outdated report delivery.
Related articles
Review these resources for additional instructions on creating, editing, and organizing reports with Cloudbeds Insights:
Comments
Please sign in to leave a comment.