Enterprise Vault Migration Case StudyNHS Wales:
ten years became eighteen months.

NHS Wales needed archived email for 180,000 mailboxes moved out of Enterprise Vault and into NHSmail. Done by hand, the estimate was a decade. With the migration automated end to end, it took eighteen months.

Organisation
NHS Wales
Sector
Public healthcare · Wales, UK
Source
Symantec / Veritas Enterprise Vault
Destination
NHSmail
Scale
180,000 mailboxes
Result
Completed in 18 months against a 10-year manual projection

The situation

NHS Wales runs one of the largest email estates in the UK public sector. As its organisations moved onto NHSmail, the shared national email service, the archived mail sitting in Enterprise Vault had to go with them. Clinicians and administrators still needed that history, and governance rules meant none of it could be lost or exposed on the way.

The first plan was manual. Teams tracked archives in spreadsheets and moved them a batch at a time. It worked, slowly. At the rate it was going, the programme was projected to take around ten years, which would have meant a decade of running, patching and paying for legacy archive infrastructure, and a decade of risk that a mailbox would be missed, moved twice or landed in the wrong place.

Why it was hard

Volume. 180,000 mailboxes is not a number you can manage on a spreadsheet. Every manual handoff is a chance for an archive to be skipped or duplicated.

Governance. This is health service email. Every item had to be accounted for between Enterprise Vault and NHSmail, with evidence that would stand up to scrutiny.

User experience. Staff were used to opening archived mail from shortcuts in their mailbox, in folders they had organised themselves. Whatever arrived in NHSmail had to look and behave the way they expected.

How the programme ran

  1. Automate the whole pipeline. The spreadsheets were retired. Extraction from Enterprise Vault, transfer and placement into the right NHSmail mailbox ran as one automated workflow, so no archive depended on someone remembering to move it.
  2. Scale out with distributed agents. Rather than one server working through the estate, agents processed many archives in parallel. Throughput was a question of how many agents to run, not how many people to hire.
  3. Keep the user's view intact. Shortcuts and folder structures were preserved, so archived items appeared where staff expected to find them.
  4. Record everything. Every message was logged on its way from source to destination, giving a chain of custody for the whole estate rather than a summary at the end.

Results

What this means for your project

The biggest saving here didn't come from moving data faster. It came from removing people from the loop. Manual archive migrations scale linearly with headcount and error rates rise with volume. An automated, distributed pipeline scales with agents, and the audit trail builds itself as it goes. If your Enterprise Vault exit is being planned on a spreadsheet, it's worth asking what the timeline looks like at full scale.

Related

How long would your
archive migration take?

Book a 30-minute scoping call with the engineers who built the engine. We'll map your sources, volumes and compliance constraints, and tell you honestly where we fit.

Request a scoping call →

No sales pitch · No commitment · A technical conversation with the engineers who built the engine