Purview Integration during Merger and Acquisitions

Hey, arunsekaran​! 😊 There isn’t a native “tenant-to-tenant migration” for Purview sensitivity labels as objects. Labels are tenant-scoped (label IDs/GUIDs and publishing/encryption constructs don’t port cleanly), so in M&A you usually pick a strategy based on how labels are being used.

• If labels apply encryption / user-defined permissions: Microsoft’s common patterns are (1) keep the source tenant available for legacy protected content during the transition, (2) plan a support-led key/TPD move, or (3) “rekey” content (decrypt in source → migrate → relabel/encrypt in destination). See: Mergers and Spinoffs | Microsoft Community Hub
• If labels are classification/markings only: the destination tenant won’t automatically interpret the source label GUIDs, so the typical approach is to recreate a common label taxonomy in the destination and then re-label content after migration using portable signals (e.g., document properties/content markings + auto-labeling). See: Sensitivity Auto-labelling via Document Property | Microsoft Community Hub
• If you only need label interpretation/mapping (not preserving protection), there’s an advanced mapping option using “labelByCustomProperties” (labeling-only). See: Walkthrough for AIP labelByCustomProperties Advanced Feature | Microsoft Community Hub

Question for you: Are most of your existing labels encryption-enabled (especially user-defined permissions), or is this primarily classification/markings today? That detail usually determines whether “bridge temporarily” (keep source tenant) vs “relabel/rekey” is the right primary approach.