Migrate from SolarWinds to HaloITSM

Agree which SolarWinds records to retain and how to redesign categories, routing and related incident handling in HaloITSM.

SolarWinds to HaloITSM in education

The published case describes a migration of about 71,000 historical tickets and roughly 200 open tickets. The team went live five weeks after discovery began.

Read the education migration case.

Map SolarWinds records to HaloITSM

Use this example to choose which records to move, what to redesign and what to validate. The supported mapping depends on your export and agreed scope.

SourceHaloITSM destinationDecision and validation
Historical tickets and attachmentsRetained HaloITSM ticket recordsAgree date ranges and compare counts and representative records after a test import.
Open requests and incidentsActive HaloITSM ticketsValidate status and ownership before cutover and reconcile any work created during the changeover.
Categories and assignmentNew taxonomy and team routingRedesign generic intake around request types, teams and measurable service work.
Recurring related incidentsProblem records and linked incidentsTest related incident handling and who can send shared updates.

Prepare the test import

Bring a representative export and name the records and workflows that matter to the service desk. The migration checklist covers test imports, reconciliation and who signs off cutover.