The MigrationWiz Project Archive and Why You Keep Projects After Cutover Closes

Are you deleting MigrationWiz projects once cutover is done and then losing the audit trail you will need months later?

A MigrationWiz project is the migration audit record. It contains per-user item counts, item-level error logs with error codes and timestamps, job status history, and throughput data across all migration passes. Once a project is deleted, that information is permanently removed.

That history becomes valuable long after cutover for common scenarios: a user reports missing mail six months later and the item-level report can show whether it migrated successfully, pointing to a delivery or access issue in the destination, or whether it failed with a specific error code, pointing to a migration issue that may have a remediation path. Compliance audits may also require proof of when particular mailbox data moved. Even internal retrospectives benefit from real throughput metrics when building a more accurate schedule for the next engagement.

BitTitan charges for active User Migration Bundle licenses applied to active migration projects. Keeping a project archived after UMB licenses have been consumed does not create an ongoing licensing cost.

Do you have a documented retention policy for MigrationWiz projects that defines how long project records are kept after migration closes?

#BitTitan #MigrationWiz

Leave a Reply

Your email address will not be published. Required fields are marked *