Enterprise Vault Migration Checklist: 15 Questions to Answer Before You Start
Migrating years of archived email and enterprise records is rarely as simple as moving data from one platform to another.
For organizations running Arctera Veritas Enterprise Vault (EV), the real challenge is understanding exactly what exists in the archive, how that information is stored, which records must remain accessible, and what needs to happen before the existing environment can be retired.
An Enterprise Vault environment may contain millions or billions of archived items, multiple Vault Stores, mailbox archives, journal records, legacy storage dependencies, and retention policies established years earlier. Some organizations are moving to Microsoft 365. Others are consolidating archive platforms, replacing aging infrastructure, or preparing to exit a data center.
Whatever the destination, a successful Enterprise Vault migration starts with an accurate understanding of the source environment and a clearly defined migration strategy.
This Enterprise Vault migration checklist covers 15 questions IT, infrastructure, messaging, and compliance teams should answer before committing to a migration approach.
Why Enterprise Vault Migration Planning Matters
Enterprise Vault often becomes deeply embedded in an organization's infrastructure over time.
What began as a straightforward email archiving system may now support regulatory retention, legal discovery, former employee records, historical journal data, and storage platforms that are approaching retirement.
Migrating this information without adequate preparation can create serious operational challenges:
Archived messages may not appear where users expect them.
Mailbox shortcuts may no longer resolve correctly.
Journal data may not be searchable in the required way.
Metadata and retention requirements may not map directly to the destination.
Legacy storage can restrict extraction performance.
Large item counts can make migration take considerably longer than expected.
Unresolved migration exceptions can delay the retirement of Enterprise Vault.
The goal is not simply to move archived items. It is to ensure the destination can support the organization's requirements and that the migration can be verified before the source environment is decommissioned.
Enterprise Vault Migration Checklist: The 15 Questions
1. Which Enterprise Vault Version Is Currently Running?
The first question is also one of the most important.
Before selecting migration software or planning a timeline, establish the exact Enterprise Vault version, build, and environment configuration.
Older Enterprise Vault deployments may introduce compatibility considerations, unsupported components, or additional preparation requirements.
Your assessment should identify:
Enterprise Vault version and build
Number of Enterprise Vault servers
Server operating systems
SQL Server configuration
Directory and site structure
Current software support status
Dependencies on Exchange, Domino, or other applications
Why it matters: Migration capabilities and supported methods can vary by source version. Establishing compatibility early reduces the risk of discovering limitations after the project has started.
2. How Much Archive Data Needs to Be Migrated?
A migration estimate based solely on terabytes can be misleading.
Two Enterprise Vault environments containing the same amount of data may require very different migration times.
For example, an archive containing millions of small email messages can create more processing overhead than an archive containing fewer, larger items.
Before migration, establish:
Total archive capacity
Number of archived items
Average item size
Largest archives
Historical growth
Archive age and distribution
Any data excluded from the migration scope
It is also important to distinguish logical archive size from the physical storage consumed by the Enterprise Vault environment.
Storage-level compression, sharing, or other platform characteristics can make those figures different.
Why it matters: A realistic migration plan needs both volume and item-count information to estimate processing requirements and identify potential bottlenecks.
3. How Many Vault Stores, Partitions, and Archives Exist?
Enterprise Vault data may be distributed across several Vault Stores and storage partitions.
These components may have different performance characteristics, archive populations, and storage dependencies.
The migration assessment should document:
Number of Vault Stores
Number of partitions
Active and inactive partitions
Archive counts per Vault Store
Archive ownership and associations
Storage locations
Any known access or integrity issues
This inventory helps determine how migration work should be organized.
A large Enterprise Vault estate may benefit from a phased approach based on archive groups, source locations, or business requirements rather than attempting to process everything simultaneously.
Why it matters: Understanding the environment's structure allows migration work to be planned around actual source conditions rather than treating the entire estate as one uniform repository.
4. What Types of Enterprise Vault Archives Are Included?
Not all Enterprise Vault archives serve the same purpose.
An organization may have several archive types, each requiring different planning considerations.
Common examples include:
Exchange Mailbox Archives
Historical email associated with individual users.
Exchange Journal Archives
Centralized records of communications, often maintained for compliance, supervision, or legal requirements.
Domino Archives
Mailbox or journal content associated with Domino environments.
File System Archiving (FSA)
Archived files originating from file servers and other supported file-system locations.
Shared and Other Archives
Archive types associated with shared information or specific applications.
Each archive type should be identified before migration.
The destination and migration method must be evaluated against the actual content and requirements of each archive population.
Why it matters: A migration approach suitable for individual mailbox archives may not be appropriate for journal data or File System Archiving.
5. Where Is the Enterprise Vault Data Physically Stored?
Enterprise Vault frequently relies on underlying storage infrastructure that may be as old as the archive deployment itself.
Depending on the environment, archived content may reside on:
EMC Centera
Dell ECS CAS
NAS platforms
File-based storage
Other supported legacy storage environments
The underlying storage can affect source access, throughput, operational dependencies, and the wider retirement strategy.
For example, an organization retiring EMC Centera may also need to migrate Enterprise Vault archives that depend on it.
This introduces two related but distinct considerations: moving the archived information into its intended destination and addressing the storage infrastructure that supports the existing environment.
Why it matters: Understanding the archive and storage layers together helps prevent an application migration from leaving unresolved infrastructure dependencies behind.
6. Are Journal Archives Part of the Migration?
Journal archives deserve their own assessment.
Unlike standard mailbox archives, journal archives may contain centralized records of communications across an organization.
They can be important for:
Regulatory compliance
Legal discovery
Internal investigations
Communications supervision
Historical recordkeeping
Retention obligations
The migration team should establish which journal archives are included, what information must accompany the messages, and how those records will be accessed in the destination.
Particular attention should be given to message recipients, historical context, metadata, retention requirements, and searchability.
For organizations moving to Microsoft 365, journal migration needs to be designed around the target's supported compliance and discovery capabilities rather than assuming a traditional journal archive can be recreated in exactly the same form.
Why it matters: Journal records may remain technically present after migration but fail to meet business or compliance expectations if the target design is not established first.
7. What Happens to Enterprise Vault Mailbox Shortcuts?
Mailbox shortcuts are one of the most visible Enterprise Vault migration challenges.
Enterprise Vault can replace archived messages in user mailboxes with shortcuts that reference the archived content.
When the archive moves, those shortcuts need to be considered.
Depending on the migration strategy, organizations may need to:
Rehydrate archived messages
Replace shortcuts with original content
Preserve expected mailbox folder organization
Account for deleted or modified shortcuts
Avoid introducing unwanted duplicate messages
Confirm the user experience after migration
Shortcut handling should be tested with representative users before production migration begins.
This is especially important for environments where users have relied on Enterprise Vault shortcuts for many years.
Why it matters: A migration can complete technically while still creating a poor user
experience if historical messages become difficult to locate or shortcuts no longer function as expected.
8. Which Retention Policies and Legal Holds Apply?
Enterprise Vault archives may contain information governed by different retention categories, regulatory obligations, or legal-hold requirements.
Before migration, organizations should determine:
Which retention categories exist
Which archives are subject to legal hold
Whether retention periods differ by department or archive
Which records must remain immutable
How retention requirements will be implemented in the target
Whether any data can legitimately be excluded
Who is authorized to approve the migration scope
Retention behavior should never be assumed to transfer automatically between different archive platforms.
The source and target may represent retention policies differently.
A documented mapping exercise is often necessary to establish how the destination will satisfy the organization's requirements.
Why it matters: Moving the data without an approved retention strategy can create governance and compliance problems long after the technical migration has finished.
9. What Is the Destination for the Archived Data?
The destination determines much of the migration architecture.
Common Enterprise Vault migration targets include:
Microsoft 365
Exchange Online
Proofpoint
Another supported enterprise archive
A modernized archive environment
Other approved platforms, depending on the data and use case
The destination should be selected based on how the archived information needs to function after migration.
For example, an organization moving mailbox archives to Microsoft 365 may prioritize user access and Outlook integration.
An organization migrating compliance archives may place greater emphasis on retention, discovery, supervision, and audit requirements.
Questions to resolve include:
Where will migrated content be stored?
Who needs access?
How will users find historical messages?
How will compliance teams search records?
Which metadata must be available?
What licensing or capacity requirements apply?
What target ingestion limitations exist?
Why it matters: A technically compatible destination is not necessarily an operationally suitable one. The target must meet the actual requirements of the organization.
10. Do We Need Enterprise Vault Migration or Just Extraction?
Not every organization needs a complete source-to-target migration.
Some organizations simply need to retrieve archived items from Enterprise Vault in a portable output format.
This is an important distinction.
Enterprise Vault Migration involves moving archive data into a destination environment, including the relevant target ingestion process.
Enterprise Vault Extraction, as a separate Interlock service, involves extracting supported archived items into EML or other output formats enabled by the applicable license, without target-platform ingestion.
Interlock's defined EV Extraction scope covers:
Exchange mailbox archives
Exchange journal archives
Domino mailbox archives
Domino journal archives
Extraction does not include moving data between Enterprise Vault Vault Stores, partitions, or storage devices, or ingesting it into Microsoft 365, another archive, mail system, or storage platform.
An organization preparing to retire Enterprise Vault may need extraction, migration, or separately scoped elements of both.
Why it matters: Establishing the correct requirement prevents organizations from purchasing or planning a full migration when the immediate need is only to obtain archive data in a defined output format.
11. How Will Data Integrity and Migration Accuracy Be Verified?
Migration success should be measurable.
A simple count of completed items is useful, but it may not provide enough evidence for complex enterprise archive projects.
Before migration begins, define how the project will verify that the expected content has been transferred correctly.
Validation requirements may include:
Source and target item counts
Successful and failed item reporting
Metadata checks
Attachment verification
Exception reporting
Retry tracking
Content integrity verification
Representative target-access testing
Final reconciliation
Where supported by the migration workflow, source-to-target cryptographic hash validation can provide additional integrity evidence.
Interlock's wider enterprise migration technology includes SHA256-based validation for applicable migration workflows. However, the exact validation method for an Enterprise Vault project should be confirmed against the selected migration software, source, and destination.
Why it matters: Organizations need evidence that the migration achieved its defined scope, particularly before retiring a system that has stored critical records for years.
12. How Will Migration Throughput and Project Duration Be Estimated?
Large Enterprise Vault migrations should be planned using measured performance rather than assumptions.
Several factors influence migration speed:
Source archive performance
Number of archived items
Average item size
Storage read performance
Network capacity
Migration software configuration
Destination ingestion limits
API restrictions and throttling
Validation requirements
Available processing windows
A pilot migration can help establish realistic throughput under representative conditions.
The results should then inform the production schedule, resource allocation, and migration-wave design.
For example, a migration deadline may require several processing streams, but increasing concurrency is not always beneficial if the source storage or destination platform becomes the limiting factor.
Why it matters: Throughput testing helps organizations create achievable project schedules and identify capacity constraints before they become critical.
13. What Will Users and Business Teams Experience During Migration?
Migration planning should consider operational impact as well as technical execution.
Some users may continue working while their archives are migrated. Others may need communications about historical content, mailbox changes, or temporary access limitations.
A user-impact plan should address:
Whether archived content remains accessible during migration
How shortcuts will be handled
Whether users need to take action
Changes to Outlook or archive access
Communication before and after migration
Support procedures
Escalation routes
Cutover and stabilization arrangements
Compliance and legal teams may also need to understand how archive searches or information requests will be handled during the transition.
Why it matters: A well-managed migration minimizes disruption and ensures the people who rely on archived information understand what is changing.
14. Have We Tested the Migration With a Representative Pilot?
A pilot should be treated as an essential validation stage, not merely a demonstration that the migration tool can move a few messages.
The pilot population should reflect the actual complexity of the Enterprise Vault environment.
Consider including:
Active employee archives
Former employee archives
Large mailbox archives
High-item-count archives
Journal archives
Different retention categories
Archives on different storage platforms
Messages with attachments
Representative shortcut configurations
Known problematic items
The pilot should answer practical questions.
Does the content arrive where expected? Can users access it? Are required metadata fields available? Can compliance teams search the records? Are exceptions reported clearly? Is throughput sufficient?
Pilot results should be documented and reviewed before approving full production migration.
Why it matters: A representative pilot exposes technical and operational issues while there is still time to adjust the migration approach.
15. What Must Be Completed Before Enterprise Vault Can Be Decommissioned?
Completing the migration workload does not automatically mean the Enterprise Vault environment is ready to be switched off.
A formal decommissioning decision should be based on agreed acceptance criteria.
Before retiring the source environment, confirm:
All in-scope archives have been processed.
Migration results have been reconciled.
Outstanding exceptions have been reviewed and resolved or formally accepted.
Required data is accessible in the destination.
Compliance and legal requirements have been verified.
User acceptance testing is complete where required.
Relevant stakeholders have approved the outcome.
Required migration evidence has been retained.
Archive and storage dependencies have been assessed.
Decommissioning activities have been separately planned and authorized.
The organization should also establish whether any archive populations are intentionally remaining in Enterprise Vault.
Why it matters: Prematurely retiring the source system can turn manageable migration exceptions into difficult or irreversible recovery problems.
A Practical Enterprise Vault Migration Readiness Checklist
Before starting production migration, your organization should be able to answer the following:
Readiness area | What should be confirmed |
Source environment | EV version, servers, Vault Stores, partitions |
Data inventory | Total volume, item count, archive populations |
Archive types | Mailbox, journal, Domino, FSA and other in-scope data |
Legacy storage | Centera, ECS CAS, NAS or other dependencies |
Destination | Target platform, licensing and access requirements |
Shortcuts | Rehydration or alternative handling strategy |
Compliance | Retention, legal holds, metadata and discovery |
Migration method | Supported tooling, workflow and target ingestion |
Performance | Pilot throughput and production capacity |
Validation | Integrity checks, reporting and reconciliation |
User impact | Communications, access and support arrangements |
Cutover | Migration waves, change control and contingency planning |
Completion | Acceptance criteria and formal sign-off |
If several of these areas remain unresolved, additional assessment is usually more valuable than immediately starting production migration.
Enterprise Vault Migration to Microsoft 365: Additional Considerations
Microsoft 365 is a common destination for organizations modernizing Enterprise Vault, but it introduces its own requirements.
In addition to the 15 questions above, organizations should review mailbox licensing, target archive configuration, ingestion performance, journal handling, retention policies, and Microsoft Purview requirements.
One important technical consideration is Microsoft's retirement of Exchange Web Services (EWS) in Exchange Online.
Microsoft began its phased EWS disablement in October 2026 and plans to complete retirement in April 2027.
Organizations should therefore verify whether their migration software depends on EWS and whether the relevant workflows support Microsoft Graph or another currently supported method.
This is particularly important for long-running projects that may continue into 2027.
Migration tools, target permissions, and API requirements should be validated against current Microsoft guidance before implementation.
Common Enterprise Vault Migration Mistakes to Avoid
Even experienced infrastructure teams can underestimate the complexity of legacy archive environments.
Estimating Only by Terabytes
Archive item counts, storage performance, and target ingestion limits can significantly affect the schedule.
Treating Journal Archives Like Mailbox Archives
Journal data may have different compliance and discovery requirements.
Ignoring Underlying Storage
Legacy Centera, ECS CAS, or NAS dependencies may affect the migration approach and retirement plan.
Assuming Retention Policies Transfer Automatically
Different archive platforms may use different retention and governance models.
Leaving Shortcut Decisions Until Cutover
Shortcut handling can directly affect user access to historical messages.
Running an Unrepresentative Pilot
A pilot using only a few uncomplicated mailboxes may fail to reveal problems affecting larger or more complex archive populations.
Decommissioning Before Reconciliation
Source retirement should follow documented validation and stakeholder acceptance.
How Interlock Technology Supports Enterprise Vault Migration
Interlock Technology works with organizations managing complex enterprise archive and data migration requirements.
Our experience spans Enterprise Vault, legacy archive storage, CAS, NAS, Object Storage, S3, and broader enterprise data modernization.
For Enterprise Vault projects, the priority is understanding the source environment, defining the required outcome, and selecting an approach appropriate to the archive and destination.
Interlock can help organizations assess:
Enterprise Vault archive configuration and data volume
Legacy storage dependencies
Mailbox and journal archive requirements
Migration versus extraction requirements
Target-platform considerations
Migration throughput and project constraints
Data integrity and reporting requirements
Archive retirement dependencies
Whether the project involves Microsoft 365, another archive platform, or a separately scoped extraction requirement, the starting point should be a clear technical assessment.
Frequently Asked Questions About Enterprise Vault Migration
What is the best way to migrate Enterprise Vault?
The appropriate method depends on the Enterprise Vault version, archive types, data volume, destination, and compliance requirements. A source assessment and representative pilot should be completed before selecting the production migration approach.
Can Enterprise Vault be migrated to Microsoft 365?
Yes. Enterprise Vault mailbox and other supported archive content can be migrated to Microsoft 365 using appropriate migration technology. Journal archives, shortcuts, retention, and target configuration require additional planning.
How long does an Enterprise Vault migration take?
Migration duration depends on archive size, item count, source performance, network capacity, target ingestion limits, and validation requirements. A pilot provides a more reliable estimate than storage volume alone.
What happens to Enterprise Vault shortcuts after migration?
Shortcut handling depends on the migration method and target. Some workflows support shortcut rehydration or synchronization. The required behavior should be defined and tested before production migration.
Can Enterprise Vault journal archives be migrated?
Yes, with suitable tooling and a supported destination. Journal migration requires specific attention to compliance, recipient information, metadata, and target discovery capabilities.
Can Enterprise Vault data stored on EMC Centera be migrated?
Yes. Enterprise Vault environments backed by EMC Centera can be assessed for archive migration. The application and underlying storage dependencies should be considered together.
Is Enterprise Vault Extraction the same as migration?
No. Extraction produces archived items in supported output formats without target ingestion. Migration includes moving archive data into a destination platform.
Can Enterprise Vault be decommissioned immediately after migration?
Not necessarily. The organization should first complete reconciliation, exception review, target validation, compliance checks, and formal acceptance.
Planning an Enterprise Vault Migration? Start With the Right Questions.
Enterprise Vault environments often contain years of business-critical information, and every migration introduces technical, operational, and compliance decisions.
A well-defined migration plan should establish what needs to move, where it needs to go, how it will be validated, and what must happen before the existing environment can be retired.
Interlock Technology helps organizations assess complex Enterprise Vault environments and plan enterprise archive migrations around their actual infrastructure, data, and business requirements.
Discuss Your Enterprise Vault Migration Project
Tell us about your current Enterprise Vault environment, the intended destination, and any known archive volume or project deadlines. Our team can help review the requirements and identify the appropriate next steps.
Comments