Cementing your Chain of Custody During a Migration Project
Why you should ensure your migration project is defensible through a preserved Chain of Custody in the case that your email archives need to be used as evidence. If you are currently undergoing a migration project, please learn more about our email archive migration tool.
Last week, we looked at how we can help you to preserve the integrity of your email archives during a migration project. Through the use of our innovative archive ingestion technology AIP, and the other features within Archive Shuttle, email items can be ingested into new target archives exactly the same as when they left. This ensures no potentially crucial data is lost should it be required for analysis later on in an investigation into employee misconduct, for example.
Providing a comprehensive log detailing the steps of the mail items journey is essential if you end up needing to use them as evidence in legal proceedings. Let’s take a hypothetical future scenario where an email administrator is looking to prove a historical mail archive (and all its items) have been successfully migrated to a new platform, such as Office 365 for instance, without suffering any undue interaction, modification or loss.
If the company has used a product like Archive Shuttle to migrate their archives, every item will have been provided with a unique, 1:1 identifier for its journey to a new platform. This identifier is compared between source and target system to demonstrate where the item came from and where it went.
This is a crucial component in your ability to prove your preservation of your Chain of Custody. The resulting record of this compliance can be further extended to include date migrated, number of items in source and target, size of items and hashes which can further help your ability to prove your Chain of Custody.
But suppose there has been an error in the migration of an item within an archive. This can happen if an item is too large for the target or became corrupted due to a network failure or server error. In these cases you need to be able to prove the reason why the item failed to ingest properly and take appropriate action where you can.
Our CTO, Michel Zehnder, recently spoke about how the new Archive Shuttle 6.6 helps negate these risks in the migration of live, offline and archive mail via the use of our AIP module.