Covia logo

Case study · ITSM migration

How Covia moved 1.03M+ ServiceNow records to Freshservice on time for go-live

Covia moved nine years of IT service desk history from ServiceNow into Freshservice on a fixed go-live date. 1.03M+ records came across in English and Spanish, 369K+ of them in one weekend.

ServiceNowtoFreshservice

Scope my migration

Free sample migration of 100 of your records, plus a fixed quote within 24 hours.

Gary HuckService Desk Supervisor, Covia

The project in numbers

records moved with full history
1.03M+
records moved ahead of go-live
663K+
records moved in one weekend
369K+
of service desk history
9 years

In short

Customer:
Covia, an industrial minerals company headquartered in Independence, Ohio, with operations across the United States and Mexico.
The move:
ServiceNow, its platform of nine years, to Freshservice.
The scope:
1.03M+ records: tickets, problems, changes, contacts and organizations, with their conversation history, in English and Spanish.
The constraint:
A go-live date set by a wider IT program, and nine years of history that had to be ready for agents from day one.
The outcome:
On time for go-live, with nine years of history intact.

The challenge

Covia's IT team set out to reshape its whole IT offering to be simpler and more user-centric. Moving the service desk off ServiceNow, its platform of nine years, sat at the centre of that change.

The migration ran alongside several other internal changes. It had to land on a timeline set by the wider program, with nine years of operational history ready for agents from day one.

Finding the right partner was a challenge of its own. The providers Covia approached could not meet both its timeline and its budget. Covia needed a team that could start right away, handle more than a million records, and shape the engagement around its needs.

What made it hard

  • Nine years of accumulated data. Picklist values with no match in the new platform, out-of-sequence timestamps and duplicate contacts. Every long-running instance collects these, and most only appear during a full run.
  • Two platforms' API limits. More than a million records had to move within the API limits of both ServiceNow and Freshservice, inside a fixed window.
  • Every record traceable to its source. Agents needed to find any historical ticket, request or task by its original ServiceNow number.
  • Two regions and two languages. US and Mexico operations, with records in English and Spanish that had to arrive intact and readable.

We chose MigrateX because they had the right people, the availability to start when we needed, and flexibility on price. That's the trifecta that actually wins business.

Gary HuckService Desk Supervisor, Covia

What we did

As Covia's needs changed during the program, MigrateX adapted with them. The work came down to five things.

  1. Moved the history ahead of go-live

    663K+ records, in English and Spanish, were moved ahead of go-live, with a final delta sync timed to the cutover window. The migration and change management teams worked in step, and a fully migrated instance was handed over for go-live checks and user communications.

  2. Brought service catalog history across in one weekend

    210K+ service catalog tasks and 159K+ comments moved into the live instance over a single weekend: 369K+ records in all. Each task kept its ServiceNow ID and stayed linked to its parent request.

  3. Kept the change history whole

    Every change task was attached to its parent change record, closed changes included, and each change was returned to its original state. The full change history now sits in one place.

  4. Paused notifications during each run

    Notifications, CSAT surveys and workflows were paused for each run and restored straight after.

  5. Carried the original numbers across

    The original ServiceNow numbers came across with the records and are searchable in Freshservice, so agents can find a historical ticket, request or task by the number they already know.

As far as the data goes, the MigrateX team has it handled. Scope it right, and they'll make sure everything gets across, so you can focus your energy on the workflows. They make the data seem like the straightforward part.

Gary HuckService Desk Supervisor, Covia

The result

Covia went live on time, with nine years of history intact.

MigrateX moved at Covia's pace and adapted as its needs changed. That left the help desk free to focus on what comes next: redesigning service journeys, automation and on-call alerting in the new platform.

1.03M+ records
Tickets, problems, changes, contacts and organizations, with their conversation history, in English and Spanish.
369K+ records in one weekend
Service catalog tasks and their comments, brought into the live instance in a single weekend.
Change history linked
Change tasks attached to their parent changes, with each change returned to its original state.
Original numbers searchable
ServiceNow IDs carried across, so history can be found by its original number.
Months of effort avoided
Covia's own estimate for the data export alone, before ingestion and translation.

If we'd done it ourselves, we'd be looking at months just for the data export, let alone ingesting and translating it.

Gary HuckService Desk Supervisor, Covia

Planning the same route?

Start with 100 of your records.

Scope my migration

Free sample migration of 100 of your records, plus a fixed quote within 24 hours.