Enterprise Vault Migration
Maximizing Office 365 Licenses?
With many organizations moving to cloud solutions like Office 365, the overhead of maintaining legacy archives such as Enterprise Vault begins to look less and less appealing – there are simply better and more efficient options to manage your data. On top of that, costs to maintain Enterprise Vault are significant including storage maintenance, hardware / software upgrades, archive license renewal, and resources to manage the environment.
Migrating this data to a modern cloud-based solution allows you to reduce your CAPEX expenditure and leverage a more modern platform that allows cohesive data governance across all your workloads.
Many organizations migrating legacy archives like Enterprise Vault to Office 365 are simply taking advantage of the licenses they are already paying for. There are real advantages to this strategy in terms of maximizing the overall end user experience along with a compelling Return on Investment (ROI) typically between 6 – 12 months!
When faced with the prospect of migrating Enterprise Vault, some organizations will opt to investigate the possibility of manually using available toolsets. What’s often overlooked is that there are many steps involved, all of which need to be coordinated to ensure an adequate outcome.
For example, data needs to be extracted and staged, copied to Azure, appropriate online archives may need to be enabled, and then data needs be ingested into O365 using a mapping file. Any mistakes in this mapping file will result in data being migrated into the wrong target mailbox. Additionally, if failures or corruption occurs, you will need to re-export and import the data.
Audit records of a migration are important to ensure your migration process has met the goals of the project. The toolsets available for a manual migration do not have the capability to ensure a full end-to-end Chain of Custody for your data. Items are not tracked individually, and you cannot be certain an item that was extracted from your archive hasn’t been tampered with prior to ingestion into Office 365.
- Who has been migrated and when?
- What was the status of each step?
- What failures occurred and why?
Manual processes typically rely on updating spreadsheets and a massive set of PowerShell logs. Human error will certainly crop-up during the process, which leads to a subpar outcome and risk.
Scaling for Speed?
With the enforcement of Microsoft’s Service Protection Throttling in late 2020, each mailbox will have limits which affect how much data may be migrated within a 5-minute interval. In order to achieve adequate velocity to meet project timelines, customers are now forced to migrate many more users at the same time.
There is simply no other way to around this limitation which leads to juggling multiple times the amount of scripts, logs and user communications. Scaling manual migration processes drastically increases the probability for human error, governance issues, and unsatisfactory results for your organization.
Related Cloudficient Blog Posts
In a previous blog, we discussed why you should migrate your legacy archives at the same time you plan to onboard your users to Office 365. While...
In this video Steve takes us through some of the details around the three different generations of archive migration solutions. He'll cover:
The technology industry has spearheaded changes across every field in the past few years. Yet, when it comes to pricing, many still cling to...
How Migration Timelines might Triple (At Least)
Last December our team encountered a strange new behavior in our Office 365 onboarding projects.