SolarWinds ends support for Web Help Desk versions 12.4 through 12.8 on November 30, 2026. If you’re running one of those versions, you have a decision to make before then — and migrating from SolarWinds Web Help Desk to another platform is one of the options. This article covers how to move your data into InvGate Service Management if you choose that route.
Web Help Desk hasn’t been discontinued: it continues as version 2026.2.1, now sold only on an annual subscription. But anyone staying on an older release has a short window to plan their next step.
What changes for Web Help Desk on November 30, 2026
On November 30, 2026, SolarWinds ends support for Web Help Desk versions 12.4 through 12.8. Once support ends, those releases no longer receive updates, security patches, or technical assistance, which leaves anyone still on them running an unsupported help desk.
The product itself continues. SolarWinds has rebuilt Web Help Desk, and the current release — version 2026.2.1 — is sold only on an annual subscription.
If you’re on one of the affected versions, you have three options:
- Upgrade to the latest Web Help Desk release and move onto the annual subscription.
- Switch to SolarWinds Service Desk, the company’s cloud-based Service Management product.
- Move your data to a different platform, if the pricing change or the redesign has you weighing other SolarWinds alternatives.
The rest of this article covers that last path: how to migrate your Web Help Desk data into InvGate Service Management.
What you can bring over
When moving from Web Help Desk to InvGate Service Management, the following data can be migrated:
- Tickets (requests)
- Conversation history
- Attachments
- Linked requests
- Linked assets (if you use Asset Management in InvGate)
- Locations
- Departments (mapped to Groups in InvGate)
Our process has been tested across various setups, including Microsoft SQL, MySQL, and PostgreSQL databases. The goal is to preserve historical records that still matter while allowing you to move forward with a better interface and modern ITSM functionality.
How the migration process works
We begin by connecting to your WHD database and retrieving the required information. Our script handles most of this, using pre-built queries designed for the WHD schema.
The data is extracted directly from your database in a non-intrusive way, so there’s no impact on your live environment.
The supported database types are:
- Microsoft SQL Server
- MySQL
- PostgreSQL
We’ll also set up InvGate Service Management to receive the imported data, using the credentials you provide. Once configured, the script pulls the data and organizes it into a structure that matches what InvGate expects, keeping the data clean and consistent.
Attachments are handled with a dedicated converter tool that transforms and prepares them for import. This ensures they’re correctly linked to their respective requests once loaded into InvGate.
The final step uses the InvGate Importer to push the data through the RESTful API. Logs are generated to help track the results and catch any minor issues if they appear.
At the end of the process, you’ll have your historical data in place and ready to continue operating smoothly in InvGate Service Management.
What to expect after migrating from WHD
The goal of this process is to move your valuable data — not to clone your old system. That means the interface, ticket views, and some workflows will look and feel different. But once you’re settled in, you’ll benefit from a platform designed with modern IT operations in mind.
And if there’s anything specific you want to keep (like custom fields or particular tags), our team can work with you to adapt the import process as needed.
Ready to make the switch?
Whether you're still weighing your options or already planning to move away from WHD, we’re here to help.
If InvGate Service Management looks like the right fit, you can start a free trial or talk to our team about what a migration would look like for your setup.
