Helpdesk migration archive context checklist: what to confirm before announcement, cutover and Zendesk cancellation

Short answer

Work through eleven items at three checkpoints: before the move to a new helpdesk is announced, before cutover, and before the old Zendesk account is canceled, with the deletion clock that follows. Each item names the person who confirms it and what is lost if it slips. Will the export keep full ticket threads and documented outcomes? The usual answer is "threads, sometimes; outcomes, rarely, unless someone asks for the audit events in time".

Visual briefFull-size diagram
A horizontal countdown runs from announcement to cutover to cancellation and on to the day deletion begins, with checklist items ticking off under each milestone and one item left open in orange.
The checklist as a countdown. Day counts follow Zendesk's published policy as checked 2026-10-18; the company's own contract governs.

This checklist is part of the helpdesk migration handoff checklist. The opportunity itself is explained in the helpdesk migration guide, and the export mechanics in the Zendesk export guide.

The countdown: three dates to pin before ticking anything

Fix three dates, and who set each, before working down the list. A blank date is a finding, not a failure.

MilestoneWhere the date usually livesIf nobody has set it
AnnouncementThe support leader's project charter or kickoff noteYou are early; take milestone one at an easy pace
CutoverThe migration runbook or the new platform's go-live planName who owns the go-live decision
Cancellation (day 0)The Zendesk renewal date or a written cancellation noticeLeave it blank and record who will decide

Give each item one of three states: confirmed by someone who ran or owns it, unknown with a named person to find out, or at risk because the current plan loses it. A vendor's statement of work is not confirmation. Keep the sheet to configuration and ownership: no ticket numbers, customer names, agent names or screenshots.

Milestone one: before the migration is announced

At this point nothing about the old account's history has been scoped, so questions read as good practice rather than a challenge to anyone's plan.

ConfirmOwnerIf skipped
How many years of tickets the account holds, and whether an earlier helpdesk was importedZendesk adminThe archive is assumed to be longer, or shorter, than it really is
Whether resolutions are written in internal notes, captured in fields, or bothSupport operations leadOutcomes that live only in notes are dropped by a field-only plan
Whether satisfaction ratings were switched on, and from whenSupport operations leadA key outcome signal is never counted
Who owns support history and whether customer contracts limit reuseOwner or counselRights questions surface after an introduction instead of before

Rows two and three matter because they decide which export route is needed later. An archive that keeps what was said but not how the case ended answers only half the question.

Milestone two: before cutover to the new helpdesk

Once the load plan is fixed, closed tickets tend to be relabeled "reference only" and the event history quietly drops out.

ConfirmOwnerIf skipped
Which route makes the archive copy: CSV, JSON or the APIMigration leadA CSV export leaves out ticket comments and descriptions, so threads are lost
Whether tickets over 1 MB will be handled separatelyMigration leadThe longest, most escalated threads lose their comments in the JSON file
Whether audit events (status changes, reopens, satisfaction ratings) are pulled, and through which endpointZendesk admin or developerThe archive shows final status, not when it changed or how often
Whether archived tickets are includedZendesk adminOlder closed tickets are missed by any route that skips the archive

The vendor documentation behind these rows, checked on 2026-10-18: Zendesk's export article says a JSON export lists tickets with their comments, CSV exports omit comments and descriptions, and comments are removed from tickets over 1 MB in the file. Zendesk usually archives tickets 120 days after they close; archived tickets drop out of views but stay reachable through search and the API. The ticket audits reference says the account-wide audit list skips archived tickets, while the per-ticket endpoint covers them, and the incremental ticket event export can include full comment data. The company's admin should confirm all of this in their own account, because plans and features change.

Milestone three: before cancellation, and the clock after it

The cancellation date starts a clock the company does not control. Count from the date in the written notice, not from go-live.

ConfirmOwnerIf skipped
The cancellation date, recorded in writingOwner or financeEvery later date is guessed
What the company's agreement says about exports after terminationCounsel or financeUnder the 2023-06-01 agreement version, export is available on written request for thirty days after termination or migration; other versions may differ
That the archive copy is saved, readable and stored somewhere a named person controlsITThe copy exists but nobody can open it after the account closes

Zendesk's deletion policy then sets the end point: deletion generally begins about 90 days after cancellation, and once it starts, ticket, user and attachment data are removed within 40 days and cannot be restored. Anything still marked at risk when that clock starts is usually gone for good. SourceX sets none of these dates; they come from Zendesk's published policy and the company's own contract.

Reading the finished checklist, and who decides what comes next

Illustrative. A fictional 240-person logistics software company finished the checklist two weeks before cancellation. The summary its Zendesk partner read back to the COO:

AreaStateNote
Ticket history, 2016 onwardConfirmedEarlier helpdesk imported in 2016
ResolutionsPartialFields since 2020, internal notes before
Archive routeAt riskVendor plan is CSV only
Audit events and ratingsUnknownDeveloper to confirm per-ticket pull
Archived ticketsUnknownSame developer
OwnershipPartialTwo enterprise contracts restrict reuse

That is a sound metadata-level description, and the CEO, not the admin, decides whether to explore licensing it; the COO can take the summary to them. If the CEO agrees, disclose first: you are a SourceX referral partner, and SourceX may pay you a reward it funds separately, never deducted from the company's payout. SourceX licenses approved business data directly from companies for AI training and evaluation, and manages agreement, rights review, data preparation, delivery and payout.

Then check fit: 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. Buyer interest, de-identification needs and any offer stay unknown until SourceX reviews the application. 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.

For the introduction itself, use the annotated helpdesk migration email. The metadata-only Zendesk inventory template and the ticket thread introduction checklist go deeper on the record side, and CX consultants will find more plays on the CX consultant referral page.

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 countdown shows threads and outcome events will survive cancellation and the owner wants to talk, register as a partner, check who qualifies and read the program terms before introducing them.

  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

The migration vendor says the export is handled. Does the checklist still matter?

Yes, because most migration plans are scoped around open tickets and current fields. Ask which route the vendor uses and whether it carries audit events and archived tickets; a yes from the person who ran it, in writing, is what ticks the box.

What if the company has already canceled Zendesk?

Start at the cancellation milestone and count from the written cancellation date. If deletion has already begun, the only question left is what copy the company kept, which is still worth asking.

Does SourceX set any of these dates?

No. Every date comes from the company's own plan or its contract with Zendesk. SourceX does not set or suggest deadlines, and a partner should never invent one.

Sources

  1. support.zendesk.com/hc/en-us/articles/4408886165402-Exporting-ti…
  2. support.zendesk.com/hc/en-us/articles/4408887617050-About-ticket…
  3. developer.zendesk.com/api-reference/ticketing/tickets/ticket_audits
  4. developer.zendesk.com/api-reference/ticketing/ticket-management/in…
  5. support.zendesk.com/hc/en-us/articles/4408883628954-Zendesk-Serv…
  6. zendesk.com/company/agreements-and-terms/main-services-a…
  7. 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