A support-triage tool is portable only when you can move the records and reconstruct the working service around them. Ownership is broader than having an administrator password: it includes control of the account, domains, customer identities, workflows, evidence, integrations, and a safe exit. Compare options with a small migration exercise rather than a feature-list promise.
Inventory what must remain usable
List tickets, message threads, attachments, users, organizations, forms, custom fields, tags, priorities, statuses, groups, agents, SLAs, macros, triggers, automations, views, consent records, suppression requests, audit history, and integration mappings. Mark each as required for live service, historical evidence, reporting, or legal retention. Record the volume, format, relationships, identifiers, and oldest required date.
The inventory prevents a common mistake: calling a flat ticket CSV a complete migration when it omits comments, attachments, identities, rule logic, or event history. Use fictional records for early tests and limit access to real customer data.
Test export claims with a real sample
Zendesk's account-data export documentation describes JSON, CSV, and XML exports, notes that account-owner enablement and permissions can apply, and identifies plan limits and an API option. That illustrates why comparison notes should distinguish available format, enabled state, entitlement, scope, and who can initiate an export.
Run a representative export before purchase or renewal when a trial or authorized sandbox permits it. Check whether stable IDs, timestamps, time zones, authors, comments, attachments, field definitions, deleted-state markers, and relationships survive. Measure export time and document any download expiry. Open the files independently and count records; an export button is not proof of recoverability.
Score account and identity ownership
Identify the legal account owner, billing owner, primary administrator, recovery contacts, domain-verification holder, integration owners, and emergency successor. Check whether roles are separable, whether administrators can be removed safely, and whether service continues if one employee leaves. Avoid shared credentials.
Verify how customer and agent identities map during import. Test duplicate emails, renamed organizations, merged users, deactivated agents, and messages sent through old support addresses. A portable archive that cannot preserve authorship or reply routing may be insufficient for an operating queue.
Compare workflow evidence, not only records
Ownership includes knowing why the system behaved as it did. Zendesk's account audit-log guidance documents time, actor, item, activity, filters, and export, with access and coverage depending on plan and permissions. Ask every vendor which administrative, routing, permission, integration, and security changes are logged; how long they remain searchable; and whether logs can be exported without vendor support.
Export a small audit window and match it to deliberately created test changes. Record missing event classes and attribution limits. Do not assume that ticket history equals configuration history.
Exercise a reversible migration
Create a scored pilot using representative fictional tickets, conversations, attachments, customer identities, fields, queues, rules, and reports. Export from the source, import or transform into the candidate, then verify counts and field-by-field relationships. Send no customer messages. Confirm that the candidate can route a new test request, preserve the original source record, and roll back without losing work created during the pilot.
Include a continuity plan: frozen-change window, dual-read period, handling of messages arriving during transfer, exception queue, reconciliation report, and cutback trigger. Document which features must be rebuilt manually and which cannot be reproduced.
Use a decision matrix with hard gates
Score export completeness, open or documented formats, API access, account succession, role separation, audit coverage, retention, identity fidelity, attachment recovery, workflow recreation, integration portability, privacy controls, accessibility, cost, and support. Treat unknowns as risks rather than awarding full points.
Set hard gates for essential data, verified administrator succession, minimum audit evidence, privacy obligations, and rollback. The preferred tool is not the one with the longest feature list; it is the one that lets an authorized owner prove control, reproduce the service, retrieve required records, and leave without abandoning customers or evidence.
Sources
- Exporting ticket, user, or organization data from your account — Zendesk Help
- Viewing the audit log for changes to your account — Zendesk Help