# Tenant consolidation archive checklist | SourceX

Canonical: https://refer.sourcex.si/resources/tenant-consolidation-archive-context-checklist
Last updated: 2026-11-04

Yes. The user-pairing step in a Microsoft 365 consolidation runs on account attributes, so the owner can see which old accounts match new ones, and which match nothing, without anyone opening a message. This checklist puts that fact on a timeline with three milestones: before the consolidation is announced, before cutover, and before the source tenant is switched off. At each one it lists what to confirm, who owns it, and what is lost if the step is skipped.

It is part of the [tenant consolidation guide for Microsoft 365 migration partners](/guides/moment-tenant-consolidation-microsoft-365-migration-partners), which covers the owner conversation itself. Use this page as the working list you keep open during the project.

## Reading the countdown

The checklist runs backwards from one fixed event: the day the source tenant stops being available. Everything on it is metadata. Counts, dates, account types and named owners are enough; no step asks for message content, a mailbox export or a login.

Three columns repeat at every milestone:

- **Confirm:** the fact to write down, in one line.
- **Owner:** the person at the company who can state it or decide it.
- **If skipped:** what happens by default when nobody acts.

Dates come from the company's own project plan, license agreement and tenant administrator. This page invents none. Where Microsoft documents a standard window, it is cited, and enterprise or partner-purchased agreements can differ, so the company's admin confirms the real one.

## Milestone one: before the consolidation is announced

The aim at this stage is to know the shape of the history before the project plan fixes its scope. Once staff hear about the move, accounts start being cleaned up informally, and departed users' mailboxes are the first to go.

| Confirm | Owner | If skipped |
|---|---|---|
| The date the source tenant's subscription ends or is due to be cancelled | IT lead, from the license agreement | The project works to an assumed date and the real one arrives first |
| Whether any retention policy or hold already covers former employees' mailboxes | Compliance or IT lead | Accounts deleted during cleanup may not become inactive mailboxes |
| Which entity will own the records after consolidation | General counsel or CFO | Nobody can later say who may authorize a licensing discussion |
| A freeze on deleting user accounts until the identity map is drafted | IT lead, approved by the CFO | Informal cleanup removes history before anyone has counted it |

Microsoft's documentation explains why the hold question comes first. A mailbox becomes inactive only if a hold or retention policy is applied before the user account is deleted. A hold applied afterward does not bring it back. The [Microsoft 365 retention policy checklist](/resources/microsoft-365-retention-policy-checklist) covers the policy options in more depth.

## Milestone two: before cutover

Cutover is when mapped users start working in the target tenant. The identity map is drafted here, and it is the step that answers this page's question.

Microsoft's Cross-Tenant Identity Mapping pairs each source user with one destination user, matched by primary email address or from an uploaded list of object IDs, and it has to run before workload licenses are applied in the destination. Nothing in that step reads a message, a file or a chat.

| Confirm | Owner | If skipped |
|---|---|---|
| Count of source accounts paired with a destination account | Migration partner, from the mapping file | The owner cannot see how much history follows current staff |
| Count and type of source accounts with no destination (former staff, shared, service) | Migration partner, reviewed by the IT lead | Orphaned accounts stay behind with no decision recorded |
| Earliest and latest activity years for the orphaned accounts | IT lead | Nobody knows whether the history spans two years or fifteen |
| The person who decides what happens to orphaned history | CEO, with general counsel | The decision defaults to whoever closes the old tenant |
| Whether the owner wants to hear about a licensing review | The named decision-maker | The question is never asked, or is asked too late to matter |

Illustrative. In a consolidation of a 230-person engineering services firm into its parent's tenant, the pairing file covers about 230 current staff and leaves about 85 accounts with no destination, mostly former staff back to 2011. Those three numbers, plus the name of the CEO as decision-maker, are everything the checklist records at this milestone.

The last row is where the referral question sits. Disclose before the owner answers: you are a SourceX referral partner and may receive a reward if a qualifying license completes; SourceX funds it separately, it never reduces the company's payment, and it is payable only after the conditions on the [rewards page](/rewards) are met. If the answer is no, mark the row "declined" and carry on with the migration unchanged.

## Milestone three: before the source tenant is switched off

The final stage is about windows that close on their own. Each item asks whether a decision about orphaned history has been made while it can still be acted on.

| Confirm | Owner | If skipped |
|---|---|---|
| Whether any orphaned accounts were deleted, and on what date | IT lead | A deleted user can be restored with their data for 30 days; after that the account and mailbox are permanently deleted |
| Whether inactive mailboxes exist for former staff, and under which hold | Compliance lead | History thought to be kept may not be |
| The subscription stage the source tenant is in (active, Expired, Disabled) | IT lead, from the admin center | During Disabled only admins can reach and back up data, and for most offers that stage lasts 90 days before deletion |
| A recorded decision for the orphaned history: keep, delete, or review for licensing | The named decision-maker | The tenant's end date makes the decision instead |
| Where the decision record is filed | CEO's office | Nobody can show later who decided and when |

### The flag to raise out loud

If the source tenant's end date is close and the last row is still blank, say so to the owner directly. That is the only real urgency on this page, and it comes from the company's own verified dates, not from any program deadline.

## Turning the checklist into an owner decision

A finished checklist gives the owner a short, factual picture: how many accounts have no target, how far back they go, which windows are still open, and who decides. It does not say whether the history has value. Only a SourceX review can address that.

Read it in one of three ways:

1. **No orphaned history of note:** close the file; there is nothing to decide.
2. **Orphaned history, owner declines a review:** the checklist still did its job; the decision is recorded before the tenant closes.
3. **Orphaned history, owner opts in:** check the company baseline below, then send a short introduction to the named decision-maker.

The company baseline is 50+ full-time employees at peak (contractors excluded), a documented operating history, rights to license the records and an authorized contact. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English. After an acquisition, confirm which entity holds the rights.

Unknown until SourceX reviews it: the rights position after the acquisition, privacy commitments that limit reuse, and whether any dataset need exists. Partners sign the Channel Partner Agreement before submitting introductions, and the first valid introduction within the 90-day window is credited when the company submits a verified application. For wider preservation planning, see the [tenant-to-tenant migration guide](/guides/microsoft-365-tenant-to-tenant-migration-after-acquisition), the [software consolidation handoff checklist](/resources/a-data-opportunity-handoff-checklist-for-a-software-consolidation) and the [IT handover checklist](/resources/it-handover-checklist-sale-of-business).

## Next step

> **Refer a company. No cap on rewards.** Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.

If the checklist shows orphaned history and the owner opts in before the source tenant closes, [register as a partner](/register), confirm the company on [who qualifies](/who-qualifies), and read the [terms](/terms) before you introduce the decision-maker.

## Sources

- https://learn.microsoft.com/en-us/microsoft-365/migration/cross-tenant-identity-mapping?view=o365-worldwide
- https://learn.microsoft.com/en-us/purview/inactive-mailboxes-in-office-365
- https://learn.microsoft.com/en-us/microsoft-365/admin/add-users/restore-user?view=o365-worldwide
- https://learn.microsoft.com/en-us/microsoft-365/commerce/subscriptions/what-if-my-subscription-expires?view=o365-worldwide
- https://refer.sourcex.si/terms
