Explore TransVault™

AXS-One Migration to Enterprise Vault

How is data moved between AXS-One and EV?

TransVault has connectors that link directly into your AXS-One archive store and Enterprise Vault stores.

In fact, TransVault was the first solution in the market to have its archive connectors certified by Symantec (now Veritas) under the STEP program.

Using these connections your email records are moved in one transaction, ensuring optimum speed and reliability for your move.

Can we convert a Notes AXS-One archive into Exchange format?

Yes.  TransVault offers migration and conversion capability between Exchange and Notes archives. E.g.

An organization using AXS-One for Notes can migrate their contents to say, Enterprise Vault for Exchange or Office 365, using TransVault to perform the migration along with on-the-fly email format conversion.

In most cases, TransVault can convert shortcuts so they work with the new archive system.

Where necessary, TransVault can re-write internal email addresses so that legacy emails can be successfully replied to.  This is useful in the event of a merger or other scenario where the email address may have changed.

TransVault also includes the ability to decrypt Notes emails where passwords can be made available.

Additionally organizations can actually reduce the time it takes to migrate their ‘live’ email system between Exchange and Notes by taking advantage of migrating their archives first, as this can be done in a way that does not impact end users.  In fact some organizations ramp up their archiving so that they can minimize the size of the live mailboxes that need to be migrated as a ‘foreground’ exercise.

Benchmark testing has further shown that TransVault has superior conversion performance and message format fidelity when compared with leading third-party mailbox migration applications.

How can we be sure all our data is being moved correctly?

As your data is moved, TransVault carries out a series of integrity checks to ensure your email records will be viable post-migration.  Any items that fail to migrate are automatically re-processed a specified number of times and/or at a different time of day.

Failures to migrate an item may be temporary, owing to environmental issues such as poor network bandwidth or high loading on the legacy archive.

‘Permanent’ failures tend to be low – typically .001% of the overall email quantity.  They are usually attributable to pre-existing problems in the source archive (i.e. not caused by the migration process).  As such, it is likely that these items would NOT have been picked up by any audit or eDiscovery exercise.   

In the event of a permanent failure, a full log of the item(s) in question is produced to enable investigation.  You can attempt a manual retrieval of any failed messages directly from the log, a feature which massively reduces troubleshooting overheads.

If your organization requires further investigative work to be carried out on failed items, data remediation services are available to help and where possible, fix the problem to the satisfaction of your legal team.

For example, in one project it was discovered that some emails only had the email ‘shell’ intact – the actual body of the email and any attachments were missing. The customer’s legal team requested for all the retrievable header data (i.e. Subject, To, From, Date) to be preserved and migrated along with explanatory text into the email body to explain to a future eDiscovery operator that the original message was broken prior to the migration. TransVault’s remediation service was able to meet this request.

NB – If your organization requires further investigative work and data remediation to be carried out in the event of a corrupted item, this should be discussed with your chosen TransVault service provider in advance.

Click here for more FAQs relating to this platform

TransVault logo