Fix "Looks Like You Have an Incorrect Database" After Migrating Webgility Desktop
You restored your Webgility Desktop backup on a new computer and the app will not open the database — here is how to point Webgility at the right SQL instance so it loads cleanly.
Overview
When you move Webgility Desktop to a new computer and restore your backup, Webgility expects to find a specific SQL Server instance on that machine. If the instance name, authentication mode, or credentials do not match, Webgility shows the message "Uh oh… looks like you have an incorrect database" even though the backup restore itself succeeded.
When This Applies
You moved from a hosted environment such as RightWorks to a local computer, you took a fresh backup from the old machine, and the restore in SQL Server Management Studio reported success — but Webgility Desktop will not open with that database.
Why This Happens
Webgility Desktop connects to a SQL Server instance named WEBGILITY using mixed-mode authentication with the sa account. A restored backup is tied to the SQL instance that opens it, so if the new computer has no WEBGILITY instance, or the instance uses Windows-only authentication, Webgility cannot read the restored database.
Steps to Fix the Incorrect-Database Error
Step 1: Review the end-to-end move checklist in How to move the Webgility database to a new computer and confirm the new machine meets the system requirements before continuing.
Step 2: Install SQL Server on the new computer using How to Manually Install SQL for Webgility Desktop; during setup, name the instance WEBGILITY, pick Mixed Mode Authentication, and set the sa password to the one Webgility ships with.
Step 3: Restore your backup into that WEBGILITY instance by following How to Restore a Webgility Database Backup.
Step 4: Run the DB Upgrade Utility as shown in How to Run DB Upgrade & Utility so the restored database matches the Webgility Desktop version on the new computer.
Step 5: Open Webgility Desktop, choose Connect to an existing SQL Server, enter the computer name followed by \WEBGILITY, and sign in with the sa account — the application opens on your restored data.
Important Note
Note: The restore must happen inside the WEBGILITY-named instance; restoring into the default instance leaves the file on disk but Webgility Desktop cannot find it.
Key Recommendation
Keep the WEBGILITY instance name, the mixed-mode authentication setting, and the sa password the same across every computer that runs Webgility Desktop so your backups move cleanly between machines.
Additional Support
If the error returns after these steps, contact Webgility Support with the new computer name, the SQL instance name you created, and a screenshot of the error so the team can confirm the connection details.