Before plan consolidation: a retention timeline for entitlement exception records

Short answer

Before customer plans are consolidated, inventory four things: which record classes exist (plan histories, permission changes, support tickets, legacy contracts), how many years each covers, who owns each system, and the date after which each stops being reachable. Event-level history goes first. Stripe events are retrievable through its API for 30 days, and Okta's System Log query returns 90 days. Zendesk archives most tickets about 120 days after closing but keeps them reachable. The acquired product's billing system ends on whatever date the company sets.

Visual briefFull-size diagram
A horizontal retention timeline with four record rows: billing events reachable for 30 days, identity events for 90 days unless streamed, tickets archived after about 120 days but still reachable, and the acquired billing system ending at a company-set retirement date unless preserved.
Windows are product defaults from vendor documentation; the retirement date is set by each company.

This retention timeline is part of exception handling records for AI agents. It is for customer platform consultants working on a plan consolidation or billing migration who want to know what disappears, when, and who decides.

The retention clock, record by record

Not every record ages the same way. Current state usually survives a consolidation; the history of how it changed often does not.

Record typeWhere it livesTypical windowWhat happens at the endWho approves keeping it
Billing change eventsBilling platform, for example StripeRetrievable through the Events API for 30 daysOlder events no longer returned; the subscription's current state remainsFinance or billing owner
Identity eventsIdentity platform, for example OktaSystem Log query returns 90 daysOlder events not returned unless streamed or exportedIT owner, with the data owner
Support ticketsHelpdesk, for example ZendeskArchived in most cases 120 days after closingOut of views and reports; still reachable by search and APICustomer support director
Ticket change historyHelpdesk auditsKept with the ticketArchived tickets drop out of the account-wide audit list; read ticket by ticketCustomer support director
Legacy plans and contractsAcquired product's billing system and CRMUntil retirementGone, or reduced to a summary migrated into the new systemCOO, CFO or CEO

The pattern is consistent: the further a record is from current state, the shorter it lives. A billing platform will always show what a customer pays today. It may not show what it paid in 2022, why that changed, or which exception covered the gap.

What disappears first during plan consolidation

Three things tend to vanish in this order.

  1. Event detail. The 30-day and 90-day windows above run continuously. Any change older than that exists only if the company already kept it somewhere else. Okta offers log streaming to external platforms for exactly this reason, and many companies send billing events to a warehouse. Whether this company does is the first question.
  2. Legacy plan history. Consolidation projects migrate active customers onto current plans. The acquired system's history of old plan codes, grandfathered features and one-off deals usually stays behind. When the system is retired, that history goes with it unless someone decides otherwise.
  3. The mapping between old and new. The table that says which legacy account became which current account is often a spreadsheet owned by the integration team. Once the project closes, nobody maintains it.

Tickets are the most durable. Archiving changes how they are found, not whether they exist. That is why helpdesks often hold the complaint long after billing and identity have lost the decision.

The inventory before a system change

Ask the customer support director, at the level of what exists:

  • Which systems hold plan histories, permission changes and support resolutions, and from which year?
  • Are identity events streamed or exported anywhere, and since when?
  • Are billing events copied to a warehouse or kept only in the platform?
  • When is the acquired product's billing system scheduled to be retired, and who set that date?
  • Does a mapping from legacy accounts to current accounts exist, and who keeps it?
  • Roughly how many entitlement exceptions a year, and since when?

Write down the answers as ranges and names. If answering would mean logging in to a system, ask instead. Partners never ask for or handle raw client records. The software consolidation handoff checklist covers the wider project, and the system map for entitlement records shows which keys need to survive.

Who must approve keeping it

The partner never decides what is kept. Each record class has an owner, and keeping it past its default window is that owner's call, often with the executive above them.

  • Event streams and exports need the IT owner to set them up and the data owner to agree that keeping them is appropriate, because identity events carry personal data.
  • Legacy system retirement is usually a decision for the COO or CFO, sometimes written into the integration plan.
  • Ticket retention sits with the customer support director, within the company's retention policy.

Do not recommend keeping or exporting anything. A partner's job is to notice that a real access event exists, such as a documented retirement date, and to ask who decides. That is real urgency; an invented deadline is not. The software consolidation introduction plan covers when to raise it, and the software consolidation guide covers the project itself.

Qualification: what the inventory settles

The inventory tells SourceX which records exist, for how long, in which system and under whose ownership. It does not settle whether they can be licensed. Customer contracts may limit use of account data, identity logs carry personal data and acquisition agreements can carry their own terms. Those questions belong to the company and SourceX in rights review. The who-can-license decision tree shows who should be in the room.

The company also needs 50+ full-time employees at peak (contractors excluded), documented operating history, rights to license 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.

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 a client's consolidation has a dated retirement and the owner can say what exists before it, register as a partner, check the company on who qualifies and read the program terms before introducing its decision-maker.

  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

Should a partner tell the company to export its logs before they expire?

No. Keeping or exporting records is the company's decision, made by whoever owns them. A partner can point out that a window exists, ask who decides, and leave it there.

Does an archived ticket count as lost?

No. Zendesk says archived tickets drop out of views and reports but stay reachable through search and the API. They are harder to report on, not gone.

Sources

  1. docs.stripe.com/api/events
  2. developer.okta.com/docs/reference/system-log-query
  3. help.okta.com/oie/en-us/content/topics/reports/log-streami…
  4. support.zendesk.com/hc/en-us/articles/4408887617050-About-ticket…
  5. developer.zendesk.com/api-reference/ticketing/tickets/ticket_audits
  6. refer.sourcex.si/terms

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