Transvault is the go-to solution for migrating Commvault users, leavers and journal archives into a range of on-premises and cloud-based destinations, including Microsoft Office 365.
Transvault migrations from Commvault start with a deep dive into the Commvault archive data to establish its exact contents. This initial analysis enables your organisation to create a baseline from which you can check that emails, metadata and attachments have been successfully migrated.
Start your migration to Commvault with Transvault
Transvault has pioneered the migration market space and has produced a benchmark whereby all migration companies are measured.
Migrating from Commvault
Commvault is the latest archiving platform to be added to Transvault’s extensive list of email archiving solutions. Our Commvault migrations utilise a direct connector via the Commvault REST (Representative State Transfer) API.
All data movement is fully audited to ensure chain-of-custody when moving from Commvault. Mailbox shortcuts are fully managed to ensure a seamless experience for end-users as they move.
To extend the seamless user experience, Transvault also provides a comprehensive shortcut management service. As your data is moved, the corresponding shortcut is converted to point to the new archive. This activity can take place whilst users are online, so there’s no need for any downtime or for users to logout.
Here are just some of the platforms we support for Commvault migrations:
- Commvault to Microsoft Office 365 migration
- Commvault to Enterprise Vault migration
- Commvault to Exchange migration
- Commvault to Google migration
- Commvault to PST migration
Commvault to Microsoft Office 365 Migrations
If your plan is to move your organisations archive from on-premises Commvault to Microsoft’s Cloud, then Transvault is the solution for you.
As with all Transvault migrations, we ensure full chain-of-custody throughout the migration from Commvault to Microsoft Office 365. Alternative solutions will first restore your compliance emails to PST before migrating to Commvault, this will potentially create additional problems for your migration project. Transvault’s direct, end-to-end, transactional transfers involves no interim storage and no interim file formats, ensuring your mailboxes and journal data is not only discoverable when it comes to eDiscovery, but more importantly defensible.
Transvault is also able to migrate your legacy journal format into the new compliance model that has been introduced with Microsoft Office 365, ensuring all your data is intact, fully discoverable and stored in accordance with Microsoft’s licencing policies.
Our expert Partner network together with our Services team will ensure your Commvault to Microsoft Office 365 migration is seamless as well as cost-effective. Contact our Microsoft Office 365 migration specialists to discuss your project or get a quote today.
Migrating to Commvault Cloud
Transvault also supports migration into Commvault’s email archiving solution from several archiving platforms:
- Enterprise Vault to Commvault
- EMC SourceOne & EmailXtender to Commvault
- HP to Commvault
- PST, MSG, EML to Commvault
Transvault also supports migration from a wide range of archives into the Commvault Express journal service.
Start your Commvault Cloud migration with Transvault
Commvault Migration FAQs
- How can Transvault Help With my Commvault Migration?
Available from a global network of Transvault Certified partners, Transvault quickly and securely migrates legacy archived email (including archived user mailboxes and journals) from Commvault V10 and V11 (please call for other versions) into a wide array of different email archives and platforms.
It also migrates from a wide range of archives into the Commvault Express journal service.
All data movement is fully audited to ensure chain-of-custody, and mailbox shortcuts are fully managed to ensure a seamless experience for end-users as they move.
- How does Transvault connect into Commvault?
Where possible, Transvault connects directly via the Commvault REST (Representative State Transfer) API. In some instances, for example, when retrieving messages, we work directly with the source data. This is because the Commvault API can be slow and therefore not ideal for mass extractions at high speed.
- What happens to shortcuts (stubs) when we migrate from Commvault to the new system?
Transvault provides a comprehensive shortcut management service that ensures users have a seamless experience when they migrate from Commvault Cloud. As your data is moved, the corresponding shortcut is converted to point to the new archive. This activity can take place whilst users are online – there’s no need for any downtime or for users to logout.
In the situation where shortcuts aren’t supported by the target archive (for example, if you’re migrating from Commvault to Exchange or Office 365), legacy shortcuts are replaced (rehydrated) with the original item.
Another key feature designed to ensure a great user experience is that Transvault synchronizes with the current status of users’ shortcuts as they exist in their mailbox at the time of the migration. For example, where users have re-foldered their shortcuts ‘post-archiving’, Transvault ensures the corresponding items end up in the right folders post-migration.
- How can I find out if Transvault has moved all of our Commvault data?
Transvault migrations from Commvault start with a deep dive into the Commvault archive data to establish its exact contents.
This initial analysis enables you to create a baseline from which you can check that everything – emails, metadata and attachments – has been successfully migrated. It also enables forensic 1:1 auditing that provides evidence your data has been successfully transferred to the new environment.
Pre-analysis of the contents of your archive also gives you visibility of how much data there is to be migrated, how many mailboxes exist and how long the process is expected to take. This enables you to streamline and prioritise your migration, for example, migrating the IT department first, and apply policies that determine what you move and where. For example, move items less than 2 years old to primary Office 365 mailboxes, and anything between 8 and 10 years old to In-Place Archives.