Upgrading a Hosted Windows App: Plan the Change
An upgrade that works on the vendor’s test machine can still surprise you on yours.
Hosted application upgrade planning is how you avoid that surprise. It means agreeing who changes what, how you’ll check the result, and what you’ll do if the change goes wrong, before anyone touches the live system. This guide covers keeping a useful legacy application in service through an upgrade, part of managed legacy app hosting, so the worksheet at the end holds the plan.
Step 1: Record the Reason, the Target Version, and the Dependencies
Write down why you’re upgrading, such as a fix, a feature, or vendor support, and which version you’re moving to. If nothing forces the change, compare the risks of upgrading now with the security, support, and compatibility risks of delaying, because Microsoft’s safe deployment guidance notes that all deployments carry risk and that failing to update brings risks of its own. Then list what the application depends on: its database, the Windows version, integrations, custom reports, scheduled overnight jobs, add ons, and any license key. Ask your vendor to confirm in writing which Windows and database versions the target version supports.
Step 2: Agree Vendor, Host, and Customer Tasks
Three parties share an upgrade, but each assumes another one is handling the gaps. As an example, the vendor supplies the upgrade package, the host runs the environment, and you test the workflows, approve the result, and tell your staff. Treat that split as a starting point to agree under your support contracts, so name who installs the upgrade, who runs database conversions, and who executes recovery. Then agree how the parties contact each other, and name one approver who can say go or stop. A new version can change your license terms, as our guide to bring your own license hosting explains.
Step 3: Plan Backups, Rollback Limits, and Testing
Take a backup before the change, then rehearse restoring it before the change window. Our hosted application data migration checklist shows how to run a restore test. Record what the restore test demonstrated and which recovery limits remain.
Then define both recovery options and a decision deadline. Rolling back undoes the change and returns to the last known working version, while rolling forward fixes the problem in the new version. Microsoft’s guidance describes both, but flags database and other stateful changes as complex to roll back. For each option, agree how changes made after the backup would be preserved or reconciled, since that’s where data gets lost.
Run your application testing on a copy first, so you find problems without touching live data, and keep copied environment tests connected to test destinations. Production checks involving invoices, orders, or emails need an agreed method, so a test doesn’t create a real business transaction. Use real workflows, reports, and scheduled jobs, so you can keep a software upgrade checklist of what passed.
Step 4: Schedule the Downtime and Check Daily Workflows
Pick a window when work is light, tell staff what to expect, and agree who is on call. During the window, pause user writes and integrations, finish active jobs or stop them in a controlled way, and take the final consistent backup before upgrading. Complete the agreed application testing checks before reopening access, so have an approved user run the daily workflows, such as entering an order and printing. Compare the results with the old version using the same test data, then keep watching for the first few days.
The Change Worksheet
Use this change worksheet as your software upgrade checklist. Fill in an owner and an acceptance test for each line, and don’t schedule the window until each line has both.
| Item | Owner | Acceptance |
|---|---|---|
| Business reason and target version | The approver agrees the reason and the version in writing. | |
| Dependencies list | The vendor confirms each supported version in writing. | |
| Vendor, host, and customer tasks | Each task, including install, database conversion, and recovery, has a name. | |
| Backup and restore rehearsal | A restored copy runs, and the recovery limits that remain are recorded. | |
| Roll back or fix forward, with a deadline | The approver knows what each option would lose and when the choice is made. | |
| Test on a copy | Workflows, reports, and jobs pass on the copy. | |
| Downtime window, write pause, and notice | Writes pause, active jobs are handled, and staff have the date and a contact. | |
| Daily workflow check and sign off | Each daily workflow passes under an approved user, and the approver signs. |
Where CloudTop SaaS Fits
We host Windows applications on Azure with Parallels RAS, but an upgrade changes the application, so responsibilities and scope are specific to your application, your vendor, and your agreement. For hosted application upgrade planning, bring the application’s name, its current and target versions, and your worksheet. Our compatibility checklist screens the application first.
CloudTop SaaS is a CloudTop Office company, hosting Windows business software since 2000 through the parent brand.
FAQ
Planning an upgrade to an application you already host?
Bring your worksheet, and we’ll discuss responsibilities and scope for your application.