Forum Discussion
Purview Integration during Merger and Acquisitions
DerekMorgan2 Our labels doesn't apply Encryption, and it is primarily used for marking or classifying. Our labels are applied manually and doesn't use any auto-labelling policies.
I am still not sure with the other organizations labelling practices.
arunsekaran, depending on the labelling practices from other organizations, I would definitely go by what nikkichapple replied earlier and perform an impact assessment on the other organizations. From experience, either the other organizations will adopt your labelling practices, if they have none or have weak labelling practices, or you'll absorb their practices if they strengthen your labelling foundations 😁
That said, there is migration tooling available from Quest on Demand, that migrates content protected by Purview via sensitivity labels: https://support.quest.com/on-demand-migration/kb/4379126/sensitivity-labels-and-encryption-migration-of-protected-content-for-mail-sharepoint-and-onedrive
Thanks! I'll be sure to check that out
One additional factor that’s often overlooked is licensing in the target tenant.
If the merged tenant is licensed with Business Premium or A3/E3/G3, you are limited to manual sensitivity labelling by end users. Service‑side auto‑labelling for data at rest (SharePoint and OneDrive) requires higher‑end compliance licensing (for example, E5 or equivalent add‑ons).
This makes the migration approach even more critical. Where automatic labelling at scale isn’t available post‑migration, it becomes essential that:
- Your migration tooling preserves or reapplies labels during migration, and
- Labels are already present on the content as it lands in the target tenant
Otherwise, you risk ending up with large volumes of unlabeled data and no practical way to remediate that at scale without major user effort.
In short, licensing directly influences your viable migration strategy, and should be treated as a core input when designing the target labelling model and migration approach.
I confirmed that they are on E5 already, so one less problem to worry about.. haha
