Ask your team which part of the application they’d miss most if it changed, and someone will name a report.
Custom reports in hosted Windows applications depend on more than the application itself, because they use templates, data connections, fonts, printers, and export folders, and any of those can change in a move. This guide shows how to carry your report requirements into a managed hosting move and check that staff can still produce the outputs they need. It assumes no report will work until you test it.
Step 1: List the Reports That Matter
List the essential reports staff run, who runs each one, how many times a month, and the decision it supports, such as a job cost summary for pricing or an aging report for collections. Rank them, because you can’t test everything at once. If a report supports no decision, ask whether it belongs in the move at all. Reports that run overnight without a person are covered in our guide to overnight jobs.
Step 2: Map Templates, Connections, Fonts, and Export Locations
For each essential report, write down four things, starting with where its report templates live.
- Report templates. Note where each one lives: inside the application, in a shared folder, or on one person’s PC, so a template on a local drive won’t follow the application.
- Data connections. Note how the report reaches its data, whether through the database, an ODBC connection, or a spreadsheet, and which reporting add on or runtime it needs.
- Fonts. Identify where the report renders and which fonts its engine requires. Test the hosted view, exported files, and printed output on the devices staff use. Microsoft’s guidance for SSRS reports shows why: a PDF that doesn’t embed a font needs it on the viewing computer.
- Export and print locations. Note where PDFs and spreadsheets are saved and which printers receive output.
The access method matters here, because Parallels’ feature comparison lists Universal Printer Support and dynamic time zone redirection for both its Windows client and its web client, but lists drag and drop redirection for the Windows client and not the web client, so test the method your staff will use. Dates and number formats can also shift with regional settings, so compare those too.
Step 3: Compare Sample Outputs With the Same Test Data
Run each essential report on the old system and the new one, using the same copy of the data, not data from different days. Use identical filters, date ranges, and parameters, and run both under equivalent approved accounts, since user permissions can change what a report shows. Then compare totals, row counts, layout, page breaks, fonts, and exported files. For printed output, compare paper size, orientation, and scaling too. Save both outputs so someone else can check your result.
Step 4: Decide Who Fixes What
Custom reports in hosted Windows applications can fail in several ways, so the table below gives suggested starting points for troubleshooting. Agree the first contact and escalation path with your application owner, vendor, and hosting provider before migration.
| Symptom | Check first | First owner (example) |
|---|---|---|
| A template is missing or edited | Where it was stored. | App owner |
| Layout or logic differs from the old output | The template and the vendor’s notes. | Vendor, with the app owner |
| The report can’t reach its data | The data connection and any add on. | Host, with the app owner |
| A font, printer, or export folder is wrong | Where the report renders, its fonts, and the access method. | Host, with the app owner |
| Totals differ | The data copy, then the report logic. | App owner, then vendor |
Step 5: Add Report Approval to the Acceptance Checklist
Your application migration checklist should include report approval, because the move isn’t done until the reports that run the business pass. So for each essential report, its owner signs off the comparison before cutover. Use a sheet like this one, with a row for each report.
| Output | Dependency | Owner | Result | Evidence link | Approval date |
|---|---|---|---|---|---|
| Job cost summary (example) | Template in a shared folder, report add on, PDF export folder | Operations manager | Pass, Fail, or Open | Link to saved outputs | Date signed |
| Aging report (example) | Database connection, company font, default printer | Office manager | Pass, Fail, or Open | Link to saved outputs | Date signed |
Open means testing isn’t finished or a problem isn’t resolved. An essential report marked Fail or Open blocks approval until it’s resolved, so record the evidence link and approval date alongside the result.
Our hosted application data migration checklist shows how to reconcile the data behind the reports.
Where CloudTop SaaS Fits
We host Windows applications on Azure with Parallels RAS. Whether your reports work in a hosted environment depends on the application and its add ons, so compatibility is specific to them, and we don’t promise that any report will work before a test. For legacy app hosting, bring your report list to the discussion, then use our compatibility checklist to screen the application first.
CloudTop SaaS is a CloudTop Office company, hosting Windows business software since 2000 through the parent brand.
FAQ
Not sure your reports will survive the move?
Bring your report list, and we’ll discuss what your application and its add ons would need.
