We have about 240,000 ticket in our ITSM system. How long do you think the down time will be converting to ESM? How long did it take for yall to convert?
For an environment with approximately 240,000 tickets, the conversion of SolarWinds Service Desk from standard ITSM to Enterprise Service Management (ESM) typically results in several hours of controlled downtime, but the exact duration depends primarily on data complexity rather than just ticket count. In most comparable environments, organizations report 4–12 hours for the full migration window.
Below are the factors that most directly influence the timeline.
Observed ranges from similar implementations:
Ticket Volume
Typical Downtime Window
<100k
2–4 hours
100k–300k
4–12 hours
300k–1M+
8–24 hours
With 240k tickets, most organizations land in the half-day maintenance window category.
The ESM enablement process restructures the backend data model to support multiple service providers and shared configuration objects. The migration process generally includes:
Ticket volume affects primarily:
Attachments can significantly increase the runtime.
Your environment size is only one variable. The biggest multipliers are:
If many tickets include files, conversion time increases noticeably.
Large numbers of workflows or automations may require validation and remapping.
Fields shared across modules must be reorganized into ESM structures.
If external systems are connected, SolarWinds often pauses or reinitializes them during migration.
Large reporting datasets can add several hours.
For 240k tickets, most administrators plan for:
Estimated outage window:6–10 hours
This usually includes:
Many companies schedule it as an overnight maintenance window.
Administrators who shorten the conversion window usually:
These steps reduce indexing and relationship processing.
A practical change window used by many teams:
Planned outage: 8 hoursExpected runtime: 4–6 hoursBuffer: rollback + validation.
This gives operational safety without rushing the process.
