Picture the day you ask your hosting provider for your data. A file arrives. A file proves you have data. A restore proves you have an application. A hosted application data migration checklist starts there: can a copy of your database run your software somewhere else?
Most owners find out the answer too late, in the middle of a provider change, with the old contract running out. The better time is while you’re still a customer and the people involved want it to work. This test works with any provider, including us.
A Hosted Application Data Migration Checklist You Can Run Before You Leave
Five tests, in order. Each has a pass condition and a piece of evidence to keep. The examples assume SQL Server, since that’s what many legacy Windows applications run on. Other engines follow the same steps with different tools.
T1 Inventory what moves
DO
List each database, its engine and version, and the files behind it. Add what lives outside the database: attachments, report templates, and scanned documents. Then list what the application needs from the server around the database: logins and permissions, scheduled jobs, linked servers, credentials, encryption keys and certificates, and full text indexes.
PASS WHEN
Each item has a name, an owner, and a destination on the new side.
KEEP
The signed inventory.
T2 Confirm versions, licenses, and approval
DO
Pick the target SQL Server version and check that your software vendor supports it. Microsoft says a SQL Server backup can’t be restored by an earlier version, so aim at the same version or a newer one. Confirm the vendor allows hosting at the new provider, and whether it wants an addendum. Our guide to
bring your own license hosting has an email template.
PASS WHEN
The vendor’s approval is in writing and the target version is on its supported list.
KEEP
The vendor’s email or addendum, and your license terms.
T3 Collect keys and credentials through secure channels
DO
Gather what the data can’t be used without: passwords for SQL logins, the database master key password if the data is encrypted, certificates and keys, any password set on the backup itself, credentials used by scheduled jobs, and application license keys. Send them through a secure channel agreed in advance, and send keys on a different channel from the backup.
PASS WHEN
The receiving team has tested each credential and key, and a date is set to replace the shared ones after cutover.
KEEP
A log of what was sent, when, through which channel, and who confirmed it.
T4 Restore a copy and test real workflows
DO
Restore the backup as a copy on the new side, under a new database name and not over the live one. Check the file paths first, and move the files if the drives differ. Recreate the logins and scheduled jobs. Then run what staff do all day: sign in with real roles, open a record with attachments, run a report, post a transaction, print, and let a scheduled job run.
PASS WHEN
The application starts against the copy, each workflow gives the expected result, and record counts and totals match the source.
KEEP
The restore log, the workflow results, and a comparison of counts and totals.
T5 Agree cutover and completion evidence
DO
Set a freeze time, take a final backup, restore it, switch the application’s connection, and reconcile again. Keep the old environment until the reconciliation is signed. Then ask the old provider for written confirmation that your access is removed and your data is deleted.
PASS WHEN
Both sides have signed the reconciliation, and deletion is confirmed in writing.
KEEP
The final backup record, the signed reconciliation, and the deletion confirmation. Our post on
who owns your data in cloud hosting covers the contract clauses behind this step.
SIGN OFF
Previous provider, and date
What the SQL Server Backup Restore Test Catches
Microsoft’s documentation on copying databases with backup and restore describes the traps. A restore recreates the database files in the same paths as the source by default, so a missing drive or folder stops it until you move the files. The login that runs the restore becomes the database owner. Logins and scheduled jobs live outside the user database, so Microsoft says you may have to recreate them on the new server.
Its page on managing metadata on another server adds more. A database user without a matching login becomes an orphaned user and can’t sign in. Encrypted data needs its master key opened on the new server. Scripted logins leave their passwords behind, so SQL authentication logins need attention. Some options, such as TRUSTWORTHY and Service Broker, may be off by default on the new server.
A restore test turns an application data export from a guess into evidence. It finds these failures in an afternoon, where a cutover finds them on a Monday morning. We’d put the restore test before the notice letter.
Where We Fit in a Hosting Provider Exit
This hosted application data migration checklist doesn’t depend on who your provider is. At CloudTop SaaS, export tools and exit assistance are written into the contract, and automated daily backups come with a tested point in time restore. We confirm compatibility on a discovery call and send a written summary the same day. If you’re weighing a move to us, the compatibility checklist and the on premise server to cloud migration guide cover the front end of the same process.
CloudTop SaaS is a CloudTop Office company, hosting Windows business software since 2000 through the parent brand. This article covers SQL Server specifics from Microsoft’s documentation, so confirm your application’s database engine with your software vendor.
FAQ
How do I test a SQL Server backup before leaving a hosting provider?
Restore it as a copy on a test server, under a new database name. Check the file paths, recreate the logins, then run real workflows and compare record counts and totals with the source. Keep the results as evidence.
Why do users get login errors after a restore?
Logins are stored outside the user database. A database user with no matching login on the new server is orphaned and can’t sign in until the login is recreated.
Can I restore a SQL Server backup on an older version?
No. Microsoft says a SQL Server backup can’t be restored by an earlier version. Restore to the same version or a newer one that your software vendor supports.
What do I need besides the database backup?
Passwords for SQL logins, the master key password for encrypted data, certificates and keys, credentials for scheduled jobs, and application license keys. Microsoft notes that scripted logins don’t carry their passwords.
Who should sign off a data handoff?
Your team, the previous provider, and the new host, all against the same written inventory. A signed reconciliation of counts and totals is the completion evidence.