Case Study: Managing and Migrating Office 365 tenant for Spin-off


Biotech Company, Pharma Company


Client was spun out as an independent, public traded company.

Solution Summary

The client had split into two business entities and wanted to migrate data for the newly created entity from the existing O365 tenant to a new tenant. Since the client was a pharmaceutical company, there was a lot of GXP data in the source tenant. Each document was required to be migrated. A source to target comparison report needed to be prepared for review and approval by the Quality team.

Data migration included both OneDrive for Business personal data and SharePoint data. SharePoint data also has term sets that needed to be migrated, and data was required to be tagged. All permissions were to be retained.

Solution Strategy

Since the client has validated data in the source environment, our migration team developed discovery scripts to make an inventory of data and presented it to the customer. This helped the customer to gauge the scope of the migration and presented with a high-level overview of what’s getting migrated. This inventory also helped customer IT to send it for Legal review.

Though there are popular migration tools available in the market which can migrate from tenant to tenant, they don’t offer reports that can compare source and target post-migration. Often, they report what’s migrated and what failed. TrnDigital team developed a comparison tool that can compare source and destination, item by item, and present a report of missing items. This ensured that each item was accounted for during the migration. Along with the migration report, a comparison report was prepared, which reassured the customer that everything copied over.

Using PowerShell batch scheduling of migration jobs and integrating the comparison tool reduced the time taken for migration, which in turn saved cost.

  • Innovative post migration comparison tool helped testing team to save migration testing time. It also helped the Legal and Quality teams to review and sign off on the migration.
  • PowerShell automation of migration saved lot of effort in creating migration jobs manually.
  • Reporting framework enabled quicker strategic and operational decisions with very minimal human errors and enabled cross-segment reporting.

If you are planning any Microsoft implementation and looking for help, feel free to request a consultation.