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.
| Milestone | Where the date usually lives | If nobody has set it |
|---|---|---|
| Announcement | The support leader's project charter or kickoff note | You are early; take milestone one at an easy pace |
| Cutover | The migration runbook or the new platform's go-live plan | Name who owns the go-live decision |
| Cancellation (day 0) | The Zendesk renewal date or a written cancellation notice | Leave 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.
| Confirm | Owner | If skipped |
|---|---|---|
| How many years of tickets the account holds, and whether an earlier helpdesk was imported | Zendesk admin | The archive is assumed to be longer, or shorter, than it really is |
| Whether resolutions are written in internal notes, captured in fields, or both | Support operations lead | Outcomes that live only in notes are dropped by a field-only plan |
| Whether satisfaction ratings were switched on, and from when | Support operations lead | A key outcome signal is never counted |
| Who owns support history and whether customer contracts limit reuse | Owner or counsel | Rights 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.
| Confirm | Owner | If skipped |
|---|---|---|
| Which route makes the archive copy: CSV, JSON or the API | Migration lead | A CSV export leaves out ticket comments and descriptions, so threads are lost |
| Whether tickets over 1 MB will be handled separately | Migration lead | The longest, most escalated threads lose their comments in the JSON file |
| Whether audit events (status changes, reopens, satisfaction ratings) are pulled, and through which endpoint | Zendesk admin or developer | The archive shows final status, not when it changed or how often |
| Whether archived tickets are included | Zendesk admin | Older 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.
| Confirm | Owner | If skipped |
|---|---|---|
| The cancellation date, recorded in writing | Owner or finance | Every later date is guessed |
| What the company's agreement says about exports after termination | Counsel or finance | Under 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 controls | IT | The 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:
| Area | State | Note |
|---|---|---|
| Ticket history, 2016 onward | Confirmed | Earlier helpdesk imported in 2016 |
| Resolutions | Partial | Fields since 2020, internal notes before |
| Archive route | At risk | Vendor plan is CSV only |
| Audit events and ratings | Unknown | Developer to confirm per-ticket pull |
| Archived tickets | Unknown | Same developer |
| Ownership | Partial | Two 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.