Skip to content
Get a quote

Migrate to Zendesk

Zendesk is a multi-channel helpdesk whose import model rewards teams that pre-build ticket forms, ticket fields and brands, and that treat triggers, automations and macros as rebuild work rather than import work.

Short answer

FlitStack AI migrates tickets, threads, and customer histories into Zendesk from 250+ helpdesks, including Intercom, Freshdesk, Gorgias, Kayako. Every field is mapped to Zendesk's objects, history and associations come across, the Zendesk setup is configured alongside, and the whole migration stays reversible in one click.

By

From Any source
DestinationZendesk
IntercomFreshdeskGorgiasKayakoZoho Desk
250+ sources mapped into Zendesk

What Zendesk supports, and where its import tools stop

  • Mature omnichannel routing across email, chat, phone, messaging, and social — one unified inbox for support teams regardless of size or complexity.
  • Deep automation with Triggers, Automations, and SLA Policies lets high-volume teams enforce consistent workflows without manual ticket handling.
  • Large ecosystem of third-party integrations and a public app marketplace reduce friction for teams already using Salesforce, Jira, or Slack.
  • Industry-leading brand recognition and trust signal — many enterprise buyers default to Zendesk as a known quantity in vendor procurement cycles.
REST onlyAPI key or OAuth 2.0
Rate limitsTier-dependent; rate limits vary significantly between Team and Enterprise plans and are not fully publicly documented
ObjectSupportNote
TicketsfullThe central Zendesk object. Every ticket has a requester, assignee, group, status, priority, tags, custom fields, and a chronological comment thread. We map ticket IDs, statuses, timestamps, and comments 1:1; attachments are downloaded and re-hosted on the destination. Plan differences affect available fields (e.g. SLA fields on Enterprise) but the core object migrates cleanly.
Users (End-Users / Requesters)fullZendesk separates end-users (requesters) from agents. We import all requester profiles including name, email, phone, custom fields, and organization membership. Agent vs. end-user role assignment is preserved as a property on the destination record.
Agents (Staff)mappedAgents have roles (admin, agent, light agent, contributor) tied to group memberships. We map agent identities and role assignments but role naming differs by destination CRM — we store the Zendesk role as a custom property and let the destination admin set the equivalent role post-import.
OrganizationsfullZendesk Organizations are shared account/company records that multiple users can belong to. We migrate Organizations with their domain names, details fields, and user memberships intact. Cross-references to custom objects are preserved via lookup fields where the destination supports them.
BrandsmappedBrands are Zendesk's multi-brand abstraction — each brand has its own email addresses, help center, and routing. Brands are gated: Growth/Professional allow up to 5, Enterprise allows up to 300. We migrate Brand assignments on tickets but the destination must support an equivalent multi-brand or tagging strategy.
ViewsmappedViews are saved ticket filters with columns and sort order. We export view definitions (conditions, columns, ordering) as structured data and recreate them on the destination where the target system supports custom ticket list views. Complex nested conditions may simplify on platforms with different filter semantics.
MacrosmappedMacros are canned reply templates with variable placeholders. We export macro content, conditions, and actions. Destination systems map to different concepts (templates, snippets, quick replies) — we map the content and flag which destination object it maps to.
TriggersmappedTriggers fire immediately on ticket events. They reference ticket fields, user fields, and conditions. We export full trigger definitions and attempt to recreate them on the destination. Complex trigger chains and certain condition types may need manual reimplementation depending on the target platform's rule engine.
AutomationsmappedAutomations are time-based and run hourly on up to 1,000 tickets per hour. Zendesk caps 500 active automations per account and each automation must be under 65KB. We export automation definitions and note the hourly batch constraint — destination platforms with no equivalent will need workflow alternatives.
SLA PoliciesmappedSLA Policies define first-response and resolution targets per plan or ticket type. Enterprise-only for the full feature; lower tiers lack SLA management. We migrate SLA definitions as structured records but the destination must support an equivalent SLA engine.
TagsfullZendesk tags are flat string labels applied to tickets, users, and organizations. We migrate all tag assignments and recreate them on the destination platform. Tag naming collisions are handled by appending a source qualifier where needed.
Help Center / Knowledge Base ArticlesmappedArticles live in Sections and Categories within one or more Help Centers (Growth+). Zendesk does not offer a native full KB export. We use the API to pull articles, section hierarchy, translations, and attachments. Content formatting (HTML/Zendesk Markdown) is preserved and converted to the destination's format.
Custom ObjectsmappedCustom Objects (v2 API) are only available on Enterprise and Enterprise Plus plans. They have user-defined schemas with custom fields and lookup relationships to Tickets, Users, or Organizations. We export the schema and all records, then map lookups to the destination's equivalent relational structure.
AttachmentsfullTicket comments and Help Center articles can contain file attachments. We download all attachments from Zendesk via the API, preserve filenames and MIME types, and upload them to the destination using its native file attachment API. Large file batches are chunked to stay within rate limits.
Dynamic ContentmappedDynamic Content holds multilingual placeholder-based text for macros and auto-replies. It is only available on Growth, Professional, and Enterprise plans. We export the item variants (locale + text) and recreate them on the destination, mapping each locale to the target system's equivalent translation object.

The Zendesk migration guide

Why teams migrate to Zendesk

The four shapes a Zendesk migration takes, and what makes the platform easier — or harder — than the category average.

Zendesk, Inc. was founded in Copenhagen, Denmark in 2007 and is headquartered in San Francisco, California. The company went public in 2014 and was taken private in November 2022 by an investor group led by Hellman & Friedman and Permira for roughly $10.2 billion1. The product is now sold primarily as the Zendesk Suite, which bundles Support, Guide, Chat, Talk and Explore under a single subscription.

The typical Zendesk customer is a B2C or B2B support organisation — anywhere from 5 to 5,000 agents — that runs multi-channel inbound volume across email, web widget, mobile, voice, chat and social. Compared with Freshdesk and Help Scout, Zendesk positions itself on workflow depth; compared with ServiceNow CSM and Salesforce Service Cloud, it positions on faster time-to-value and a flatter admin function.

The shapes of migration that actually land on Zendesk tend to fall into four patterns. First, consolidation projects: a company replacing a stack of Intercom plus Help Scout plus a homegrown ticket tool with Zendesk Suite. Second, exits from competing helpdesks — Freshdesk, Front, Kustomer, Gladly — usually triggered by feature gaps in routing, SLAs or Explore-style reporting.

Third, legacy replacements — Jira Service Management, Spiceworks, on-prem ServiceNow, or shared mailboxes — where the source has no real ticket model and the project is really a re-architecture. Fourth, M&A integration, where an acquired business runs on a different helpdesk and the parent standardises on Zendesk. Each shape has a different difficulty profile: a Freshdesk migration has clean ticket-and-user parity but messy tag spillover; a shared-mailbox migration has no schema at all.

What makes migrating to Zendesk easier than the category average is the dedicated Ticket Import path that preserves historical created_at, updated_at and solved_at timestamps, does not fire triggers or automations during import, and accepts batches of up to 100 tickets at a time23.

What makes it harder than the average is that triggers, automations, macros, SLA policies, views and Guide content do not import — they are rebuilt from the source's documentation in Zendesk's own admin UI. Multi-brand customers also discover late that Sandbox availability is plan-gated (Suite Professional and above), which forces some teams to dry-run on production27.

Ticket-field tagging, drop-down tag collisions and the 50-tag-per-ticket cap also reward teams that design the tag taxonomy before the first row is imported.

Teams that scope the trigger, macro and Guide rebuild work up front finish on time; teams that assume parity do not.

The Zendesk data model you need to map into

Tickets, users, organizations, brands, custom objects, and the external-ID keys you'll wire on every field — the destination schema decoded.

Zendesk Support is built around a small set of standard objects, each with default and custom fields, and lookup relationships that connect them. The Suite layer adds Guide articles, Talk calls, Chat conversations and Sunshine custom objects on top of the same shared schema used by Support.

Before you can map a field on the source side, you need to know exactly which destination object the row belongs on, what fields it requires, and which value will serve as its upsert key. The table below summarises the objects you will touch in a Zendesk Suite migration.

ObjectWhat it storesRequiredTier
TicketsSupport requests across all channelsRequester, subject, comment body, statusAll tiers
Users (End users + Agents)Customers, agents, admins, light agentsName + email (or external_id)All tiers
OrganizationsCustomer accounts; group end usersName (unique within instance)All tiers
GroupsAgent assignment groups for routingNameAll tiers
BrandsMulti-brand routing + branded help centersName, subdomainSuite Growth+ (Multi-brand)
Ticket FormsTemplates that scope ticket fields per workflowName, ordered field listSuite Growth+ (multiple forms)
Custom Objects (Sunshine)Customer-defined record typesObject key, name field; plan-scaled fieldsSuite Team+ (counts scale by tier)
Guide articles, sections, categoriesHelp Center knowledge base contentTitle, body, section, localeAll Suites (Guide)
Macros, Triggers, Automations, SLAs, ViewsBusiness rules and routing logicRebuilt manually, not importedAll tiers (Automations: Growth+)

Users use email as the de facto unique identifier, but the most reliable upsert key is external_id — a free-form string you populate from the source system's primary key. Organizations also expose external_id and an organization name that is unique across the instance4.

Tickets are typically matched on the Zendesk-assigned ID after creation, but during a migration the pattern is to stamp the source ticket ID into a custom ticket field (often called legacy_ticket_id) so re-runs and reconciliation are deterministic. Custom objects expose a first-class external_id field designed for exactly this purpose6.

The Data importer upserts on the identifier you nominate: if a matching record exists, it updates; if not, it creates7. The Ticket Import path does not upsert — it always creates — so any re-run requires you to delete failed rows or reconcile by legacy_ticket_id before retrying. Custom field types determine validation; the catalogue below covers what you can model and the limits you plan around.

Field typeLimitNotes
Text / TextareaFree-form stringStandard short and long text
DateYYYY-MM-DDSell importer also accepts DD/MM/YYYY if account timezone matches8
Integer / DecimalStandard numeric rangeDecimal stores numbers with decimal point
CheckboxBoolean + optional tagOptional tag writes a tag to the ticket on true
Dropdown (tagger) / Multi-selectTag value per option, 255-char regex capsEach option writes its tag to the ticket; tags must be unique across all custom fields9
Regexp≤255-char patternRuby regex syntax; validates string input9
Lookup relationshipTargets: ticket, user, organization, custom_object, brand, articleCustom field type lookup; mapped via target object ID10
Ticket fields per account≤400 fields per account, or 400 per formAbove this, performance degrades11
Custom objects per plan3 / 5 / 30 / 30 / 50 / 50Team / Growth / Pro / Support Enterprise / Suite Enterprise / Enterprise Plus12

Relationships in Zendesk are modelled three ways. Tags are the loose-coupling primitive — every ticket can carry up to roughly 50 tags. Lookup relationship fields are first-class typed references between tickets, users, organizations and custom objects, including dynamic filter definitions10. Custom-object parent-child relationships were added in 2024 alongside roll-up summary fields, and many-to-many is modelled via a junction custom object13.

Legacy Sunshine custom objects will be removed in June 202614. Plan to migrate object types, schemas, relationship types and records into the new custom-objects framework before the deprecation deadline, not as part of the cutover itself.

Pre-migration prep — the work before you touch Zendesk

What must be true on the source, the destination, and across the team before the first row hits the Data importer.

The single best predictor of a clean Zendesk migration is how much work you do on the source side before the first import is queued. Help Desk Migration's own playbook notes that roughly 60 percent of total migration effort sits in the pre-transfer phase, and the fix is almost always pre-processing rather than post-cleanup.

Around 60 percent of total migration effort sits before any data moves — the fix is pre-processing, not post-cleanup.

Treat the source export as raw material that needs to be shaped to Zendesk's expected formats — CSV files saved as UTF-8 (not ISO-8859), dates rewritten to match account timezone, email lowercased, tags normalised with dashes instead of spaces, and source ticket IDs preserved in a legacy_ticket_id custom field16.

Source-side prep

  • Audit the ticket estate. Count tickets per channel, per status and per year. Decide what window you actually need in Zendesk — most teams import 2 to 3 years of solved/closed and only the open backlog beyond that.
  • Dedup users by email. Two source rows with [email protected] and [email protected] will collapse into one Zendesk user on import; if you want them separated, deconflict the email before export.
  • Convert tags so they contain no spaces — Zendesk replaces spaces with dashes silently and you lose the ability to filter on the original string.
  • Stamp legacy_ticket_id and legacy_user_id custom fields on every record in the source export so re-runs are deterministic and conversation threads can be linked back to the source if a discrepancy appears post-cutover.
  • Decide what is in scope for ticket comments. Public comments and internal notes are both imported via the ticket comments[] array3; deciding to drop internal notes is a one-time decision that cannot be reversed without a re-import.

Destination-side prep

  • Request a Sandbox if you are on Suite Professional or above — a single Sandbox is allowed at a time, and the typical procedure is to delete the existing one and create a new one based on current production settings18.
  • Enable data imports — they are not enabled by default. The account owner or an admin must contact Zendesk Customer Support to turn on the Data importer and bulk export access7.
  • Disable required conditions on ticket forms during the import window. Required ticket fields will reject historical rows where the source did not capture that value; flip the requirement off in Admin Center → Objects and rules → Tickets → Forms → Conditions before importing, and re-enable after.
  • Provision agents and groups first, ideally through SSO with Okta or Microsoft Entra ID, and create the role assignments before importing — ticket-assignment fails silently if the referenced assignee does not exist in Zendesk.
  • Pre-create every ticket field, ticket form, brand, organization custom field and user custom field with the correct type and tag value. Dropdown tag values must be unique across all custom fields on the account9.

People prep

Cutover only works if humans cooperate. Lock down a source-system freeze window — typically 24 to 72 hours — and communicate it to every channel that touches the inbox. Train agents on the Zendesk macro library, the views they will work from, and the new SLA policies before go-live. A single-brand migration under 10,000 tickets runs one to two business days; a multi-brand, Talk + Chat + Guide consolidation runs two to six weeks.

Import mechanisms: Data importer, Ticket Import, and ETL

Multiple paths in, each with different limits and shapes. Picking the wrong one is how mid-migrations stall at scale.

Zendesk exposes several load paths and the right one depends on dataset size, object mix, and whether you need to re-run idempotently. The native Data importer covers users, organizations and custom-object records up to mid-volume. The Ticket Import path is the sanctioned route for historical tickets at scale. Third-party migration tools sit on top of both and add staging, transformation and reconciliation layers.

Data importer (UI)

The native importer lives at Admin Center → Objects and rules → Tools → Data importer and replaces the legacy Bulk actions page19. It accepts a CSV file (UTF-8 only16) and supports three record types: users, organizations and custom-object records. It does not import tickets — that path is Ticket Import. The legacy bulk-actions page caps at 2,000 rows per file20; the new Data importer benefits from chunking at large volumes.

Bulk export of users via CSV is throttled to 100,000 results per hour per user21. The right call: Data importer for any one-shot users / organizations / custom-object load under a few hundred thousand records where you want a visual mapping review before commit.

Ticket Import

The Ticket Import path is dedicated to moving historical tickets and is documented separately from standard ticket creation3. The bulk form processes up to 100 tickets per batch322.

Unlike standard ticket creation, the import path preserves historical created_at, updated_at and solved_at timestamps, supports an archive_immediately parameter for closed tickets, does not trigger business rules (triggers, automations, notifications) on import, and lets you set custom comment timestamps per element of the comments[] array3. The requester user must already exist in Zendesk — pre-load users via the Data importer first.

Bulk operations that take longer than a single request queue background jobs. The platform ceiling is 30 queued-or-running jobs at once23. Exceeding it returns TooManyJobs; respect the remaining and reset values and back off. Plan-tier throttles sit on top — Team plans run lower request caps than Enterprise23. Choose the programmatic path when ticket volume is over a few thousand.

Third-party migration and ETL tools

Specialist Zendesk-targeted migration tools handle file generation, type coercion, attachment fetching and conversation-thread reconstruction before the result is fed to Zendesk. ETL platforms like Fivetran, Airbyte, Stitch and Talend Data Integration are commonly used for the reverse direction — staging Zendesk data into a warehouse — but on the inbound side they are typically used to land source data into a warehouse, transform in SQL, then push into Zendesk.

Mapping your data into Zendesk

The longest section — because field mapping is where almost every helpdesk migration that fails actually breaks.

Mapping is where every helpdesk migration earns its scars. The schema decisions you make in your mapping spreadsheet determine whether reports work on day two, whether SLA breaches fire correctly on day five, and whether your agents trust the ticket history on day thirty.

Work object by object, top to bottom of the import order: Organizations first (so users can associate), then Users, then Tickets (with comments inline), then Guide content, then Custom Objects.

Users and organizations

Common source → Zendesk User / Organization mapping
SourceDestinationNote
emailemail (primary identity)Lowercased on import; case-only duplicates collapse
source primary keyexternal_id (User / Organization)First-class upsert key — populate on every row
name / full_namenameSingle string; concatenate first + last if needed
phonephoneNormalise to E.164 before import
rolerole (end-user / agent / admin)Agents must hold a paid seat; light agents are read-only on Pro+
account / companyorganization_id via Organization name or external_idPre-load organizations first; user import resolves the FK
custom attributesuser_fields.{key} / organization_fields.{key}Field key must pre-exist; use snake_case lower

Tickets — history, comments and conversation threads

Tickets are the heart of the migration. Every public comment and internal note from the source needs to land in Zendesk's comments[] array in the right chronological order with the right authorship and the right public/private flag. The Ticket Import path accepts a fully composed ticket plus comments in a single payload3, which means you do not have to make a second pass to backfill the conversation thread.

Common source → Zendesk Ticket mapping
SourceDestinationNote
subject / titlesubjectRequired
ticket_idCustom ticket field legacy_ticket_id (regex or text)Zendesk assigns its own ID; keep the source ID for reconciliation
requester_emailrequester_id via user lookupRequester must exist in Zendesk before the import
statusstatusMap to new / open / pending / hold / solved / closed
priorityprioritylow / normal / high / urgent
channel / sourcevia.channel + custom field if richer mapping neededNative channels: email, web, mobile, voice, chat — keep original in a tag if consolidating
created_at, updated_at, solved_atcreated_at, updated_at, solved_atPreserved by Ticket Import; pre-1970 dates rounded to 19703
ticket form (if multi-product)ticket_form_idForm must pre-exist; tag values from form-scoped dropdowns must match
comments[].body + author + is_publiccomments[] with public, author_id, created_atInternal note = public: false; preserve per-comment timestamp3
tagstags[]Replace spaces with dashes; ~50-tag soft cap per ticket
brand (if multi-brand)brand_idBrand must pre-exist; routing follows brand on Growth+
CCs / followerscollaborator_ids / follower_idsAdding on create mirrors notification history
attachmentscomment_attachments via the Uploads pathUpload binary first → receive token → attach to comment

Side Conversations — Zendesk's way to email or message out from a ticket without polluting the main thread — are an under-imported artefact. Most migration tooling collapses them into a private note at the bottom of the ticket because there is no public way to recreate them with their original participant graph intact. Decide whether you accept that trade-off or whether the lost context warrants a manual re-create for high-value historical tickets.

Knowledge base (Guide) — categories, sections, articles, translations

Help Center content imports as categories → sections → articles28. Categories and sections are containers; articles carry the body HTML, locale, draft flag and labels. Translations are imported per-locale through the same path — the UI does not bulk-import translated content, so multi-locale knowledge bases require scripted work28.

Inline image URLs in article bodies need to be rewritten — pointing at the source platform's CDN means the images break the moment that account is cancelled. The pattern is to download every referenced image, re-upload to the Articles Attachments path, capture the new URL, and rewrite the body HTML before insert. Article comments are kept in a separate object and are imported only if your historical knowledge base depended on community discussion.

Macros, Triggers, Automations and SLAs — the rebuild list

Macros (manual actions an agent applies to a ticket), Triggers (event-driven business rules that fire on ticket create or update), Automations (time-based rules that run hourly), SLA policies (response and resolution targets bound to ticket conditions), and Views (saved filters that agents work from) do not import. They are rebuilt from the source platform's documentation in Zendesk's own admin UI.

Plan for this as a parallel workstream, not a post-import task — the rebuild is the work, not the data move. Export the source's automation rules as a spreadsheet with three columns: trigger condition, what it does, who owns it. Filter out anything inactive in the last 90 days. Anything left over is the rebuild backlog. Business hours and schedules are also rebuilt: SLAs reference schedules, so the schedule definitions need to exist before SLA policies are created.

CSAT history and survey responses

Zendesk's CSAT survey writes a satisfaction_rating value (good / bad / offered / unoffered) and an optional comment to the ticket itself. Historical CSAT from a source platform cannot be backfilled into the native satisfaction_rating field on import — the recommended pattern is to land legacy survey scores in a custom ticket field (legacy_csat_score) and a legacy survey comment field, then rewrite historical-period CSAT reports to point at those fields rather than the native one.

Multi-channel inbox setup — Email, Web Widget, Mobile, Voice, Chat, Messaging

The migration moves historical tickets; the live channels still have to be cut over separately. Email is the simplest — point the source mailbox MX or a forwarding rule at {your-subdomain}.zendesk.com. The Web Widget and Mobile clients need to be re-embedded with the new account credentials. Zendesk Talk numbers are ported via a separate carrier porting process that runs in parallel and takes one to four weeks.

Chat (legacy) is being superseded by Messaging (Sunshine Conversations), and many migrations consolidate from third-party chat to Messaging at the same time as the helpdesk move. Social channels (Facebook, X, WhatsApp via Sunshine Conversations) reconnect through the Channel Framework. Brand-specific routing — assigning the right group, ticket form and SLA policy to each brand — is configured in Admin Center → Account → Brand management once Brands are pre-created.

Files, attachments and inline images

Email and web-form attachments cap at 50 MB per inbound file and outbound email attachments cap at around 7 MB total per email29. Attachments are uploaded first, returning a token that you attach to a ticket comment in the same import call. For Guide articles, the per-attachment cap is 20 MB per file or image and community post images are capped at 2 MB30.

Plan for storage tier consumption — Zendesk meters file storage by GB per agent, and the storage dashboard in Admin Center → Account → Usage → Storage refreshes every 24 hours31. For large attachment estates (multi-TB), the pattern most teams adopt is: keep originals in S3 or Azure Blob, store a deep link in a custom ticket field, and only inline-upload the most recent or most-referenced subset to keep storage costs predictable.

Audit trail, ownership and original timestamps

The Ticket Import path is the only route that preserves created_at, updated_at and solved_at on historical tickets — standard ticket creation stamps them to import time. For users and organizations, there is no equivalent override: the Data importer always sets created_at to the moment the row is processed. If you need the original user-created date for reporting, capture it in a legacy_created_at user field.

Ownership during import works through the submitter_id and assignee_id fields on the ticket, both of which must resolve to existing Zendesk user IDs at the moment of import. Rows whose assignee cannot be resolved are imported unassigned, which silently breaks downstream group-based views and reports. The Ticket Audits view exposes the full event timeline post-import32 — useful for reconciliation but not for backfilling: import-generated audits are stamped to import time, not to the source events.

The pitfalls that derail Zendesk migrations

Specific failure modes — ranked by impact, each tied to the exact Zendesk mechanism that breaks.

Validation and cutover

What to verify after the import job, in what order — and how to fail safely when something is wrong.

Validation is the bridge between the import finishing and agents being allowed in. The Supportbench playbook recommends a three-stage validation: a small-scale test load with stakeholder spot-checks, the full load with real-time monitoring of ticket counts and conversation integrity, and a post-migration data-quality audit that runs for 30 days. The most reliable signal is having team leads verify their own ticket queues — they know what right looks like better than any reconciliation script.

Build a reconciliation queries spreadsheet that compares source and destination on each of these counts. Anything outside a 0.5 percent variance gets investigated before agents get login access.

  • Total tickets imported vs source — minus deliberately excluded rows (spam, closed-no-comment, out-of-scope years).
  • Tickets per status (new / open / pending / hold / solved / closed) vs source — a non-trivial drift usually signals a status-mapping error.
  • Tickets per brand and per ticket form vs source — confirms multi-brand routing landed correctly.
  • Comments per ticket — sum of public + private comments vs source, sampled across 100 high-traffic tickets to confirm the comments[] array round-tripped intact.
  • Attachments per ticket — count + bytes; missing attachments are usually a token-expiry or content-type problem on the upload step.
  • Users imported vs source distinct emails — confirms email-case-only collisions did not over-merge.
  • Tags distribution — top 50 tags by frequency vs source; tags with spaces should appear with dashes and counts should match.
  • Original timestamps — sample 50 historical tickets and confirm created_at matches source within 1 second; this is the single most common silent failure on the Ticket Import path.

On top of reconciliation, run a manual spot-check protocol: pick 30 random tickets across statuses, channels and brands and verify each comment, attachment and tag against the source UI. Pick five highest-touch tickets and trace the full conversation graph — every public reply, every internal note, every attachment, every Side Conversation collapse. If a non-trivial discrepancy shows up in three or more of the 30, halt the load, fix the root cause, and re-import the affected rows by legacy_ticket_id.

Zendesk does not offer a native bulk-undo. The Data Recovery Policy is explicit that Zendesk will not restore data the customer deletes36. The supported pattern is: export every object to your own storage before the import starts, stamp every imported ticket with an Import Batch ID custom field, and if catastrophe strikes, bulk-delete by that batch ID and re-import from the cleaned source36.

Cutover sequencing: (1) source helpdesk goes read-only; (2) final delta export captures changes during the test-import window; (3) delta is imported with archive_immediately: true for closed tickets; (4) reconciliation queries run; (5) email MX / forwarding flips to the new Zendesk subdomain; (6) Web Widget and Mobile clients are re-pointed; (7) agents get login with a 48-hour hyper-care window; (8) source decommission is scheduled 30 to 90 days out, never the same day.

Migration partners and tools

Solutions partners, automated migration services, ETL vendors — what each is good for and how to choose.

The Zendesk Solutions Partner Directory tiers Premier, Select and Member partners by certifications, customer count and regional coverage. For a Suite migration specifically, partners with explicit Freshdesk-to-Zendesk, Intercom-to-Zendesk or shared-mailbox-to-Zendesk practices tend to ship cleaner than generalist implementation shops because the failure modes in helpdesk migrations are pattern-matched rather than discovered live.

Alongside certified consultancies, a second category exists: automated migration services that wrap the Ticket Import and Help Center paths in a SaaS UI with field-mapping, demo migrations and delta-sync. These services typically price per-record on a sliding scale, with separate line items for inline-image rebuild, custom-object records, Side Conversations preservation and post-cutover delta runs.

On the ETL and iPaaS side, Fivetran, Airbyte, Stitch, Matillion and Talend Data Integration all have Zendesk connectors. Their role in a migration is rarely the migration itself — it is the staging layer that lands source data into a warehouse, the transformation layer that converts tag conventions and resolves owner IDs, and the ongoing-sync layer that takes over once the one-time migration is complete.

Managed-migration cost ranges vary widely. Automated tool quotes start around $800 for under-10,000-ticket transfers, but practitioners report true project cost lands 4×–40× higher once configuration rebuild, inline-image fixes, retry orchestration and custom-object recovery are factored in. Implementation, migration and training services for enterprise Zendesk deployments are quoted in the $5,000–$50,000+ range. Drivers: ticket volume, custom-field complexity, multi-brand count and integration rebuilds.

For teams that want to outsource the migration end-to-end, FlitStack specialises in Zendesk migrations and handles the field mapping, ticket-history and comment preservation, KB article and inline-image rebuild, custom-object record migration, and validation work described in Sections 5 and 7 of this guide. Pricing is fixed-fee, based on ticket count and source platform, with separate line items for multi-brand setups and Side Conversation preservation so the scope is transparent before signature.

This is one of several legitimate paths — the right choice for any given team depends on whether they want a Zendesk Solutions Partner, an automated migration service, an iPaaS-first approach, or a specialist migration vendor. [Explore FlitStack →](/contact)

Zendesk migration checklist

An exhaustive 8-phase punch list for migrating tickets, users, organizations, knowledge base content, and business rules into Zendesk Support. Typical timeline: 6–16 weeks.

0. Decide & Plan10 tasks
  • Define which Zendesk products are in scope. Document Support, Guide (help center), Talk, Chat/Messaging, Explore, and Sunshine custom objects per product. Each has its own data model and migration path.If skipped: Scope ambiguity around Talk recordings or Sunshine custom objects surfaces mid-migration and stalls cutover.
  • Confirm Zendesk plan tier and product entitlements. Sandbox availability starts at Professional and above; Custom Objects are restricted to Support Enterprise and Suite Team and above; Light Agent seats require Suite Professional or higher.If skipped: Plan-tier limits discovered after contract signing force last-minute upgrades or cut features from scope.
  • Decide the historical-data window per object. State explicitly: how many years of closed tickets, KB article revisions, satisfaction ratings, and Talk recordings move. Closed tickets older than the window stay in archived source exports.If skipped: Pulling all-time history balloons storage usage and migration runtime; pulling too little erodes agent context.
  • Choose data center region for the new Zendesk pod. Zendesk hosts Service Data in AWS regions including US, EU, APJ, and others gated by the Data Center Location add-on. Confirm the region matches data-residency obligations before provisioning.If skipped: Provisioning in the wrong region requires Zendesk Customer Support to spin up a fresh account and reload everything.
  • Capture GDPR, HIPAA, SOC2, and HDS compliance requirements. If PHI is in scope, sign Zendesk's Business Associate Agreement before import. Capture data-retention policy changes that take effect at cutover.If skipped: PHI loaded into an account without an active BAA creates a notifiable breach.
  • Assign a single accountable migration owner (DRI). One named person owns scope, schedule, and sign-off. Multiple stakeholders may contribute, but only one person decides.
  • Document explicit out-of-scope items. List what is NOT migrating: e.g. spam tickets, archived users, deleted KB articles, Talk voicemails older than X months. Get sponsor sign-off on the exclusion list.If skipped: Unwritten exclusions become user complaints after cutover.
  • Set the cutover window and source-system freeze date. Pick a low-volume weekend. Freeze must include source-system writes, automations, and integration triggers.
  • Define written success criteria. Concrete pass/fail thresholds: ticket count delta < 0.1%, KB article count exact match, attachment availability > 99.5%, zero failed user imports, custom field coverage 100%.If skipped: Without numeric criteria the migration is never formally finished and the team keeps firefighting.
  • Identify legal and procurement signoff steps. Surface contract review, DPA execution, BAA execution, and any required security questionnaires before the cutover date.
1. Pre-Migration Prep27 tasks
  • Export current source record counts as a baseline. Capture counts for tickets (open, pending, solved, closed, archived), users (end users, agents, admins), organizations, groups, brands, KB categories/sections/articles, and macros/triggers/automations.If skipped: Without a baseline you cannot prove the migration was complete during Phase 6 reconciliation.
  • Run dedup analysis on source users keyed on lowercase email. Resolve merges in the source before export. Zendesk upsert on email collapses duplicates non-deterministically if both sides have the same address.If skipped: Duplicate users in source cause one agent's tickets to land under the wrong end-user profile.
  • Standardize email casing and trim whitespace on all user records. Lowercase the email column. Trim leading and trailing whitespace. Zendesk treats email matching case-insensitively but external IDs are case-sensitive.
  • Normalize phone numbers to E.164 format. Convert all phone fields to +CountryCodeNumber with no spaces or punctuation. Zendesk Talk requires E.164 for number assignment and outbound routing.If skipped: Mixed phone formats break Talk number lookup and prevent the customer-card phone match from firing.
  • Identify and resolve records missing required fields. Tickets without a requester, users without an email or an external_id, organizations without a name will all fail import.If skipped: Required-field failures abort batches of up to 100 records and force re-batching mid-cutover.
  • Audit tag usage and consolidate. Zendesk does not allow spaces in tags and converts spaces to dashes on import. Inventory tags with spaces or special characters and decide the canonical form before mapping.If skipped: Tag fragmentation post-migration breaks the views, triggers, and reports built on those tags.
  • Flag and remove spam, test, and bot-generated tickets. Decide a cut-off (e.g. tickets from blocked domains, tickets with a single body of 'test', tickets created by deactivated test accounts). Export only what should be preserved.
  • Provision the production Zendesk subdomain. Pick the permanent subdomain. Renaming a subdomain post-launch breaks bookmarks, integrations, and SAML configs.If skipped: A throwaway subdomain locked in by procurement haunts the URL forever.
  • Provision the sandbox environment. Create the standard sandbox from Admin Center on Suite Professional or above. A standard sandbox is a partial clone with no production tickets; verify what does and does not copy over from production config.If skipped: Skipping sandbox work means every problem in Phase 4 is a production-data problem.
  • Contact Zendesk Customer Support to enable data imports. Data imports are disabled by default. The account owner or an admin must open a ticket to enable bulk imports and exports.If skipped: Discovering imports are disabled on cutover day adds a multi-hour support delay.
  • Configure org-level locale, timezone, and business hours. Admin Center > Account > Localization. Timezone affects how created_at and updated_at render and how SLA clocks tick.If skipped: A wrong timezone means every migrated timestamp is off by hours in agent views.
  • Create all Brands before importing tickets. If the source is multi-brand, recreate each Brand in Zendesk first. Tickets carry a brand_id and the brand must exist on import.
  • Create all Groups before importing agents. Groups control ticket routing and visibility. Importing agents into a non-existent group silently drops the group assignment.
  • Create all custom ticket fields with the correct type. Use type checkbox, date, decimal, dropdown, integer, lookup, multiselect, regexp, text, or textarea. Once created the type cannot be changed.If skipped: Wrong field type forces deletion and re-creation, which orphans every reference in existing tickets, triggers, and macros.
  • Create all custom user fields and organization fields. User and organization fields appear on the side panel of every ticket. Build them with the same key names used in source so mapping is mechanical.
  • Bulk-import dropdown and multiselect field options. Per Zendesk, field options can only be CSV-imported during field creation, not after. Build the option list before creating the field.If skipped: Hundreds of options added one-by-one through the UI burns a week and produces typos.
  • Provision Custom Objects and Custom Object fields. Custom Objects are available on Support Enterprise and Suite Team and above. Per-account caps: Suite Team 3 objects, Suite Growth 5, Suite Professional 30, Suite Enterprise 50. Each object holds 100 fields, with 5–10 lookup fields per object depending on tier.If skipped: Hitting the Custom Objects ceiling mid-load forces a schema redesign.
  • Recreate ticket forms and conditional fields. Multi-ticket-form support requires Suite Growth or higher. Build forms to match the source's ticket-type semantics.
  • Disable all conditional 'required' rules on ticket forms during import. Per Zendesk's import guidance, every required condition must be set to Never during the import window. Re-enable required after the load completes.If skipped: Required-field conditions block ticket creation during the import with cryptic validation errors.
  • Create all custom roles with the correct permission matrix. Suite Enterprise supports up to 197 custom agent roles across eight permission categories. Build them before importing agents so role assignment is part of the user load.
  • Decide the Light Agent strategy. Light Agents are free read-only seats on Suite Professional or higher who can be CC'd on internal notes. Map source 'collaborator' or 'view-only' users to Light Agents during import.If skipped: Loading collaborators as full agents inflates the seat count and the bill.
  • Configure SLA policies and Business Hours schedules. SLA Policies require Suite Professional or higher. Create policies plus their underlying Schedules before importing tickets so SLA clocks attach correctly on load.If skipped: Tickets imported before SLA policies exist arrive with no SLA target attached, breaking downstream reports.
  • Set the file-type allowlist on the destination account. Admin Center > Objects and rules > Tickets > Settings > Downloads and attachments. Match the allowlist to the file types present in source export to avoid silent rejection.If skipped: Default allowlist may reject .key, .pages, or other source file types and skip those attachments.
  • Pause all destination-side triggers, automations, and outbound notification rules. Triggers fire on every ticket update; mass import will spam customers with notifications, fire Slack hooks, and re-route tickets. Set every trigger to inactive until cutover validation completes.If skipped: A single 'thank you for contacting us' trigger sends 100k+ emails to customers during import.
  • Announce the source-system freeze window to all users. Communicate twice: 1 week prior and 24 hours prior. State the exact freeze start time and the destination go-live time.
  • Schedule destination-platform training sessions per role. Separate sessions for agents, light agents, admins, and end-user help-center users. Schedule them in the 1–2 weeks before cutover.
  • Designate first-responder agents for the first 48 hours post-cutover. Two to four agents on standby to triage user reports, with a direct Slack channel to the migration DRI.
2. Source Export17 tasks
  • Export the full user list with roles, organization, and custom fields. Include user_id, external_id, email, name, role, organization_id, tags, locale, time_zone, and every custom user field.
  • Export organizations with custom fields and domain mappings. Include organization_id, external_id, name, domain_names, tags, and all custom organization fields. Organizations must load before users that reference them.If skipped: Loading users before their organizations strands the org_id and forces a second pass to backfill.
  • Export groups with member rosters. Capture group_id, name, and the agent-to-group mapping for routing rebuild.
  • Export brands with logos and host mappings. Capture brand_id, name, subdomain or host_mapping, signature, and active state. Reference logos must be re-uploaded; URLs do not transfer.
  • Export all tickets including closed and archived. Use the Incremental Exports path with a start_time cursor for completeness. Search-based exports cap results and miss closed tickets older than 120 days.If skipped: Search-based exports silently drop archived tickets and produce a count mismatch in Phase 6.
  • Export ticket comments (public_comments and internal notes). Capture every comment per ticket along with the public boolean to preserve internal-vs-public on import.If skipped: Collapsing public and internal comments into a single field on import leaks private notes to end users.
  • Export ticket audit events for SLA and timestamp reconstruction. Ticket Audits return create, change, comment, SLA target change, satisfaction rating, and status events. Capture the via.channel object to preserve channel of origin.If skipped: Without the audit log, SLA breach evidence and original channel attribution are lost.
  • Export ticket attachments to local storage as binary files. For each attachment record, follow content_url and download the binary. Preserve the original filename and the parent ticket and comment IDs in a manifest.If skipped: Attachment URLs expire and re-fetch becomes impossible after source cancellation.
  • Export Side Conversations transcripts and attachments. Side Conversations are outbound emails or Slack threads attached to a ticket. Pull every Side Conversation and its events; most destinations do not have a native equivalent.If skipped: Side Conversation context evaporates because the destination has no parallel data structure.
  • Export Sunshine Custom Object types, schemas, and records. Native CSV exports flatten or omit Custom Object data. Use the dedicated Sunshine extract to dump object types, fields, records, and relationship records as JSON.If skipped: Custom Objects vanish from the native export and resurface only after months of post-cutover work.
  • Export Help Center categories, sections, articles, and translations. Extract Help Center categories, sections, articles, and per-article translations. Capture article_attachments separately.
  • Export all macros, triggers, automations, and views. These will be rebuilt, not migrated. Dump them as JSON for reference. Capture trigger conditions, actions, and ordering.
  • Export SLA policies and Business Hours schedules. Capture each policy's filters, target thresholds per priority, and the linked Schedule's time blocks per weekday.
  • Export satisfaction ratings and CSAT comments. Pull every satisfaction rating. CSAT history rarely has a native destination field; plan to land it in a custom field or archive separately.If skipped: CSAT trend data evaporates and the team loses the baseline that informs hiring and quality calibration.
  • Export Zendesk Talk call records, recordings, and voicemails. Capture Voice Comments and the recording URLs. Recordings expire; download binaries during the freeze.
  • Capture screenshots and JSON exports of dashboards, reports, and Explore queries. Reports do not migrate. Capture the configuration so they can be rebuilt in the destination.
  • Stamp every export file with its exact export timestamp. Record start_time and end_time of each Incremental Exports call. This timestamp is the delta cursor for the final pre-cutover top-up.If skipped: Without the cursor, the delta export at cutover either over-pulls and creates duplicates or under-pulls and loses recent tickets.
3. Transform & Map34 tasks
  • Build the master field-mapping spreadsheet. For each source field record: source object, source field, source type, destination object, destination field key, destination type, transformation rule, nullability, and required-on-import flag.If skipped: Without a single source of truth for the mapping, every transformation tweak risks a regression nobody catches.
  • Choose upsert key per object. Use external_id for tickets, users, organizations, and custom object records. For users, email is a secondary unique key; one or the other identifies the record on the Create or Update Many bulk operation.If skipped: Loading without an external_id key makes re-runs duplicate every record.
  • Resolve picklist value mismatches. For every source dropdown, write the source-to-destination value map. Zendesk dropdown values are tags under the hood and tags cannot have spaces; spaces become dashes.If skipped: Unmapped dropdown values arrive as null and reports break silently.
  • Decide handling for source fields with no destination equivalent. Three options per field: drop, concatenate into the first private note, or create a new custom field. Record the decision in the mapping sheet.
  • Reserve tag namespace and prevent collisions. Tags cannot be reused across custom ticket fields. If a tag is used in a checkbox field, it cannot be reused as a dropdown option.If skipped: Tag collisions block future edits to the field configuration and surface as 'tag already in use' errors.
  • Verify ticket-field count stays under the 400-per-account or 400-per-form limit. Zendesk recommends a 400-ticket-field ceiling per account or per form to preserve performance.If skipped: Crossing the limit silently degrades agent UI load times and ticket-form submission reliability.
  • Convert every datetime field to ISO-8601 with explicit timezone offset. Zendesk expects ISO-8601 UTC (e.g. 2026-05-27T14:00:00Z). Native exports may emit account-local timestamps without offset, causing silent timezone drift on import.If skipped: Timestamps imported without offset land in the wrong day in agent views.
  • Re-encode every CSV file as UTF-8. Per Zendesk import errors, files in ISO-8859 or Windows-1252 fail with 'invalid byte sequence in UTF-8'. Pass through Google Sheets or use the CSV UTF-8 export in Excel.If skipped: Encoding errors abort whole files and surface only after the upload completes.
  • Convert date fields in Sell-style imports to match account timezone format. The importer accepts DD/MM/YYYY and MM/DD/YYYY but only if the format matches the account's regional setting. Mismatched format silently flips day and month.If skipped: January 4 imports as April 1 with no error.
  • Truncate string fields exceeding destination character limits. Subject lines, name fields, and most custom text fields have a 255-character cap. Truncate with an explicit ellipsis and log the truncation.
  • Normalize regex-validated field values. Zendesk regex fields use Ruby regex and reject values that fail the pattern. Test every value against the regex before import. Regex patterns are capped at 255 characters.If skipped: A single failing value rejects the entire row.
  • Validate that tags contain no spaces and stay under the 50-tag-per-ticket soft cap. Replace spaces with dashes. Above 50 tags per ticket, performance degrades in views and reports.
  • Escape commas, quotes, and newlines inside CSV cells. Comment bodies frequently contain commas and CRLF sequences that break naive CSV parsers. Use a CSV writer that double-quotes and doubles internal quotes.If skipped: A single ragged comment shifts every column to the right for the rest of the file.
  • Reduce attachment file sizes to fit Zendesk inbound limits. Inbound email and web-form attachments cap at 50 MB per file; outbound email caps at 7 MB per file. Compress, split, or migrate to external storage links anything over the cap.If skipped: Oversize attachments are silently dropped and the linked binary becomes inaccessible.
  • Use the Ticket Import path to preserve original created_at and updated_at. Standard ticket creation stamps created_at to now. The Ticket Import path accepts created_at, updated_at, and solved_at as overrides. Note: timestamps before 1970 are rounded up to 1970.If skipped: Using the wrong load path re-stamps every ticket to migration day, destroying SLA history and tenure context.
  • Set archive_immediately on closed source tickets. When the source ticket is closed, set archive_immediately=true on the Ticket Import call so Zendesk archives the ticket on creation. This avoids quota-burning open-ticket bloat.If skipped: Loading old closed tickets as open inflates the active-ticket dashboard for months.
  • Decide ticket-comment author strategy for missing source users. Comments require an author_id. If the source author was deleted, route the comment to a single 'Data Migration' system user and record the original author name in the comment body.
  • Decide record-ownership strategy for orphaned assignees. If the source assignee no longer exists, assign to a placeholder agent or null assignee. Record the original assignee name in a custom field 'Original Assignee'.
  • Plan attachment re-upload via the dedicated Uploads path. Attachments must be re-uploaded to obtain an upload token, then referenced in the ticket comment payload. External-storage links are an alternative if file sizes exceed limits.
  • Mirror lookup-relationship fields by recreating the references. Lookup fields take type=lookup with relationship_target_type values like zen:user, zen:organization, zen:ticket, or zen:custom_object:{key}. Recreate the same target types in destination and load lookup values in dependency order.If skipped: Lookup fields loaded before the referenced object exists arrive as null and require a second pass.
  • Migrate legacy Sunshine custom objects to the new Custom Objects framework. Per Zendesk, legacy custom objects retire in June 2026 and new creation stops January 15, 2026. Recreate object types in the new Custom Objects framework, recreate relationships as lookup fields on the 'many' side, then load records.If skipped: Building on legacy objects in 2026 means a second migration within months.
  • Reassemble ticket threads with public and internal comments in order. Order comments by created_at ascending. Preserve the public boolean to keep public_comments visible to the requester and internal notes restricted to agents and light agents.If skipped: Out-of-order or mis-flagged comments leak internal commentary to end users on first view.
  • Map Help Center categories, sections, and articles with translations preserved. Help Center hierarchy is Category > Section > Article. Create categories first, then sections inside each category, then articles in each section. Add translations on each article for every locale.If skipped: Loading translations after switching the default locale strands them under the wrong language.
  • Rebuild macros from scratch using the captured JSON. Macros are manual ticket actions. They do not migrate; they must be recreated in Admin Center > Objects and rules > Macros referencing the new field keys.
  • Rebuild triggers with destination field keys, not source field IDs. Triggers are event-driven business rules (fire on ticket create or update). Recreate them with the new ticket-field IDs; copying source trigger JSON verbatim breaks every field reference.
  • Rebuild automations with destination Business Hours. Automations are time-based rules (e.g. close pending tickets after 4 days of inactivity). They depend on a Schedule; create Schedules first, then automations.If skipped: Automations referencing the wrong schedule fire at the wrong time and close tickets prematurely.
  • Decide the SLA-clock strategy for in-flight tickets. Imported open tickets get SLA targets applied based on the active policies and the ticket's current state. Decide whether to override created_at to preserve original SLA clocks or to reset the clock at migration moment.If skipped: Naive load resets every SLA breach counter to zero and erases compliance evidence.
  • Land CSAT history in a custom ticket field if no native target exists. Zendesk's native satisfaction_rating accepts good/bad plus a comment. Source platforms with 5-star or NPS-style ratings should map the original score into a 'Legacy CSAT' integer custom field and the raw response into a text field.
  • Plan email channel cutover including MX record changes. Support email addresses become Zendesk support_address records. To route inbound email through Zendesk, either forward from source mailboxes or repoint MX records. Plan the DNS cutover for the cutover window.If skipped: MX change before Zendesk addresses are verified bounces every customer email.
  • Configure Web Widget and Mobile channels. Generate the Web Widget snippet from Admin Center > Channels > Classic > Web Widget or Messaging. Embed on website before cutover but keep messaging conversation creation disabled until go-live.
  • Port Zendesk Talk phone numbers or order new ones. Talk number porting takes 2–6 weeks with the carrier. Submit Letters of Authorization weeks in advance. For temporary numbers, order Talk numbers and forward source numbers during the freeze.If skipped: Porting timeline ignored means cutover day has no working phone channel.
  • Plan Chat-to-Messaging consolidation. Zendesk Chat (legacy) and Messaging are different products with different data models. Decide whether to consolidate onto Messaging and rebuild flows in the Flow Builder, or maintain Chat parity.
  • Collapse Side Conversations into a private-note transcript. If the destination does not preserve Side Conversations natively, write a single internal note per parent ticket with participants, original timestamps, message bodies, and file references inline.If skipped: Without the collapse, Side Conversation context is dropped silently and agents lose follow-up trails.
  • Map source agent seats to Zendesk seat types including Light Agents. Map full-time support reps to Suite agent seats and read-only contributors to Light Agent seats. Light Agents add CCs and internal notes but cannot own a ticket.If skipped: Loading every contributor as a full agent triples the seat invoice.
4. Sandbox Test Migration12 tasks
  • Load a representative 1–5% sample of each object into sandbox. Use the Ticket Import path in sandbox. Include open tickets, closed tickets, and tickets with side conversations and attachments to exercise every code path.
  • Chunk batches to the 100-record per-request cap. Bulk operations like Create or Update Many cap at 100 items per request. Larger payloads return a 400 Bad Request.If skipped: Exceeding the cap aborts whole batches and forces re-chunking under pressure.
  • Stay within the 30 concurrent jobs ceiling. Background jobs cap at 30 queued or running. Throttle requests against the remaining job count.If skipped: Crossing the limit returns TooManyJobs and silently leaves work unfinished.
  • Validate field-by-field on 10 random sandbox records per object. Open the ticket in agent view. Compare every visible field, including custom fields, side panel user fields, and side panel organization fields, against source.
  • Test edge cases: long strings, special characters, NULL handling. Push a comment with 32 KB of text, a ticket subject with emoji, a custom field with embedded quotes, and a user with a null organization to surface parser quirks.If skipped: Edge cases that pass the sample test still fail at production scale; document and fix each one.
  • Test timezone handling on datetime fields. Pick a ticket with a created_at near midnight UTC and verify it renders on the correct calendar day in agent view.
  • Test attachment re-upload and inline-image rendering. Upload the binary, attach the token to a comment, and confirm the attachment renders in agent view and downloads cleanly. Verify inline images in comment HTML still resolve.If skipped: Inline-image src URLs from source remain pointing at the dead source domain and silently break.
  • Test custom-object lookup relationships. Confirm that a ticket lookup field referencing a Custom Object Record resolves to the correct target record in agent view.
  • Run a full-volume rehearsal on the sandbox if quota allows. Measure throughput (tickets per minute) and total runtime. Extrapolate to production volume. Confirm the cutover window fits.If skipped: Production runtime two times the sandbox estimate blows the cutover window and forces a partial rollback.
  • Verify trigger and automation behavior is fully paused. Create a test ticket via the import path and confirm no triggers fire and no emails go out.If skipped: An active trigger in sandbox is a live trigger in production until the same admin pauses both.
  • Get a domain expert from the support team to spot-check sandbox tickets. A senior agent reviews 20 sandbox tickets end to end: thread completeness, custom field correctness, attachment access, side-conversation reconstruction.
  • Sign off the sandbox test results in writing. Migration DRI and support lead sign a one-page sandbox sign-off document before proceeding to Phase 5.If skipped: Verbal sign-off evaporates and Phase 5 fails because a known issue was 'going to be fixed later'.
5. Production Cutover13 tasks
  • Confirm source-system freeze and verify zero writes in the last hour. Spot-check source audit logs or last-modified timestamps. If writes are still arriving, the freeze is not effective.If skipped: Partial freeze means the delta export misses tickets created during the freeze ramp.
  • Take the final delta export from source using the Phase 2 timestamp cursor. Run the Incremental Exports call with start_time set to the cursor saved at Phase 2 end. This captures every change since the baseline export.
  • Re-confirm all destination triggers, automations, and outbound notification rules are paused. Spot-check Admin Center > Objects and rules and confirm no active rules. A trigger that was paused yesterday may have been re-activated by a colleague.If skipped: An active 'send response' trigger spams thousands of customers within minutes of the first ticket load.
  • Load Brands, Groups, custom fields, and Custom Object types first. These are the schema scaffolding. Every later load references them. Confirm they all exist before the user load.
  • Load Organizations via Create or Update Many Organizations. Key on external_id. Cap at 100 records per request. Capture every job_id for status polling.
  • Load Users via Create or Update Many Users. Key on external_id with email as secondary. Use the data importer for bulk updates. The legacy Bulk actions page caps at 2,000 rows per file.If skipped: Loading users without external_id makes re-runs duplicate every user.
  • Load tickets via the Ticket Import path with archive_immediately on closed tickets. Submit batches up to 100. Set archive_immediately=true for tickets with status=closed. Capture job_ids.If skipped: Using the standard ticket creation path re-stamps created_at to today.
  • Poll job status via Show Many Job Statuses. Poll many jobs in one call. Watch for status=completed with per-record error arrays.
  • Load Custom Object records via Create or Update Many Custom Object Records. Key on external_id. Custom Object records cap at 32 KB each and at 50 million per account.
  • Load Help Center categories, sections, articles, then translations in that order. Hierarchy must exist before children. Translations must reference an existing article_id.If skipped: Loading translations before articles errors out the entire translation batch.
  • Capture every job_id, row count, and error log per load step. Persist to disk. These are the only audit trail of what loaded and what failed.If skipped: Without per-step logs, Phase 6 reconciliation is guesswork.
  • If a load step fails partway, stop and diagnose before continuing. Do not push through with partial data. Fix the transform, re-run idempotently from the last known-good external_id.
  • Reactivate triggers, automations, and outbound notification rules in a staged sequence. Re-enable internal-routing triggers first, then external-notification triggers last. Smoke-test by creating a single test ticket and confirming the expected automations fire and no others.If skipped: Re-enabling every trigger at once detonates queued background jobs and floods customers.
6. Validate18 tasks
  • Compare total record counts per object: source vs. destination. Counts: tickets (by status), users (by role), organizations, groups, brands, KB categories, KB sections, KB articles. Investigate any delta > 0.1%.If skipped: Count mismatches discovered after user access exposes the gap to customers first.
  • Cross-check 25–50 randomly selected tickets field-by-field. Open each in agent view. Compare subject, requester, assignee, status, priority, every custom field, every comment, every attachment against source.
  • Verify open-ticket count matches source. Open + Pending + On-hold ticket counts. Open backlogs are the most operationally sensitive figure.
  • Verify ticket-thread integrity on 20 random tickets. Confirm every comment is present, in order, with the correct public_comments vs internal_note classification.If skipped: A single mis-flagged internal note leaks private commentary to a customer.
  • Verify attachment accessibility on 30 random tickets. Click each attachment in agent view. Confirm it downloads and renders. Verify inline images in comments display.
  • Verify ticket-to-requester and ticket-to-organization links. Sample 25 tickets. Confirm requester resolves to the correct user record and the user's organization is correct.
  • Verify Custom Object Record links from tickets. For every lookup field used, sample tickets and confirm the linked Custom Object Record opens.
  • Verify created_at and solved_at on a sample of imported tickets. Pick 20 closed tickets. Confirm their created_at and solved_at match source. This is the audit-trail-preservation test.If skipped: Re-stamped timestamps invalidate every tenure-of-issue and SLA-breach metric.
  • Verify Side Conversation transcripts landed in private notes. Sample 10 tickets that had Side Conversations in source. Confirm the transcript appears as an internal note with participants and timestamps.
  • Verify Help Center article rendering, including images and links. Sample 25 articles across categories. Confirm inline images render, internal links resolve to the new Help Center URLs, and translations show under the language switcher.If skipped: Broken inline-image src URLs persist post-launch and erode help-center trust.
  • Verify SLA policies attach to imported open tickets. Open 10 imported active tickets and confirm an SLA target shows in the side panel with the correct priority threshold.
  • Verify Business Hours schedule is applied to automations. Trigger a test automation (e.g. close-after-X-days) on a test ticket and confirm it respects the Schedule.
  • Verify CSAT history landed in the Legacy CSAT custom field. Sample 20 tickets with source CSAT and confirm the legacy score is visible to agents.
  • Verify file-attachment file types match the allowlist. Spot-check that .pdf, .png, and any other in-scope types upload and download. Confirm no attachments were rejected silently.
  • Run compliance verification per Phase 0 obligations. Confirm GDPR data-residency region matches expected. Confirm BAA is signed if HIPAA. Capture SOC2 audit evidence (storage region, encryption-at-rest confirmation).
  • Have 3–5 power users from the support team validate day-to-day workflows. Each runs a real ticket end to end: open, comment, side-conversation, status change, close. Document any data or workflow gaps.
  • Document UAT findings and remediate before sign-off. Bug list with priority. Critical and high issues must be fixed before go-live; medium and low can be scheduled for the first 30 days.
  • Get written sign-off from the migration sponsor. A signed go-live decision document. Names the date, the open-issue list, and the rollback decision criteria.If skipped: Without written sign-off, accountability for go-live decisions becomes finger-pointing later.
7. Post-Migration Cleanup12 tasks
  • Announce go-live to all end users. Email or in-app announcement with login URL, where-to-get-help contact, and a 'what's new' brief. Include the Help Center URL.
  • Run agent training sessions segmented by role. Separate sessions for full agents, Light Agents, admins, and supervisors. Cover triggers, macros, side conversations, custom-object workflows.
  • Set the source system to read-only and announce the read-only date. Disable writes via source-system admin settings or revoke write permissions on agents.If skipped: Leaving source writable means agents accidentally update tickets in source post-cutover and lose those updates.
  • Rebuild dashboards and Explore reports. Reports do not migrate. Recreate from the screenshots and JSON captured in Phase 2 using Zendesk Explore for analytics.
  • Re-enable and validate macros in the destination. Have agents run each macro against a test ticket and confirm the actions fire correctly with destination field keys.
  • Re-establish integrations with calendar, email-sync, BI, and CRM systems. Reconnect Slack, Jira, Salesforce, and any other integrations from the Zendesk Marketplace. Each integration needs new credentials.If skipped: Forgotten integrations leak ticket activity to the wrong system or to nowhere.
  • Activate ticket and user deletion schedules per data-retention policy. Admin Center > Account > Data deletion schedules. Configure end-user deletion schedules and ticket deletion schedules to match the retention policy decided in Phase 0.
  • Set Zendesk storage notifications and review storage usage. Admin Center > Account > Usage > Storage. Storage notifications fire above 80% usage; review the 7/30/90-day trend chart weekly for the first month.If skipped: Hitting storage limits silently rejects new attachments.
  • Archive source-system data exports to long-term storage. Move every export file plus the binary attachments to durable archival storage (object storage with versioning). Retention per the policy from Phase 0.If skipped: Without an archive, any audit, dispute, or 'what did the customer originally say' inquiry post-cutover has no source-of-truth.
  • Schedule the 30-day post-migration retrospective. Calendar invite issued on cutover day. Attendees: DRI, support lead, agent first-responders, technical lead. Agenda: what went well, what to do differently, residual data issues.
  • Document and schedule the source-system decommission date. Typically 90 days after cutover. Decommission stops paying for source licenses and removes the temptation to dual-source.
  • Close out the migration project formally. Final status report. Lessons learned. Project closure document signed by the sponsor.

Questions, answered

Migrating to Zendesk: questions

How long does migration to Zendesk take?

A small single-brand migration with under 10,000 tickets and standard objects runs one to two business days end-to-end. A mid-market project with multi-brand routing, Talk + Chat + Guide and historical CSAT runs two to six weeks of elapsed time, including preparation, sandbox dry runs, validation, training and a 48-hour hyper-care window.

Can I migrate from Freshdesk to Zendesk?

Yes — Freshdesk-to-Zendesk is one of the cleanest helpdesk shapes because the object models align closely. Contacts map to End users, Companies to Organizations, Tickets to Tickets, Conversations to Comments. Watch ticket-status terminology drift (Freshdesk Resolved vs Zendesk Solved) and rebuild automation rules from scratch — they do not transfer.

Can I migrate from Intercom to Zendesk?

Yes, and Intercom-to-Zendesk is a common consolidation play. Intercom Conversations become Zendesk Tickets, Companies become Organizations, Contacts become Users. Live-chat conversation threads collapse into ticket comments with timestamps preserved. Plan to rebuild Intercom Bots, Series and qualification flows in Zendesk Messaging — automation logic does not transfer.

Does Zendesk preserve original timestamps on import?

Partially. The Ticket Import path preserves `created_at`, `updated_at` and `solved_at` on tickets, plus per-comment timestamps in the `comments[]` array. But user and organization `created_at` is always stamped to import time. Use a `legacy_created_at` custom field if you need the original date for reporting.

What's the difference between the Data importer and the Ticket Import path for Zendesk?

The Data importer handles users, organizations and custom-object records via CSV with a visual mapping step — but not tickets. The Ticket Import path is the only sanctioned route for historical tickets with original timestamps and comment threads preserved. Most migrations use both: Data importer for people, Ticket Import for tickets.

Can I migrate custom objects to Zendesk?

Yes, but custom-object counts are plan-scaled — 3 on Suite Team, 5 on Growth, 30 on Professional and Support Enterprise, 50 on Suite Enterprise and Enterprise Plus, with 100 fields each. Define the object schema and relationships before importing records. Legacy Sunshine custom objects will be removed in June 2026.

What happens to ticket history and conversation threads during migration?

Ticket history is preserved via the Ticket Import path, including original timestamps and the full `comments[]` array with public replies and internal notes. Side Conversations typically collapse into a private note because there is no public way to recreate them with the original participant graph. Attachments upload separately and attach via token reference.

Is there an undo or rollback for Zendesk imports?

No native bulk-undo exists. The Zendesk Data Recovery Policy is explicit that Zendesk does not restore deleted data. The supported pattern is to export every object before the import starts, stamp imported tickets with an Import Batch ID custom field, and bulk-delete by that field if catastrophe strikes.

Get a quote

Moving to Zendesk?

Tell us where your data lives today and roughly how much there is. We scope the migration and the Zendesk setup with you, then send a quote.

Get a quote