Migration Report
Overview
When upgrading to the Forge version of Advanced Portal Reports, all existing configurations - including global, project, global and personal views - are automatically migrated.
The Migration Report provides visibility into the result of this process. It helps administrators confirm whether the migration completed successfully, or identify configurations that require manual attention.
⚙️ What is migrated
The migration includes the following configuration data:
Global configuration
Project configurations
Global views
Personal (user) views
Last saved report layout
Request Type filter behavior
In the previous version, Request Type was always available as a default filter. In the Forge version, it must be explicitly added.
If the Request Type field was not explicitly added to the report’s project configuration, the filter and its previously selected values are not preserved.
If you need the Request Type filter available in the report, enable the Request Type field in the project configuration.
🚀 When migration happens
Migration runs automatically when your site is upgraded to the Forge version of Advanced Portal Reports.
📊 Migration outcomes
Depending on the migration result, administrators will see one of the following views in the Global configuration of Advanced Portal Reports:
✅ Successful migration
Displayed only when all configurations were migrated successfully.
In this case, no additional sections (Global, Project, or Views) are shown.
Migration completed successfully
All Advanced Portal Reports configurations have been updated successfully!
The product is now up to date and ready for use.
How a successful migration looks
This short video shows the Migration Report when all configurations have been migrated successfully and no manual action is required.
🟦 Actions available:
Open the documentation via See what’s new to learn more about the Forge version.
⚠️ Manual Migration Required
Displayed when the automatic migration didn’t complete.
No configuration data is lost - the admin can manually start the migration.
Manual Migration of Configurations Required
Please click Run Migration so Advanced Portal Reports configurations can be updated and work as expected.
Retrying the migration
This video shows how the Migration Report looks when automatic migration did not complete and how to manually trigger the migration again using Run Migration.
🟦 Actions available:
Click Run Migration to attempt migration again.
Open See what’s new for additional information.
🧩 Manual Reconfiguration Needed
Displayed when some configurations failed to migrate, even after retrying.
In this case, the Migration Report shows only the configurations that failed - successfully migrated ones are not displayed.
Manual reconfiguration needed
You need to manually reconfigure Advanced Portal Reports for the projects listed below, including global and custom views.
You can also download the JSON file to review your previously saved configurations.
🟦 Actions available:
Review failed configurations by section.
Expand each project or view to View previous configuration.
Export JSON file to download all configurations that you had in the previous version for reference.
📁 Sections in the Migration Report
If migration failures occurred, the following sections appear.
Only sections that include failed configurations are displayed.
Section | Description |
|---|---|
Global Configuration | Shows the migration status for the app’s global settings. |
Project Configurations | Lists projects with failed migrations and allows you to view previous configurations. |
Global Views | Displays failed migrations for shared (global) views. |
Personal Views | Displays failed migrations for user-created (personal) views. |
📤 Export previous configurations
When migration failures occur, administrators can export all previous configurations as a JSON file for reference.
Export JSON file - Contains all configurations in the previous version of the app.
Use this file as a reference when manually reconfiguring your Advanced Portal Reports setup.
🧠 Additional information
Migration is triggered automatically during the upgrade from Connect to Forge.
Migration results and statuses are stored in Forge storage.
Failures are logged and displayed in the Migration Report UI.
If your Connect app used only the User profile access point, it is automatically changed to Requests access point during migration.