Cloud2Cloud Migrator moves personal archives, journal archives, shortcuts and public folder content out of Veritas Enterprise Vault and into Microsoft 365, directly and with every message accounted for. It works even when the archive is full of corruption that stops native tools.
Enterprise Vault (formerly Symantec, now Veritas) was built for the on-premises Exchange era. Once your mailboxes are in Microsoft 365, EV becomes an expensive dependency. You're paying for servers, storage, SQL and specialist skills to keep a system alive just so users can open old shortcuts and Legal can run searches.
Leaving it is harder than it looks. Three things make EV migrations notoriously difficult:
Corruption. In our experience, up to 80% of users have at least one corrupt message in their Enterprise Vault archive. Native export tools stop at the first error and leave the rest of the archive behind.
Shortcuts. Users' mailboxes are full of stubs pointing back to EV. If you migrate the archive naïvely, you either break those shortcuts or bring back years of email that users deliberately deleted.
Journal archives. Journals hold every message sent or received for compliance. They're often hundreds of millions of items in one archive, far beyond what single-threaded tools can extract in a reasonable time.
Native EV tools stop at the first corrupt item. Ours logs the corruption, skips that message and carries on, so the migration finishes. Every skipped item appears in the reconciliation report with a reason, so nothing goes missing silently.
When a user deletes an Enterprise Vault shortcut, they believe they've deleted the email. A full archive dump into Microsoft 365 brings all of those messages back, and suddenly users are wading through years of mail they thought was gone.
Shortcut rehydration is driven by what the user still has. We scan mailboxes and personal archives for EV shortcuts, resolve each one to its archived original, copy that message back into the same folder, and remove the stub cleanly. The user simply sees a normal email. It works in Microsoft 365, Exchange on-premises or hybrid.
Rehydration and full archive migration aren't mutually exclusive. Many programmes rehydrate live shortcuts into the mailbox and move the remaining archive to a Microsoft 365 online archive or a compliance hold. We help you choose the right exit strategy during scoping.
Journal archives are where most EV projects stall. We split extraction by day and run it across multiple agents in parallel. Every message is checkpointed, so an overnight failure resumes from the last successful item rather than starting again. There are no duplicates on restart and no re-scans.
You can add agents to go faster. Agents run in your data centre, in your cloud or in ours, wherever your data residency rules require.
NHS Wales moved Enterprise Vault archives for 180,000 mailboxes into NHSmail. Done by hand, the estimate was ten years. With extraction, transfer and placement automated end to end and distributed agents working in parallel, it took eighteen months. Read the NHS Wales case study →
Investec retired Enterprise Vault for 8,100 mailboxes on five continents by rehydrating only the shortcuts users still had, so deleted mail stayed deleted. Read the Investec case study →
When things have already gone wrong, the same engine recovers them. A Magic Circle law firm resolved EV shortcuts left in its document management system and PSTs by a competitor's failed upgrade.
Every action is logged: the source item, its destination, the timestamp, the agent and the result. Counts are reconciled between source and destination. The audit trail exports as signed CSV, JSON or PDF, which is the evidence Legal needs to sign off decommissioning and your auditor needs to close the finding.
Every estate is different, but most EV exits follow the same six stages. Knowing them up front makes it much easier to plan budgets, communications and the date you can finally switch EV off.
We start by profiling the whole estate: every archive, its owner, item count, size, date range and type (personal mailbox archive, journal, shared or public folder). Archives are matched against Active Directory, so archives belonging to leavers stand out immediately. This is usually where organisations discover they have far more orphaned archives than they thought.
Not every archive should go to the same place. A common pattern is:
It's also worth applying your retention schedule before you migrate. Moving items that are already past their retention date costs time and storage and adds risk for no benefit.
A pilot of a few dozen mailboxes, deliberately including some archives you know are problematic, tells you three things: real throughput in your environment, how corruption shows up in the reconciliation report, and how users react to rehydrated items in Outlook. Those numbers drive the plan for everything that follows.
Production waves run by department, region or business unit, and are scheduled around working hours. Microsoft 365 throttles how quickly data can be written into each mailbox, so speed comes from working on many mailboxes at once rather than pushing one mailbox harder. That's why our agents scale out: to go faster, you add agents.
Each wave closes with a reconciliation report: items in the source, items migrated, items skipped with the reason for each, and a duplicate count. Legal and compliance review the skipped items and sign off. Nothing is decommissioned on the strength of "it looked fine".
Keep EV running read-only until the final wave is signed off. Then remove the EV Outlook add-in, clear any remaining shortcut leftovers, and retire the servers, storage and SQL databases. Keep the exported audit trail with your project records. It's the evidence that the data was moved completely.
Take an illustrative wave covering a legal team's personal archives, like the one shown on our How it works page. The source held 412,847 messages. 412,822 were migrated, 25 were skipped and there were no duplicates: a 99.994% success rate.
The headline number matters less than the 25. Each skipped item is listed with its archive, its source identifier and a reason, such as a corrupt header. Legal can then decide, item by item, whether it needs action. That might mean recovering it from a backup, recording it as unrecoverable, or accepting it because it falls outside any hold. With a native export, those 25 items would typically have stopped the job, and you might never have known what was left behind.
Yes. Data moves straight from the Enterprise Vault stores into Microsoft 365 mailboxes or online archives in one orchestrated pass. Skipping the PST step halves the data handling and removes a whole copy of your archive from the breach surface.
Corrupt items are logged, skipped and reported with a reason, and the migration keeps going. Native tools typically stop at the first error. In our experience up to 80% of users have at least one corrupt message, so this matters on almost every project.
No. Shortcut rehydration replaces each live shortcut with the original message in the same folder and removes the stub. Messages users had already deleted stay deleted.
Yes. Journal archives are extracted with multi-threaded, day-based parallelism across distributed agents, and checkpointed per message. You can add agents to increase throughput on very large journals.
It depends on volume, the number of agents you can deploy, the destination's throttling limits and how much corruption is in the source. We scope it properly before giving a timeline. Book a scoping call and we'll give you an honest estimate.
Data moves directly from source to destination. Agents and the audit store can run on your own infrastructure, so data needn't leave your jurisdiction unless the destination itself is cross-border.
It depends on data volume, the number of archives, the level of corruption and Microsoft 365 throttling. We give an estimate after discovery and confirm it with real throughput figures from a pilot wave. Adding agents increases throughput.
Yes. Migration runs in the background and waves can be scheduled outside working hours. Users don't need to do anything, and rehydrated shortcuts simply appear as normal emails.
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