---
title: "SolarWinds Web Help Desk 12.x End of Life (2026): Upgrade or Migrate"
slug: solarwinds-web-help-desk-12x-end-of-life-2026-upgrade-or-migrate
date: 2026-11-16
author: Raajshekhar Rajan
categories: [SolarWinds Service Desk, Migration Guide, Help Desk]
excerpt: "SolarWinds Web Help Desk 12.x loses support November 30, 2026. Here are the 2026.2.x upgrade trade-offs and how to migrate your data."
tldr: "WHD 12.4–12.8 hit end of life Nov 30, 2026. Upgrade to 2026.2.x (which has no REST API in 2026.2.1 and no classic UI) or migrate to a new platform. Export data via API while still on 12.x."
canonical: https://clonepartner.com/blog/solarwinds-web-help-desk-12x-end-of-life-2026-upgrade-or-migrate
---

# SolarWinds Web Help Desk 12.x End of Life (2026): Upgrade or Migrate


# SolarWinds Web Help Desk 12.x End of Life (2026): Upgrade or Migrate

**SolarWinds Web Help Desk (WHD) versions 12.4 through 12.8 lose all technical support on November 30, 2026** ([documentation.solarwinds.com](https://documentation.solarwinds.com/en/success_center/whd/content/release_notes/release_history.htm)). End-of-engineering already passed on July 4, 2026 — no more bug fixes, service packs, or workarounds for any 12.x release. You have two options: upgrade to WHD 2026.2.x, or migrate your data to a different platform.

Both paths have real trade-offs. The upgrade path carries breaking changes that SolarWinds' marketing doesn't lead with — including a REST API that is missing from 2026.2.1 and subscription licensing you should price before you commit. The migration path requires extracting data from a legacy on-premises system with specific technical hurdles at the database level. This guide covers the exact timeline, what breaks when support ends, the technical state of the 2026.2.x upgrade, the database-level mechanics of data extraction, and how to decide between the two options.

> [!WARNING]
> **Web Help Desk ≠ SolarWinds Service Desk.** These are completely separate products with separate codebases. Web Help Desk is self-hosted, on-premises software running on a Java application server with a relational database. SolarWinds Service Desk (formerly Samanage) is a cloud-based SaaS ITSM platform with its own API and pricing model. There is no direct upgrade path between them — moving from WHD to Service Desk requires a full data migration, just as it would if you were moving to ServiceNow or Freshservice. This article covers Web Help Desk only. For Service Desk alternatives, see our [SolarWinds Service Desk Alternatives guide](https://clonepartner.com/blog/blog/solarwinds-service-desk-alternatives-2026-tco-features-migration).

## What does WHD 12.x end of life actually mean?

**End of life for WHD 12.x means SolarWinds stops providing technical support after November 30, 2026, on top of the service releases and bug fixes that already stopped at end of engineering on July 4, 2026.** The SolarWinds release history page lists identical lifecycle dates for every 12.x minor version — 12.4, 12.5, 12.6, 12.7, and 12.8 all share the same end-of-life date ([documentation.solarwinds.com](https://documentation.solarwinds.com/en/success_center/whd/content/release_notes/release_history.htm)).

Three dates matter:

| Milestone | Date | What stopped |
|---|---|---|
| **EOL announcement** | June 2, 2026 | SolarWinds formally notifies customers to begin transitioning |
| **End-of-engineering** | July 4, 2026 | No more bug fixes, workarounds, or service packs for 12.x |
| **End-of-life** | November 30, 2026 | Technical support ends entirely — no tickets, no phone, no help |

After November 30, your WHD 12.x instance keeps running. The data is still there, the server still boots. But no one at SolarWinds will help you when something breaks, and — more critically — no one will patch the next security vulnerability.

For an on-premises application that commonly integrates with Active Directory, email servers, and internal asset databases, running an unpatched instance past EOL is a severe security liability.

## Why staying on WHD 12.x after EOL is a risk you can't manage

This isn't theoretical. Web Help Desk has an active, documented history of critical security vulnerabilities — including ones exploited in the wild against real organizations.

**CVE-2024-28987** was a hardcoded credential vulnerability (CVSS 9.1) in WHD 12.8.3 Hotfix 1 and earlier. CISA added it to the Known Exploited Vulnerabilities catalog on October 15, 2024 ([nvd.nist.gov](https://nvd.nist.gov/vuln/detail/CVE-2024-28987)). The hardcoded credentials allowed remote unauthenticated attackers to access internal functionality and modify data.

Running a 12.x instance past November 30 means absorbing every future vulnerability with no vendor patch available.

The 2026.2.1 release patched a critical SAML authentication bypass, CVE-2026-28323 (CVSS 9.8), which affects instances with SAML 2.0 authentication enabled ([documentation.solarwinds.com](https://documentation.solarwinds.com/en/success_center/whd/content/release_notes/whd_2026-2-1_release_notes.htm)) — an example of the class of vulnerabilities that will go unpatched on 12.x after the EOL date.

The pattern is clear: WHD is an actively targeted attack surface. Running 12.x past November 30 is not a managed risk; it is an unmanaged one.

## The upgrade path: WHD 2026.2.x and its complications

SolarWinds' recommendation is to move from 12.x to the current release, WHD 2026.2.1. If you are on a version earlier than 2026.1, SolarWinds says to upgrade to 2026.1 first, verify it, and then upgrade to 2026.2.1 ([documentation.solarwinds.com](https://documentation.solarwinds.com/en/success_center/whd/content/release_notes/whd_2026-2-1_release_notes.htm)). This is closer to a platform migration within the same product than a routine version bump — and you should confirm the licensing cost before you start.

### Licensing model change: perpetual to subscription

This is the least-publicized change and, for some WHD customers, the most financially significant.

SolarWinds' WHD licensing page describes subscription (term-based) licenses and directs buyers to request a quote. When a license expires, WHD supports only one technician ([documentation.solarwinds.com](https://documentation.solarwinds.com/en/success_center/whd/content/helpdeskinstallproductlicensing.htm)). If you bought WHD on a perpetual license, ask SolarWinds in writing what staying on a supported version will cost you each year.

For organizations evaluating whether to upgrade or migrate, that quote is often the decisive factor. Compare it with the published per-agent prices of the alternatives covered below over a 3-year horizon.

### The initial 2026.2 release was pulled

SolarWinds removed WHD 2026.2 from the release portal while it completed "additional quality work" ([documentation.solarwinds.com](https://documentation.solarwinds.com/en/success_center/whd/content/release_notes/whd_2026-2_release_notes.htm)). The 2026.2.1 release notes list a fix for upgrades to 2026.2 that failed with errors.

WHD 2026.2.1 was released on July 30, 2026 as the follow-up release. It is now the current version.

### Breaking changes in 2026.2.x

The 2026.2 line is a major architectural overhaul. Key changes that affect daily operations and integrations, per SolarWinds' 2026.2.1 release notes ([documentation.solarwinds.com](https://documentation.solarwinds.com/en/success_center/whd/content/release_notes/whd_2026-2-1_release_notes.htm)):

- **REST API removed.** The WHD REST API exposed at `/helpdesk/WebObjects/Helpdesk.woa/ra/` is not available in 2026.2.1. SolarWinds lists this as a known issue and says it will return in a future version. Its WHD 2026.4 release-candidate notes, dated October 26, 2026, say the REST API returns there, but SolarWinds says RC content is not a commitment ([documentation.solarwinds.com](https://documentation.solarwinds.com/en/success_center/whd/content/release_notes/whd_2026-4_release_notes.htm)). Any integrations, monitoring, or automation scripts that use the WHD REST API will break on upgrade to 2026.2.1.
- **Classic interface removed.** The old UI is gone. 2026.2.1 completes the migration to the redesigned modern interface. Workflows and muscle memory built around the classic UI need re-training.
- **Tomcat replaced with Caddy.** The bundled Tomcat server has been replaced with Caddy as the front-end HTTP server, and certificates now use PEM files instead of Java keystores. Custom Tomcat configurations, SSL setups, or reverse-proxy rules tied to the old architecture need rework.
- **Servlet authentication removed.** Organizations authenticating via Servlet must switch to SAML 2.0 or HTTP Header authentication before upgrading.
- **CentOS 6, CentOS 7, and RHEL 7 dropped.** If your WHD server runs on any of these, you need an OS migration before the application upgrade.
- **No in-place upgrade on Linux.** SolarWinds says an upgrade for any Linux version is not supported in 2026.2.1, so Linux deployments need a fresh install with migrated settings.
- **macOS requires version 13+.** Older macOS deployments are no longer supported.
- **No high-availability deployments.** The multi-instance Tomcat setup used for high availability in earlier versions is not available in 2026.2.1.
- **Exchange Web Services replaced by Microsoft Graph API.** Email integration with Exchange or Microsoft 365 now requires Graph API configuration.
- **New MySQL JDBC driver required.** External MySQL databases need a new JDBC driver for MySQL 8.0, 8.4 or 9.x.

> [!CAUTION]
> **Extract your data before upgrading.** The REST API is available on 12.x but not on 2026.2.1. If you need to programmatically export tickets, clients, assets, or other data via the API, do it while you're still on 12.x. Once you upgrade to 2026.2.1, that extraction path is gone until SolarWinds restores API access in a later release.

### Infrastructure prerequisites

Legacy WHD instances (12.4–12.7) often run on older operating systems and database engines. Beyond the breaking changes above, verify:

- **Operating system:** If your instance runs on Windows Server 2012 or 2012 R2, Extended Security Updates for that OS ended on October 13, 2026 ([learn.microsoft.com](https://learn.microsoft.com/en-us/lifecycle/faq/extended-security-updates)). Move to an operating system on WHD 2026.2.1's system requirements list. For Linux, SolarWinds supports fresh installs on CentOS 9 and 10 and RHEL 9 and 10.
- **Database engine:** SolarWinds says embedded-database behavior differs between an upgrade to 2026.2.1 and a fresh installation, so read its installation and upgrade guide before you plan the database step.
- **SSL certificates:** Custom SSL certificates stored in the legacy Java keystore must be backed up and converted, because 2026.2.1 uses PEM files. The move from Tomcat to Caddy changes where and how TLS termination is configured.

If you choose this route, stand up a parallel 2026.2.1 server, copy the database, and test the application upgrade in a staging environment before touching production.

### Is the upgrade worth it?

If you're committed to staying on Web Help Desk, upgrading to 2026.2.1 is not optional — it's the only way to keep receiving security patches. But go in with realistic expectations. Budget time for re-testing integrations, re-training technicians on the new UI, potentially reworking your email and authentication configurations, working around the missing REST API, and absorbing your subscription costs.

## How to get data out of Web Help Desk

Whether you're migrating to another platform or creating a safety-net archive before upgrading, you need a reliable data extraction strategy. WHD offers three paths — REST API, direct database export, and built-in TSV and Excel export — and which one works depends on your current version, technical resources, and what you're doing next.

### Identifying your database configuration

Before choosing an extraction method, determine whether your WHD instance uses the embedded PostgreSQL database or an external database. WHD supports embedded and external PostgreSQL, MySQL, and Microsoft SQL Server ([documentation.solarwinds.com](https://documentation.solarwinds.com/en/success_center/whd/content/helpdeskconfiguresqlservermysql.htm)). Check the Database Connection page at **Setup > General > Database** in the WHD admin console to see which one your instance uses.

If embedded: the PostgreSQL process runs locally on the WHD server, listening on port **20293** by default, and the default database user is `whd` ([support.solarwinds.com](https://support.solarwinds.com/SuccessCenter/s/article/Back-up-and-restore-the-PostgreSQL-database-using-the-command-line)).

If external MySQL or SQL Server: standard connection details for that engine apply. WHD 2026.2.1 needs a new JDBC driver for MySQL 8.0, 8.4 or 9.x.

### REST API (12.x and 2026.1)

**Web Help Desk's REST API** is the cleanest extraction path for structured data. SolarWinds documents it for 2026.1 and earlier, but it is not available in 2026.2.1 ([documentation.solarwinds.com](https://documentation.solarwinds.com/en/success_center/whd/content/helpdeskprogrammingrestapi.htm)). Requests and responses use JSON or XML, and calls authenticate with an API key. SolarWinds also says it cannot help you write code against the API.

```bash
# Retrieve one ticket by ID (12.x and 2026.1)
curl -s "https://your-whd-server/helpdesk/WebObjects/Helpdesk.woa/ra/Tickets/100?apiKey=YOUR_API_KEY"
```

**Practical constraints for bulk extraction:**

SolarWinds does not document the API as a bulk-export tool. Build your extraction script defensively:

- **Re-authentication:** Handle `401 Unauthorized` responses and re-authenticate automatically.
- **Server errors under load:** Back off and retry on `5xx` responses, and log any page you could not fetch instead of skipping it silently.
- **Pagination drift:** If records are modified during extraction, page offsets can shift, resulting in skipped or duplicated records. Filter by last-updated time for delta runs rather than relying solely on page offsets.

For large initial extractions, a database dump is faster and more complete than the API. Use the API for smaller exports and delta runs.

### Direct database export

WHD uses an embedded **PostgreSQL** database by default (version 9 or 13, depending on your WHD release). Some deployments use an external PostgreSQL instance, MySQL, or Microsoft SQL Server. Because you own the host infrastructure, you have direct access to this database. A direct dump gives you everything — every table, every relationship, every attachment — and it is much faster than the API for bulk extraction.

For the embedded PostgreSQL database, SolarWinds' command-line backup article uses this pattern ([support.solarwinds.com](https://support.solarwinds.com/SuccessCenter/s/article/Back-up-and-restore-the-PostgreSQL-database-using-the-command-line)):

```bash
# Embedded PostgreSQL. On PostgreSQL 13 installs, replace the user and database name if yours differ.
pg_dump -Fc -v -h 127.0.0.1 -p 20293 -U whd whd > whd_pgdump.backup
```

For MySQL deployments, a standard `mysqldump` works. SolarWinds also provides a web console backup under **Setup > General > Database**.

To transform the extracted data for a target platform, you need to understand the core WHD relational schema. SolarWinds' own support articles name **`JOB_TICKET`** as the central ticket table and **`TECH`** as the technician table ([support.solarwinds.com](https://support.solarwinds.com/SuccessCenter/s/article/Performance-Tuning-in-Web-Help-Desk-to-fix-slow-performance?language=en_US)). Clients, ticket statuses, custom field values and definitions, and attachments sit in their own tables. List them on a restored copy before you write mapping queries:

- **Statuses** — your custom WHD statuses must be mapped to the state machine of your target ITSM.
- **Custom fields** — values are stored apart from the ticket row. Migrating them to the flat structures modern REST APIs expect means pivoting the values, joining them to their field definitions, and then joining to `JOB_TICKET`.
- **Attachments** — WHD stores attachments in the database, each with its own URL ([documentation.solarwinds.com](https://documentation.solarwinds.com/en/success_center/whd/content/helpdeskmigratingapplication.htm)).

SolarWinds also says not to modify the default schemas, so run every query read-only. Direct database extraction requires careful query design to avoid locking production tables. Create a read-only database user and execute extractions against a restored backup or a read replica — not the live production database.

**When to use this:** Direct database export is the right choice when you need a complete archive of everything, when the REST API doesn't expose the data you need, or when you've already upgraded to 2026.2.x and lost REST API access.

### Built-in TSV and Excel export (non-technical fallback)

WHD includes a built-in export available without database or API access. Tickets export as PDF, TSV or Excel. Clients, parts, FAQs and purchase orders export as TSV or Excel, and assets as PDF, TSV or Excel ([documentation.solarwinds.com](https://documentation.solarwinds.com/en/success_center/whd/content/helpdeskimportdata.htm)). For tickets, open a ticket list under **Tickets**, select the tickets, and choose **Download TSV** from the toolbar.

This path has significant limitations compared to API or database extraction:

- **Flat files only.** Exports are lists, so attachments must be retrieved separately from the database.
- **No relational integrity.** Relationships between tickets, notes, assets, and clients are flattened.
- **Cell size limit.** SolarWinds limits TSV file cells to 32 KB, so long ticket text can be cut.
- **Version differences.** SolarWinds' 2026.4 release-candidate notes list a fix that restores ticket notes and custom fields to ticket TSV exports, so check what a 2026.2.1 export actually contains before relying on it.
- **No programmatic control.** Ticket exports work from a selected list in the browser, not on a schedule.

Use the built-in export only as a last resort when database access is unavailable and the REST API cannot be used (for example, after upgrading to 2026.2.x with no immediate database access). It is adequate for auditing data volume and spot-checking field values, but not for a complete migration.

### Handling attachments

Attachments are the most complex component of a WHD migration. SolarWinds says WHD stores attachments in the database, and each attachment has its own URL that depends on the server's DNS name ([documentation.solarwinds.com](https://documentation.solarwinds.com/en/success_center/whd/content/helpdeskmigratingapplication.htm)). Old links in emails or other systems can break once the WHD server is gone.

Extraction means reading each attachment's binary data from a restored copy of the database and either streaming it to the target API or writing it to disk before uploading via `multipart/form-data`.

Run a **pre-migration attachment audit** on that restored copy: count the attachments per ticket, confirm each one reads back with a non-zero size, and log any that fail. Report broken attachments before — not during — the production migration.

### What constitutes a valid sample migration

Before running a full migration, validate your data mapping against a representative sample. A minimal viable sample should include:

- **At least 500 tickets** spanning all status types (open, closed, pending, on-hold, or your custom equivalents)
- **At least 1 ticket per request type** in your WHD configuration
- **Tickets with custom field values** covering each custom field type (text, dropdown, date, checkbox)
- **Tickets with technician notes, client replies, and internal notes** to validate note type mapping
- **At least 10–20 attachments** across different file types and sizes
- **Tickets linked to assets** to validate relational integrity

Validation checks to run against the sample in the target platform:

1. Record count matches source (no silent drops)
2. Creation and update timestamps preserved in the target's native timezone
3. Requester and assignee relationships intact (not orphaned)
4. Custom field values match source values, including null/empty fields
5. Attachment files open and render correctly (not corrupted)
6. Ticket note ordering preserved (chronological)
7. Status values mapped correctly to target platform equivalents

### Built-in WHD-to-Service Desk migration

SolarWinds provides a free migration tool from Web Help Desk to SolarWinds Service Desk, set out in a five-phase migration guide ([documentation.solarwinds.com](https://documentation.solarwinds.com/en/success_center/swsd/content/completeguidetoswsd/migratetoservicedesk.htm)). Its migration options cover tickets with their notes and attachments, FAQs, vendors, purchase orders, assets and their attachments, plus required metadata such as locations, departments, categories, custom fields, techs and clients ([documentation.solarwinds.com](https://documentation.solarwinds.com/en/success_center/swsd/content/completeguidetoswsd/migratewhdtoservicedesk-phase4_migrateorbuild.htm)).

**This only applies if Service Desk is your target.** If you're migrating to ServiceNow, Freshservice, Jira Service Management, Zendesk, or any other third-party platform, this tool doesn't help.

## Where to migrate: common WHD replacement targets

The right target depends on your operational requirements. WHD users typically fall into a few profiles, each pulling toward a different platform:

**Staying in the SolarWinds ecosystem:** SolarWinds Service Desk is the vendor's own cloud path. It's cloud-based, starts at $39/technician/month billed annually as of November 2026 ([solarwinds.com](https://www.solarwinds.com/service-desk/pricing)), and has the migration tool described above. The trade-off: you lose on-premises control. If you chose WHD specifically for data sovereignty or air-gapped environments, Service Desk may not fit.

**Moving to enterprise ITSM:** ServiceNow, BMC Helix, or Ivanti are common targets for organizations that outgrew WHD's capabilities — especially around change management, CMDB depth, and orchestration. These are multi-month implementation projects where the data migration is the quick part and rebuilding workflows is the long part. See our [ServiceNow migration guide](https://clonepartner.com/blog/blog/how-to-migrate-from-solarwinds-service-desk-to-servicenow) for the technical details.

**Moving to mid-market ITSM:** Freshservice, Jira Service Management, ManageEngine ServiceDesk Plus, or InvGate Service Management map relatively closely to WHD's data model and are typically the fastest migrations. As of November 2026, Freshservice lists its Growth plan at $49/agent/month billed annually ([freshworks.com](https://www.freshworks.com/freshservice/pricing/)), and Atlassian's Jira Service Management pricing page, now sold as Service Collection, lists Standard at $21.50/agent/month ([atlassian.com](https://www.atlassian.com/software/jira/service-management/pricing)). Compare those against your WHD subscription quote at your technician count.

**Moving to customer-support platforms:** If WHD was used for external customer support rather than internal IT, Zendesk, Freshdesk, or HubSpot Service Hub may be better fits. The data model mismatch is significant — WHD's asset management, purchase orders, and CMDB concepts don't translate to these platforms. Expect to archive rather than migrate those records.

> [!NOTE]
> **Keep two clocks apart.** The data migration — moving tickets, assets, contacts, and attachments from WHD to your new platform, the part ClonePartner performs — is one workstream. Rebuilding workflows, training technicians, integrating with existing tools, and configuring the new platform is a separate, typically longer effort. Don't conflate these two timelines when planning your project. The data migration is typically measured in days; the platform implementation is typically measured in weeks or months.

## What data can — and can't — be migrated from WHD

| Data type | Migrates? | Notes |
|---|---|---|
| Tickets (open + closed) | ✅ | Subject, description, status, priority, dates, custom field values |
| Ticket notes and worklogs | ✅ | Technician notes, client replies, internal notes |
| Ticket attachments | ✅ | Requires separate extraction; binary data |
| Clients / requesters | ✅ | Name, email, department, location |
| Technicians / agents | ✅ | Name, email, group membership |
| Assets | ✅ | Asset type, serial, model, linked tickets |
| Custom fields | ✅ | Values migrate; field definitions need manual recreation in the target |
| FAQs / knowledge articles | ✅ | Content and attachments |
| Request types / categories | ⚠️ | Migrate as metadata; require mapping to target platform's taxonomy |
| SLA policies | ❌ | WHD SLA rules don't export as portable objects; rebuild in target |
| Approval workflows | ❌ | Platform-specific logic; rebuild manually |
| Billing rates / time tracking config | ❌ | Configuration-level data; not portable |
| Email templates | ❌ | Recreate in target |
| Dashboard layouts / saved reports | ❌ | Platform-specific; screenshot and recreate |

For a deeper look at what to move and what to leave behind, see our [Help Desk Data Migration Playbook](https://clonepartner.com/blog/blog/help-desk-data-migration-playbook).

## Decision framework: upgrade WHD or migrate away?

This isn't a one-size answer. Here's how to think through it:

**Upgrade to 2026.2.x if:**
- You're satisfied with WHD's feature set and need to stay on-prem
- You don't have REST API integrations (or can wait for API restoration)
- Your server OS is already supported (no CentOS 6/7, RHEL 7, or outdated Windows Server)
- You can absorb the new UI rollout and re-train your team
- You're not using Servlet authentication or legacy Exchange Web Services
- You can handle a fresh install if WHD runs on Linux, where 2026.2.1 has no in-place upgrade
- Subscription licensing is acceptable at your technician count
- Your WHD subscription quote is competitive with alternatives at your scale

**Migrate to another platform if:**
- You've hit WHD's feature ceiling — limited automation, no enterprise service management, basic change management
- You need cloud-native architecture, API-first design, or better integration options
- You want to consolidate into a platform your organization already uses
- The cumulative breaking changes in 2026.2.x — plus the cost of a subscription license — make the upgrade feel like a migration anyway
- You have existing REST API integrations that you can't afford to run without while SolarWinds restores the API
- WHD's CVE history and the unpatched exposure period between vulnerabilities and EOL-blocked patches is a factor in your risk calculus
- You're already paying for a cloud ITSM platform elsewhere and running WHD in parallel

**In both cases:** Back up your database now. A verified `pg_dump` or `mysqldump` is your safety net regardless of which path you take. Don't start either path without it.

## How long does a Web Help Desk data migration take?

**The data migration itself — extracting records from WHD and loading them into the target platform, the work ClonePartner performs — is usually completed within 1–5 business days**, depending on data volume, complexity, and API rate limits on the target platform. Small datasets under 10,000 records can finish in under 24 hours. Large attachment volumes and the target's API rate limits are what stretch a run.

Your technicians keep working in WHD while the bulk history loads during the working days before go-live. Go-live is a Monday morning: WHD is frozen before the working day starts, a final delta of changed records runs in about 30 minutes, and technicians log in to the new platform that morning.

The broader platform transition — selecting the new tool, configuring it, building automations, training staff, testing — is your own clock and is measured in weeks or months. With 12.x support ending November 30, 2026, start scoping now and plan on running unsupported for a short period if your evaluation runs past that date.

## Step-by-step: preparing for a WHD data migration

If you've decided to move off Web Help Desk, here's the practical sequence:

1. **Inventory your data.** Count tickets (open and closed), assets, clients, technicians, custom fields, FAQs, and attachments. Use the WHD admin console Reports section or query `SELECT COUNT(*) FROM job_ticket` directly to establish baseline record counts. This determines scope and timeline.
2. **Identify your database configuration.** Check **Setup > General > Database** to determine whether you're on the embedded PostgreSQL (port 20293) or an external PostgreSQL, MySQL or SQL Server instance. This determines your extraction path.
3. **Export via API while on 12.x.** If you haven't upgraded yet, use the REST API to extract tickets, clients, and assets in JSON. This is the cleanest extraction path — and it's missing in 2026.2.1. Handle re-authentication and server errors with retry logic.
4. **Back up the database.** Run `pg_dump` (PostgreSQL) or `mysqldump` (MySQL), or your SQL Server backup tooling, as a complete archive. Store it off the WHD server. This is your safety net and your source for a direct database migration if needed.
5. **Audit attachments.** Run the attachment audit described above on a restored copy to find unreadable files before they become migration failures.
6. **Map your data model to the target.** WHD's ticket structure — request types, status types, priorities, custom field values stored apart from the ticket row, tech notes, worklogs — needs to be mapped to equivalent fields in the destination. Not everything will have a 1:1 match. Custom fields require joining the stored values to their field definitions and pivoting the result to the target's flat field structure.
7. **Run a sample migration.** Load a representative sample (see the sample criteria above) into the target platform's sandbox. Validate the seven checkpoint list before committing to a full run.
8. **Execute the full migration and validate.** Run the complete migration, verify record counts against the source, spot-check individual tickets with complex histories, and confirm that attachments are accessible.
9. **Run a delta sync.** Technicians keep working in WHD during the bulk load, so at go-live capture any records created or updated since the initial extraction and sync them to the target using timestamp-based filtering.

## The November 30 deadline is real — plan accordingly

With end-of-engineering already behind us and end-of-life on November 30, 2026, the window for a clean transition is shrinking. If you're still on WHD 12.x, the minimum steps right now:

1. **Back up your database** — regardless of what you decide next.
2. **Extract data via REST API** — while it's still available on your 12.x instance.
3. **Get your WHD subscription quote in writing** — factor it into your total cost of ownership comparison against alternatives.
4. **Make the upgrade-vs-migrate decision** — using the framework above.
5. **Start scoping the work** — whether that's an in-place upgrade with all its breaking changes, or a data migration to a new platform.

At ClonePartner, we handle WHD data migrations end to end — extracting from the database or API, mapping the schema, handling attachments, and loading into your target platform. Projects run at a fixed price starting at $500, with unlimited sample migrations included so data mapping is validated before the production run. Our SOC 2 Type II and ISO 27001 controls are independently audited, with AES-256 encryption at rest and TLS 1.2+ in transit. Post-migration, all staging databases are purged within 30 days of project close.

Don't let the deadline turn into an emergency. These transitions are straightforward when planned; they're painful when rushed.

> Book a free 30-minute scoping call with a ClonePartner engineer. Get a fixed-price proposal for your Web Help Desk data migration — whether you're moving to SolarWinds Service Desk, ServiceNow, Freshservice, Jira Service Management, or anything else.
>
> [Talk to us](https://clonepartner.com/talk-to-us?duration=30&utm_source=blog&utm_medium=button&utm_campaign=demo_bookings&utm_content=cta_click&utm_term=demo_button_click)

## Frequently asked questions

### When does SolarWinds Web Help Desk 12.x reach end of life?

All WHD versions 12.4 through 12.8 reach end of life on November 30, 2026. End-of-engineering (no more bug fixes) already passed on July 4, 2026. After November 30, SolarWinds provides no technical support, security patches, or assistance for any 12.x release.

### Is the Web Help Desk REST API available in version 2026.2.1?

No. The WHD REST API is not available in version 2026.2.1. SolarWinds lists this as a known issue and says it will return in a future version. Its release-candidate notes for WHD 2026.4, dated October 26, 2026, say the REST API returns in that release, but RC notes are not a commitment. If you need to extract data via API, do it while still on 12.x before upgrading.

### Is SolarWinds Web Help Desk the same as SolarWinds Service Desk?

No. They are completely separate products. Web Help Desk is self-hosted, on-premises software. SolarWinds Service Desk (formerly Samanage) is a cloud-based SaaS ITSM platform with its own codebase, API, and pricing model. Moving between them requires a full data migration.

### Can I migrate data from Web Help Desk to SolarWinds Service Desk?

Yes. SolarWinds offers a free migration tool, covered by a five-phase migration guide, that moves tickets, FAQs, vendors, purchase orders, assets, their attachments, and metadata from WHD to Service Desk. This tool only works if Service Desk is your target — it doesn't help with third-party platforms.

### How long does a Web Help Desk data migration take?

The data migration itself typically completes in 1–5 business days, depending on data volume, complexity, and target platform API rate limits. Small datasets under 10,000 records can finish in under 24 hours. The broader platform transition (configuration, training, workflow rebuild) is a separate, longer effort.
