Migration path
Arctera EV Cloud to Mimecast Cloud Archive migration
EV Cloud → Mimecast
Moving an Arctera EV Cloud archive to Mimecast is a fully managed eMXport engagement. EV Cloud is a different product from on-premises Enterprise Vault. If you describe the project as an Arctera to Mimecast migration, we first confirm that EV Cloud is the source. We confirm the scope, access and export arrangements for your tenant before we schedule the work. Your team does not install migration software.
Arctera EV Cloud is the cloud-hosted archive. On-premises Enterprise Vault, including Veritas Enterprise Vault, is a different product.
- Fully managed delivery
- No customer-side install
- Architecture deployed for the job
- Agreed chain-of-custody reporting
What a EV Cloud to Mimecast migration involves
Source considerations — EV Cloud
We start with your tenant: the archive in scope, how we access it, and the export arrangements that apply to your organisation. Before we set a schedule, we confirm how the export will run and the access the move needs.
Destination considerations — Mimecast
The destination is Mimecast Cloud Archive. We prepare your EV Cloud data for the ingestion route agreed for your move, track jobs and exceptions against that scope, and confirm what Mimecast requires before delivery is scheduled.
Data and metadata
We compare the message data and metadata your EV Cloud export can provide with what the agreed Mimecast route can accept. Folders, labels, retention and holds are included only if we agree that work with you first. We document the mapping, anything left out, and how exceptions will be handled before delivery starts.
Validation and reporting
We close the migration against the scope agreed with you, and we hand over the chain-of-custody and outcome reporting named in that agreement.
How we run the migration
Confirm the scope
We agree the data in scope, source access, destination requirements, volume, timing and evidence needed at handover.
Design and deploy the route
We select the supported migration method and deploy the eMXport architecture needed for the job.
Run and manage the work
We operate the migration jobs, monitor progress and investigate exceptions. Your team gets clear updates without running the platform.
Reconcile and report
We close the engagement against the agreed scope and provide the chain-of-custody and outcome reporting defined during discovery.
What we need to price the migration
Start with what you know. We can refine the rest during discovery.
- Source and destination platforms
- Approximate data volume in terabytes
- Number of users, custodians or archives, where known
- Required timescale and any fixed cut-off date
- Retention, hold, legal or compliance constraints
- Reporting and sign-off requirements
Questions we hear a lot
- Do we need to install eMXport?
- No. We deploy and operate the eMXport architecture for the engagement. Your team provides the agreed access and decisions, not another platform to maintain.
- Can you preserve every folder, label, field and retention setting?
- That depends on what the source can export and the destination can accept. We map the supported data and metadata during discovery, then document the agreed scope.
- How long will the migration take?
- Volume is only one factor. Source performance, destination limits, data shape, access, exceptions and migration windows all matter. We estimate timing after discovery.
- Is Arctera EV Cloud the same product as Enterprise Vault?
- No. Arctera EV Cloud is the cloud-hosted archive. Enterprise Vault on this site means the on-premises product, including estates still described as Veritas Enterprise Vault. Discovery confirms which product is in scope before the route is designed.
- How do you set the migration schedule?
- We confirm the archive in scope and the export arrangements for your tenant, then build the schedule around that. Volume, access and how the export behaves in practice all shape the plan.
- Do retention policies and holds move into Mimecast?
- Only when that configuration work is part of the agreement. Retention and holds are set in each platform. Discovery confirms whether the engagement covers message data, separately agreed configuration, or both.
- What does our team have to operate?
- Access and decisions. eMXport runs the migration for the engagement, and there is no customer-side install.
Plan an Arctera EV Cloud export · On-premises Enterprise Vault is a different product · Learn about Mimecast Cloud Archive migrations