How to migrate Enterprise Vault to Office 365 (Microsoft 365)?

Enterprise Vault to Office 365 migration

Migrate emails from Enterprise Vault to O365 step-by-step

EdbMails software for Enterprise Vault migration

Veritas Enterprise Vault is an enterprise information archive platform that has been around for a decade and specializes in archiving Microsoft Exchange, SharePoint, files, and emails. When it was first developed, it provided much-needed relief to many organizations looking to archive their data for eDiscovery, legal, and compliance reasons. However, as time passed and newer technologies and solutions emerged, Enterprise Vault appears to be an add-on function to the existing ones, particularly when there is a need to have everything under one roof. For instance, businesses that use Microsoft 365 for their email communication platform see Enterprise Vault as somewhat obsolete now that Office 365 provides better off-the-shelf Archive and eDiscovery capabilities. Enterprise Vault archives are stored on-premises or must be uploaded to AWS or Azure for security, which may be an additional task. EdbMails is a Microsoft partnered software that can help you to import PST to Office 365. By using the application, you can directly migrate the archives exported as PST from Enterprise Vault to Office 365 in a few clicks. In this article, we explain the pre and post migration steps including the migration to Office 365.

Reasons for Office 365 migration from Enterprise Vault

Though newer versions of Enterprise Vault are being released, it appears to be an additional burden when it comes to paying for license maintenance and upkeep.
Enterprise Vault being an on-prem solution does not directly allow individual users to access their archive data the control remains with the IT Team.
Exporting and managing archives must be done separately in Enterprise Vault, whereas in Office 365, everything is accessible through a single login.
Office 365 combines a plethora of collaboration tools and features, as well as email and archives, making it extremely popular among small and large businesses.
If users have already moved to Exchange online, it is extremely difficult for them to retain archives with Enterprise Vault if they do not wish to pay.

QUICK LINKS

Email Migration to Zoho Mail from Office 365 ProtonMail to Office 365 Migration cPanel to Office 365 Migration Transfer Comcast Emails to Office 365 Migrate Plesk IMAP mailboxes to Microsoft 365 Migrating from Barracuda Email Archiver to O365 Migrate AWS workmail to google workspace

Enterprise Vault to Office 365 migration

User Query

"We have Enterprise Vault archives that we would like to transfer to Office 365. Is there a suitable method we can use to easily migrate them to Office 365? We were unable to find a step-by-step instruction while searching for online solutions. Could you please point us in the right direction? Thank you for any suggestions."

Pre migration activities for Enterprise Vault to Office 365 migration

Make sure you have admin access on the target server
The admin account that has all the necessary permissions to migrate mailboxes on behalf of all the users in your organization. Assign the Organization Management role group and impersonation rights to the admin user on Office 365.
Create Office 365 mailboxes and assign licenses to them
Add users and assign licenses to Office 365 users
Assign Microsoft 365 licenses to user accounts
If you plan to migrate the Google Vault archive to Office 365 Public folders, ensure that you create and configure the Public folder mailboxes on the target server.
Create Office 365 Public folder and assign mailbox user
Similarly, if you want to migrate to the Office 365 In-Place archive, enable them from the admin center.
Steps to enable archive mailbox in Microsoft 365.
If you have a custom email domain from the source which you want to retain and receive emails to, you must add and verify the domain on Office 365.
Steps to add a custom domain to Office 365 and Steps to add DNS records to connect your domain.
Configure Office 365 to send and receive large messages.
Follow the steps to increase the message size on Office 365 to 150MB. See message size limits on Office 365 for more information.

How to migrate from Enterprise Vault to Office 365?

You can perform the migration with the following three methods.

Migrate Enterprise Vault to Office 365 with Azure AzCopy
Migrate the PST file from Google Vault to Office 365 with EdbMails

Migrating from Enterprise Vault to Office 365 is possible by exporting the PST files from the Export Archive Wizard in Enterprise Vault and then uploading the PST files to Microsoft 365 with Azure AzCopy tool. The second approach is to use EdbMails to migrate the PST file to Office 365. Let's go over the procedure step by step by using both the methods.

Steps to migrate Enterprise Vault to Office 365 with Azure AzCopy

Step 1: Login as an administrator and open the Enterprise Vault admin console
Step 2: Right click on the Archives and select Export to open the Export Wizard
Step 3: Select 'Export archives to PST files' and filter the archive based on the name
Step 4: Select the archive and choose to export all of them or based on the date range
Step 5: Browse the folder path on your computer to save the archive as a PST file
Step 6: Use Azure AzCopy to import the PST to Office 365 by using the network upload

The limitation of this method is that it can be slow to import your data with the network upload, and it requires technical knowledge to create a mapping file and manage the entire migration from start to finish.

Steps to migrate Enterprise Vault to Office 365 with EdbMails

EdbMails PST to Office 365 migration is a graphical interface tool that can help you transfer the exported PST file from Enterprise Vault to O365 directly. An advantage of EdbMails is that you can migrate the exported PST file directly to Office 365 Archive and Shared mailboxes with a direct one-one mapping. It also provides the facility to map your folders, filter data based on specific criteria and facilitates incremental migration.

Step 1: Download and install EdbMails Exchange server migration software
- Download EdbMails and install the application on any computer that is connected to the source and target environment. You can also perform the migration operation by installing EdbMails on a non-Exchange computer.
  See a detailed list of EdbMails system requirements for IMAP migration.
- Launch the application and click 'Login' or 'Start Your Free Trial'
  Login to the application (if you have purchased a license and already have the username and password). The free trial version allows you to migrate 30 items from every folder of the source account to the target.
- Select the migration technique as 'PST Recovery and migration' in the main window
Step 2: Select the PST file in EdbMails that you exported from Enterprise Vault
EdbMails has a user-friendly and intuitive graphical interface that helps you complete the migration in a few clicks. Click 'Browse the PST' and navigate to the file location where you previously saved it.
Step 3: Select the mailboxes and connect to the Office 365 tenant
- Select the mailboxes and folders from the left panel to migrate.
- Click 'Migrate to Office 365' to set up the connection with the target server.
EdbMails provides the following additional options to help you customize the migration task.
- Additional Include and Exclude Filter Options
- Filter emails by Date: Migrate to Office 365 by applying the Date filter
- Filter emails by Size: Exclude emails from migration larger than a specified size.
Step 4: Connect to target Office 365 as Global Admin User
EdbMails supports both modern and classic authentication. Connect to the target server by selecting Auto or Manual registration for modern authentication and the connection method as Mailboxes, Public folder or Archive Mailbox. You can also connect to the mailboxes by loading a CSV file of users from the Office 365 tenant.
Connect to Office 365 server using secure modern authentication
Step 5: Map the mailboxes and migrate PST to Office 365
Map the mailboxes and start the migration from Google Vault Archive to Office 365. Finally, verify the count of migrated emails, folders and mailbox items with EdbMails text-based log report. You can also pause and resume the migration.
If you require further assistance, contact EdbMails 24x7 support. Try the free trial version today to start the migration! See steps to import PST to Office 365 with EdbMails.

III. Post-migration tasks

Step 1: Update the MX records to point to Office 365
If you have not done this step previously, change the DNS records known as MX records to enable and receive email messages on the target Office 365 server by keeping the same domain name (yourname@domain.com) from the source server. In addition to this setup, configure the Autodiscover record to allow Outlook to connect to the migrated mailboxes.
Step 2: Create a new Outlook profile for users in the new domain
Remove any previous instances of Rackspace account on Outlook to avoid conflicts with the new server. Configure and recreate the Outlook profile for each user in your domain if it has problems connecting to Office 365 mailboxes.
Step 3: Decommission or delete the user mailboxes on Rackspace server
Configure and recreate the Outlook profile for each user in your domain if Outlook has problems connecting to Office 365 mailboxes.

Migration troubleshooting

See the migration troubleshooting guide for possible solutions related to common errors. For more information on EdbMails Office 365 and PST migration, see frequently asked questions (FAQs)

Concluding Thoughts

Migrating archives from vault solutions such as Google Vault and Enterprise Vault may appear to be a difficult task given the lack of popular tools or methods for directly transferring an archive to Microsoft 365. One approach is to first export your Enterprise Vault archives to PST and then migrate to Office 365 by using the network upload. Alternatively, you can migrate the PST to Office 365 directly using EdbMails, a Microsoft partner tool that completes the operation in a couple of steps with complete data consistency.

Free Download

Buy Now