Enterprise Vault On-Premises: Keep, Upgrade or Migrate?
Updated: 13 hours ago
Arctera announced a focused SaaS operating model on 5 May 2026. The same announcement says that customers requiring on-premises support will continue to be served through a dedicated organisation.
For Enterprise Vault customers, this creates a useful roadmap discussion. The right decision still depends on the archive and the business using it.
Keeping, upgrading and migrating each deserve a fair assessment. None of them is automatically the safe choice, and none of them should be chosen only because a vendor announcement appeared.
Start with the facts about your archive
Before comparing options, collect the same baseline for every one of them:
Archive volume, growth rate and the number of archived mailboxes, file shares or journal targets
Current Enterprise Vault version, its supporting Windows, SQL and storage versions, and maintenance status
Retention categories, legal holds and the teams who rely on search and export
Known issues: ingestion backlogs, index problems, slow retrieval, capacity limits
Contracts and renewal dates for the software and the underlying infrastructure
Without that baseline, each option tends to be judged by the enthusiasm of whoever is proposing it.
Keep a healthy environment deliberately
Maintaining the existing estate can make sense when it meets requirements and remains supportable.
Assess ingestion, indexing, retrieval, capacity and recovery. Review the supporting Exchange, Windows, SQL and storage components as well as Enterprise Vault itself.
If the recommendation is to stay, define the maintenance work, support arrangement and planning horizon. "Keep" should be an active operating decision with a budget and owners.
Confirm how on-premises support will be delivered to you under the vendor's new structure, and record the contacts and escalation route. Revisit the decision at a fixed point, such as the next renewal.
Upgrade where dependencies require it
A planned messaging or infrastructure change may require a newer archive version. Other upgrades may address a supportability gap or enable a needed capability.
Map the supported path and prerequisites using Arctera's current compatibility charts. Include accelerator products, database changes and post-upgrade testing where relevant.
Estimate the complete project, including preparation, maintenance windows and validation. A version change should produce a supported, usable environment rather than just a successful installer result.
Migrate against defined requirements
Migration can be appropriate when the future operating model, user experience or governance requirements justify it.
Identify what must move, which metadata and retention controls need preserving, and how held content will be treated. Validate search, export, access and ongoing capture in the destination.
Include extraction effort, transfer time, reconciliation and parallel operation in the cost comparison. Account for the support needed while the source remains available.
Compare the options side by side
Main effort: Keep: Ongoing maintenance and support. Upgrade: A planned project with testing. Migrate: Extraction, transfer, reconciliation.
Main risk: Keep: Drifting out of support. Upgrade: Dependency and compatibility gaps. Migrate: Lost metadata or broken holds.
Users notice: Keep: Little change. Upgrade: Short maintenance windows. Migrate: New search and retrieval experience.
Decide by: Keep: Health check and support terms. Upgrade: Compatibility and prerequisites. Migrate: Target requirements and pilot results.
Include data location and governance
For GCC organisations, review the approved data location and access arrangements for each option. The legal and compliance teams should define the requirements that the technical design must satisfy.
This matters most for migration to a hosted service, but it also applies to upgrades that change where backups, indexes or administrative access sit.
Virtech offers Enterprise Vault assessments, upgrades and archive migration services. Our Health & Roadmap Review can compare the options against the customer's actual estate, producing a prioritised recommendation. Learn more about our Enterprise Vault services.
Ask Virtech for a keep, upgrade or migrate assessment before your next archive investment.
Email sales@virtech.ae or call +971 4 580 7555 to speak with our specialists.
Frequently asked questions
Does the SaaS announcement mean Enterprise Vault on-premises is ending?
The announcement says on-premises customers will continue to be served through a dedicated organisation. Confirm your own support terms and roadmap with the vendor rather than relying on assumptions.
How long does an assessment take?
It depends on the size and complexity of the estate. Most of the effort goes into collecting the baseline data and interviewing the teams who use the archive.
Can we upgrade now and migrate later?
Yes. An upgrade can restore supportability while a migration is planned properly. Make sure the upgrade decision accounts for the expected migration timeline.
Comments