Joiner-mover-leaver redesign archive context checklist: what to confirm before legacy access workflows retire

Short answer

Check three stations in order: before the redesign is announced, before the new HR-triggered automation goes live, and before legacy rules, workflows and trackers are switched off. At each, confirm whether the records will still show who transferred, who left and why an exception was granted, name the owner, and note what is lost if it is skipped. Station dates come from the company's own plan, never from your estimate.

Visual briefFull-size diagram
A countdown track with three stations, announcement, go-live and legacy switch-off, where checklist items on HR status codes, exception tickets, log routing and script logic tick off before the old identity workflows are retired.
The checklist as a countdown. Station dates come from the company's own redesign plan.

The checklist belongs to the redesign guide for access-management advisors. The questions are first raised in the 20-minute meeting agenda; this page carries them through to switch-off.

Setting the clock for an access-process redesign

StationWhere the date usually comes fromIf no date exists
AnnouncementThe access governance project charter or an audit finding that triggered itTreat station one as an early, unhurried inventory
Go-liveThe cutover plan for HR-triggered access automationRecord who owns the go-live decision
Legacy switch-offRetirement of old automation rules, a legacy IGA tool contract end or a ticket queue migrationLeave it open; the item is "who decides"

Every item gets one state: confirmed by an owner, unknown with a named person to find out, or at risk because the plan drops it. Record configuration, counts and owners. Never record names, user IDs or HR details, even as examples.

Station one: before the redesign is announced

ConfirmOwnerIf skipped
Whether each past account change can be matched to an HR status: transfer, leave or terminationHR records owner and access leadTransfers and departures become indistinguishable in history
Where exceptions are approved: access request tool, service desk or emailAccess request ownerThe reasons behind kept access or delayed disablement scatter
Whether platform audit logs are routed to long-term storageAccess leadHistory older than the platform default is already gone
Who owns HR and access records, and which privacy obligations applyCIO or owner, with counselRights and privacy issues surface after an introduction

The control expectation is clear: NIST SP 800-53 expects access to change when someone changes jobs, and account handling to follow HR exits and moves. Whether the records show that it happened, case by case, is what this station finds out.

Station two: before the new workflows go live

ConfirmOwnerIf skipped
Whether legacy workflow and automation run history will be exported before the switchAccess leadPortal history ages out after go-live
Whether the classification logic in old automation rules is documentedAccess engineerNobody can explain later why a change counted as a transfer
Whether exception tickets keep their link to the HR event that triggered themService desk ownerDecisions survive without the situation they answered
How many years and roughly how many role changes per year existHR records ownerThe archive cannot be described when it matters

Retention is short by default on some platforms. Microsoft Entra keeps audit logs for 7 days on Entra ID Free and 30 days on P1 and P2, and lifecycle workflow history in the admin center can be filtered for up to 30 days; Microsoft's guidance is to save that history as a CSV report, up to 100,000 records per download, or use the reporting API for more. Whether to do any of this is the company's call.

Station three: before legacy workflows are switched off

ConfirmOwnerIf skipped
Whether old trackers and spreadsheets of exceptions are archived or deletedAccess leadThe only record of some handover decisions disappears
Whether the legacy IGA tool or ticket queue keeps a read-only period, and who reviews its endCIOHistory is removed at contract end without a decision
Who signs off the final retention decision for access and HR historyCIO or CISO, with HRNo one is accountable for what was dropped
Whether the owner wants to hear about licensing before switch-offOwnerThe question is never asked while the history exists

Bulk disablements after a reorganization are the case to watch. If the platform logged "account disabled" with no HR reason or approval attached, that slice of history cannot answer the transfer-versus-departure question, and the checklist should say so honestly.

When the checklist is done: fit, disclosure and what stays unknown

The checklist describes the records; it does not decide eligibility. Before raising SourceX, check: 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.

What the checklist establishesWhat only SourceX review establishes
Whether transfers, departures and exceptions are distinguishable, and for how many yearsCurrent demand for access-governance decision records
Who owns HR and access history, and which privacy rules applyThe rights and privacy review, including de-identification
Documented go-live and switch-off datesAny offer to the company
That the reward was disclosedWhether any referral reward becomes payable

Ask permission before mentioning SourceX, and disclose your interest in the same breath. SourceX licenses approved business data directly from companies for AI training and evaluation and pays any eligible reward separately under its terms, never from the company's payout. Illustrative only: a $400,000 payout to the company would mean a $70,000 default reward. Sign the Channel Partner Agreement before submitting; attribution goes to the first valid introduction within the 90-day window, credited when the company submits a verified application, with one partner per company. When the owner opts in, use the introduction email. The exception handling data guide, the email archive migration guide, the Microsoft 365 Business Premium user limit page and the MSP client offboarding checklist cover neighboring records and moments.

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 legacy workflows are still running and the owner wants to talk before they retire, register as a partner, check the company against who qualifies, and read the program terms first.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
  4. Step 4You get your rewardthe greater of $50,000 plus 5% and 15% of the actual supplier payout, with no cap. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details.

Common questions

Why does the old provisioning script matter if it is being replaced?

Because it often holds the rule that decided whether a change counted as a transfer or a departure. Without that rule, older records can show an action but not why it was classified that way.

Can the consultant export workflow history to protect it?

No. The company's identity team decides whether to export and where to store it. The consultant asks in time and records the answer, never the data.

What if the company never routed audit logs to storage?

Then platform history is short, and the longer record depends on HR status history and service desk tickets. Note that plainly; it does not end the conversation.

Sources

  1. refer.sourcex.si/terms
  2. learn.microsoft.com/en-us/entra/identity/monitoring-health/refer…
  3. learn.microsoft.com/en-us/entra/id-governance/download-workflow-…
  4. nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r…

Free resources

Know a company with valuable proprietary data?

Become a referral partner, get your link and introduce the company’s CEO (in an owner-run company, usually the owner). Referral partners can join from most countries. We can't work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists. The companies you introduce should be based in the U.S., Canada and the EU, or in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia with at least 70% of their data in English.

Refer a company →

I own a business

Explore licensing your company's data directly to SourceX for AI training and evaluation. Start a short assessment; no uploads needed.

Start an assessment