Q1. What is TransVault Migrator for Microsoft Exchange & Office 365?... 1 Q2. What archives are supported?... 2 Q3. Will I need to buy services?... 3 Q4. Who created TransVault Migrator?... 3 Q5. Why not just import our legacy archive to Exchange via PST files?... 3 Q6. I would like to upload users PST files into Exchange/Office 365. How does TransVault help?... 4 Q7. Can TransVault Migrator help manage what we upload into Exchange?... 4 Q8. How quickly can TransVault Migrator migrate archived items?... 5 Q9. How can I find out if TransVault has migrated all of the data?... 5 Q10. What happens if an item fails to migrate?... 5 Q11. How does TransVault aid compliance when migrating?... 6 Q12. What do you mean by chain of custody and why is it important?... 6 Q13. Why do Exchange Journal Archives require special care?... 6 Q14. How does TransVault help migrate from Lotus Notes to Microsoft Exchange?... 7 Q15. I want to move to a hosted email Exchange service - can TransVault help?... 7 Q16. We are involved in a demerger and need to split up our archive. How does this work?... 7 Q17. How can we remove legacy archive shortcuts or stubs from users mailboxes?... 8 Q18. How is TransVault Migrator licensed?... 8 Q19. Do I need to provide systems to run TransVault Migrator on?... 8 Q20. Can new connectors be commissioned for development?... 8 Q21. How can I find out more?... 8 Q1. What is TransVault Migrator for Microsoft Exchange & Office 365? TransVault Migrator for Microsoft Exchange & Office 365 is a high-performance application that migrates email from myriad legacy 3 rd -party archive platforms into Microsoft Exchange on-premise, Office 365 (Exchange Online Archives), or a hybrid environment. Fully certified to run on the Windows platform and one of the first migration applications to support the powerful Exchange Web Services (EWS) API, TransVault Migrator moves your email records in one step to maintain chain-of-custody. Your move is also fully audited to ensure peace of mind. As you move you can use TransVault Migrator to perform selective migrations based on multiple criteria enabling you to take only the data you need and minimize the time and cost of your migration. Ensuring as seamless as possible experience for end users is also paramount, and TransVault Migrator includes advanced capabilities in this respect. For example, you can migrate only the items for which a shortcut still exists in the user s mailbox. Page 1
Example migration scenarios include: Moving from an unsatisfactory or legacy archive solution into Exchange Volume uploads of PST files into Exchange Standardization onto a common archive (e.g. where merging organizations have incompatible systems) A switch to an cloud-based strategy based on Exchange (i.e. Office 365, including Wave 15) Migration from IBM Lotus Notes to Microsoft Exchange (using an Archive First approach) During the migration process all actions are fully audited to ensure chain-of-custody. Q2. What archives are supported? TransVault Migrator supports migration into Microsoft Exchange primary mailboxes and personal archives, onpremise and online (via EWS) from a very wide range of proprietary archive including: Assentor Mailbox Manager (ilumin) Autonomy Consolidated Archive (ACA) Autonomy EAS for Exchange/Notes (ZANTAZ) Autonomy Message Manager (CAMM) Autonomy NearPoint (Mimosa) EMC EmailXtender for Exchange & Notes EMC SourceOne for Exchange & Notes EML files HP RISS/IAP for Exchange & Notes Metalogix Archive Manager: Exchange Edition Microsoft Exchange On Premise (MAPI) Microsoft Exchange Online*/Office 365 (EWS) Microsoft Exchange Personal Archives (EWS) MSG files NSF files OpenText IXOS for Exchange PST files Quest Archive Manager Symantec Enterprise Vault for Exchange & Notes Unify Daegis AXS-One for Exchange You can also use TransVault Migrator to: Export data out of Microsoft Exchange primary mailboxes and personal archives, on-premise and online. Import and export data from/to industry standard file formats including PST, EML and MSG files Accelerate migrations from/to hosted systems, including Office 365, Mimecast & Enterprise Vault.cloud Perform migration and conversion from Lotus Notes archives to Microsoft Exchange (see also Q14) More platforms are being added all the time. Please visit http://www.transvault.com/ or email info@transvault.com to ask whether your particular archive/version is supported. Page 2
Q3. Will I need to buy services? Yes. Although TransVault automates a lot of the data migration process, you will need additional services to plan the migration, install and configure TransVault, and oversee a successful completion. One of our many experienced partners across the globe will be able to advise on and deliver the appropriate TransVault-related services for your organization. Many partners are also able to provide and implement your Exchange /Office 365 environment. To contact a reseller or partner, please see http://www.transvault.com/ for more information. Q4. Who created TransVault Migrator? TransVault Migrator is developed by TransVault, a UK company whose staff have been involved with email archiving since 1998 and have experience of many large archiving projects involving different vendors systems. A Microsoft Gold Partner for many years, TransVault has extensive experience of Exchange and migrations into Exchange from a variety of email platforms, including IBM Lotus Notes. TransVault decided to encapsulate the knowledge gained into a software product that is available for purchase from archive migration specialists and archive vendors around the world. Q5. Why not just import our legacy archive to Exchange via PST files? Many 3 rd -party archive platforms offer the ability to export archived mailboxes to PST files, conversely, Exchange/Office 365 offers tools to assist with PST file ingestion. It s tempting, therefore, to consider a manual approach that uses PST files as an interim format. There are many issues with this manual, PST-driven approach, which include: It s slow and intensive. Native archive extraction and import tools are typically single threaded and need to be manually overseen (i.e. you could not leave several mailboxes running overnight). This significantly increases the migration time-frame and manpower costs involved. There s no error management. If an extract or import fails, the process stops with no indication of what the problem was and no ability to resume where the process left off or skip (and identify) just the items that fail. There s no logging or auditing. With PSTs there is no record of what data has been moved. All checking of PST actions needs to be done manually and this is subject to human error. PSTs risk the security and integrity of your data. The multi-step process involved in PST migrations mean that files need to be held in an interim location for a length of time, during which they are potentially open to tampering. Chain of custody is broken as a consequence, making a PST-driven migration unsuitable for organizations that have a compliance remit. You lose compliance data. If you migrate Journal archives, it s likely you will have used envelope journaling to capture vital BCC d and distribution list recipients. PSTs don t preserve this information. Page 3
Large PST files are prone to corruption. This creates problems when extracting large mailbox archives or Journal archives. You ll need lots of interim storage: You ll need to set aside a large amount of space to pre-stage your data as it is migrated. Given that PSTs are notoriously space-inefficient and that you will lose single instance storage, this may be up to 10 times the size of your legacy archive. No ingestion flexibility. With the PST approach you will typically need move all data in a mailbox there s rarely the ability to filter or be selective over what you extract or ingest. By comparison TransVault Migrator offers automated, multi-threaded, high-speed extraction with full errorlogging and chain-of-custody. It also offers advanced data selection and mailbox management capabilities. Q6. I would like to upload users PST files into Exchange/Office 365. How does TransVault help? TransVault Insight, part of the TransVault Software product family, offers the most advanced and scalable PST ingestion capability available today. Its features include: Automated, high-speed upload - direct into either Exchange 2007 SP1 and the Personal Archive service introduced with Exchange 2010 Pre-upload analysis of PSTs The ability to filter what is uploaded, e.g.: o Upload emails less than 3 months into the primary Exchange server o Upload emails between 3 months and 2 years old into the Personal Archive service o Don t migrate emails with [SPAM] in the subject or in Personal folders Full logging and auditing of all upload activity Throughput control parameters to limit loading on your live Exchange environment See also information on TransVault Insight and response to Q5. Q7. Can TransVault Migrator help manage what we upload into Exchange? Yes. Prior to your migration TransVault Migrator helps analyze your existing archive usage - e.g. how much storage is being used, how many archive stores there are, the average mailbox size, total number of items etc. TransVault then lets you be selective in what you migrate and to where. For example, you might want to migrate a department of users at a time to a specific Exchange server or re-group users according to storage consumption. Compliance regulations permitting, it s also possible to: Move just the last n years-worth of data, Move only the data that users still have shortcuts to Not move data according to criteria including To, From, Subject, Folder, Attachment, Date erc A migration is therefore a great opportunity to significantly reduce the quantity of email you retain. Page 4
Q8. How quickly can TransVault Migrator migrate archived items? Migration speeds from an on-premise archive into Office 365 have been measured at a rate equivalent to 1.2TB a day. Note, however, that achieving best performance is dependent on many environmental factors such as: Available network bandwidth Speed of the storage subsystem on which the legacy archive sits as well as the destination storage The ingestion performance of the target archive system (typical speeds may range from 5-50 GB/hour) The scheduling of other project elements such the commissioning of the target environment. As well as running multiple threads on a single server, multiple TransVault Migrator servers can be configured to operate in parallel to ensure that the performance of the TransVault services is never a limiting bottleneck on the duration of the project. Your chosen archive migration partner can establish a proof of concept (POC) to establish likely throughput rates in your specific environment. Q9. How can I find out if TransVault has migrated all of the data? TransVault Migrator includes auditing functions that keep track of the migration of each individual item. If the migration of an individual item fails (e.g. owing to data corruption, system configuration or connectivity issues) tasks can be automatically re-run to target just these items, adding them into the new Exchange mailbox alongside items that were previously successfully migrated. Reporting is also available to highlight how much data has been moved for each user in the legacy archive. Q10. What happens if an item fails to migrate? Failures may simply be temporary failures owing to environmental issues such as poor network bandwidth or high loading on the legacy archive system, in which case TransVault will automatically re-process the relevant item(s) a specified number of times and/or at a different time of day. In the event of a permanent failure, a full log of the item(s) in question is produced, enabling further sitespecific investigation. Permanent failures tend to be low typically.001% of the overall email quantity. They are also 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. NB - If your organization requires further investigative work to be carried out in the event of a corrupted item, this should be discussed with your chosen TransVault service provider in advance. Page 5
Q11. How does TransVault aid compliance when migrating? Manual migration methods that rely on problematic PST files (see response to Q6 & Q7) are subject to human error and have no tracking or auditing mechanism to prove that a migration was 100% successful. As described earlier in this document, TransVault eliminates opportunity for human error. It also includes complete auditing of the migration process. For example, detailed reports show 1:1 mappings of the ID of the item in the source archive and the ID of the new item as it now exists in Exchange, enabling you to demonstrate of a complete Chain of Custody for the data whilst undergoing migration. Importantly, TransVault is the only solution available that is able to preserve BCC d recipients and distribution list information from Journal mailbox archives. These messages may be part of legal proceedings or may be subject to regulatory requirements, so the loss of such vital information could be extremely costly and potentially damaging. Q12. What do you mean by chain of custody and why is it important? Chain of custody refers to the reliable recording of processes and procedures that occur while evidence (physical or electronic) is being captured, held, transferred or disposed of. It is vital that the evidence in question has remained free from alteration and that secure handling has been provided at all stages. TransVault Migrator s logging and reporting capability provides chain-of-custody evidence demonstrating that data has been successfully transferred into Exchange or Office 365. This is important since any later data investigation or discovery against migrated emails will seek to validate that the data has been handled correctly and that nothing was missed out. Q13. Why do Exchange Journal Archives require special care? Firstly, Journal archives tend to be extremely large, making a manual extraction approach slow and subject to size-related problems that can be encountered when relying on PST files as an interim store. TransVault allows journal and large mailboxes to be split into a number of separately handled virtual mailboxes of a user-defined size. This allows multiple processing threads to be applied to the migration of a single mailbox, significantly speeding up the migration task. Secondly, most of the organizations that capture emails into Exchange Journal mailboxes for compliance reasons have now standardized on using the Envelope Journaling feature. This feature was developed by Microsoft as a way to preserve vital P1 email header information which includes BCC'd recipients and the expanded members of any distribution lists. From a compliance perspective, P1 data must be preserved and available for access. The important thing to note is that different archive platforms store the additional P1 envelope information in different ways. For example, some store the P1 data separately in the archive index as a means of preserving Page 6
single instance storage, whereas others store it in the archive store itself. This creates a very special requirement at migration time that neither manual methodologies nor vendor extraction tools can support. TransVault has a special capability known as Envelope Reconstruction designed to ensure P1 data is properly captured and re-associated with the original P2 data during a migration. Contact info@transvault.com to discuss this feature and its relevance to your project. Q14. How does TransVault help migrate from Lotus Notes to Microsoft Exchange? Many organizations working with IBM Lotus Notes have already implemented an email archiving system. TransVault Migrator provides an opportunity to extract that email from the legacy archive, convert it to Microsoft Exchange format and send it into mailboxes (personal, archive *, or journal ) in Microsoft Exchange or Office 365. This approach removes the need to restore that archive to Notes Mail Files and then run a foreground migration to Exchange. TransVault also enables organizations to adopt an Archive First approach to migrating from Lotus Notes to Microsoft Exchange. This is how it works: Prior to migrating from Notes to Exchange, legacy email (e.g. everything up until the last month) is archived using a supported Notes compatible archive system such as EmailXtender for Notes. TransVault is then used to transform the Notes archive contents into a Microsoft Exchange archive mailbox. TransVault ensures all email formats are converted and all email addresses are re-written so that legacy Notes email is immediately available for use from within Microsoft Outlook and Outlook Web Access. Unlike mailbox migration solutions that operate in the foreground, the Archive First approach used in combination with TransVault moves data in an unobtrusive, behind the scenes way, that does not inconvenience end users or burden user mailboxes with legacy e-mails. Q15. I want to move to a hosted email Exchange service - can TransVault help? Yes. Customers wishing to switch to a hosted email service such as Office 365 or Mimecast can use TransVault Migrator to migrate their archived data. Also bear in mind that TransVault Migrator can help you move out of a hosted service at a later date. Q16. We are involved in a demerger and need to split up our archive. How does this work? TransVault can filter items by user, user groups, folder and dates, thus enabling data to be incisively selected and migrated to Exchange or Office 365. TransVault also has the capability to re-write all email addresses in sender and recipient fields so that the email is usable with any new domain naming or recipient-addressing conventions. Page 7
Q17. How can we remove legacy archive shortcuts or stubs from users mailboxes? TransVault Migrator includes extensive mailbox management services which include the ability to delete shortcuts to legacy archives as users are switched to the Exchange/Office 365 environment. Additionally TransVault Migrator can survey mailboxes for legacy shortcuts so that data items can be migrated into Exchange/Office 365 only when the user has kept their shortcuts for these items. If items that had been deleted by end users were migrated back into Exchange this could be confusing. TransVault can also account for the scenario where shortcuts have been moved between folders or forwarded to other users, ensuring emails are in the correct place post-migration, and that all shortcut owners still have access to the emails they had access to pre-migration. Q18. How is TransVault Migrator licensed? The core TransVault Migrator is licensed according to the volume of data you wish to migrate. Q19. Do I need to provide systems to run TransVault Migrator on? Unless provided by your chosen TransVault partner, you will need to make available one or more servers for a short time-period. You will also need access to an SQL database. Your TransVault partner can advise you on pre-requisites. Q20. Can new connectors be commissioned for development? Yes. Some of the current product functionality has been sponsored by platform vendors. Please contact TransVault. Q21. How can I find out more? Complete a query form on the TransVault website at www.transvault.com or contact TransVault on 646.808.0407 (North America), +44 (0)3333 404433 (EMEA) or info@transvault.com to find your nearest TransVault partner. Page 8