How to Migrate from Zendesk to Chatboq Without Losing Data

Before migrating, a team should audit exactly what data currently lives in Zendesk, decide what genuinely needs to migrate versus what can simply be archived, and set a migration timeline that includes a period of overlap between the two systems rather than a single, high-risk cutover moment.

Auditing your current Zendesk data

A full audit of ticket volume, custom fields, active automation rules, and integrations gives a clear, complete picture of exactly what the migration needs to account for before any technical work begins.

Deciding what to migrate vs archive

Not every piece of historical data needs to live inside the new active system; older tickets with little ongoing relevance can often be exported and archived separately rather than fully migrated, simplifying the overall project.

Setting a migration timeline with overlap

Planning a period where both systems run in parallel, rather than an abrupt single-day cutover, gives the team a safety net to catch and fix migration issues before fully committing to the new platform.

A full migration typically follows seven steps: exporting Zendesk data, mapping Zendesk fields to their Chatboq equivalents, importing historical tickets and conversations, migrating canned responses and macros, recreating automation and routing logic, running both systems in parallel briefly, and finally cutting over and redirecting live channels.

Step 1: Export your Zendesk data

Zendesk provides built-in export tools for tickets, users, and organizations, and starting with a complete, clean export is the foundation the rest of the migration depends on.

Step 2: Map Zendesk fields to Chatboq fields

Creating a clear mapping between each Zendesk field and its Chatboq equivalent, including flagging any fields with no direct match, prevents data from being silently dropped or misplaced during import.

Step 3: Import historical tickets and conversations

Importing the exported ticket history into Chatboq, following the field mapping established in the previous step, should be followed by a spot-check of a sample of imported tickets to confirm data landed correctly.

Step 4: Migrate canned responses and macros

Canned responses and macros generally need to be manually recreated or reformatted for the new platform, since exact automatic translation between platforms' differing structures is rarely available out of the box.

Step 5: Recreate automation rules and routing logic

Automation and routing rules almost always need to be rebuilt natively in the new platform rather than directly imported, since the underlying logic structures differ meaningfully between most help desk systems.

Step 6: Run both systems in parallel briefly

A short parallel-run period, with new conversations flowing into Chatboq while Zendesk remains accessible for reference, catches migration gaps before the team is fully dependent on the new system alone.

Step 7: Cut over and redirect channels

Once the parallel period confirms everything is working correctly, redirecting live channels, chat widget, email routing, and any integrations, fully to Chatboq completes the migration.

The most common migration casualties are custom fields with no direct equivalent in the new platform, automation logic that doesn't translate cleanly between systems, and a break in continuous historical reporting when data structures shift between platforms.

Custom fields with no direct equivalent

A custom field built specifically around Zendesk's own data structure sometimes has no clean one-to-one match in a new platform, requiring a deliberate decision to either recreate it differently or accept the loss of that specific granular data point.

Automation logic that doesn't translate directly

Complex, multi-condition automation rules built up over time in Zendesk often need to be redesigned rather than directly copied, since the underlying automation engines rarely work identically across different platforms.

Historical reporting continuity

Reports that blend pre- and post-migration data can require extra care to reconcile, since a shift in underlying data structure or field naming can otherwise make historical trend lines appear to break or shift artificially at the migration date.

How to Train Your Team on the New System

Training should happen during the parallel-run period, giving agents hands-on time in the new platform on real, low-stakes conversations before they're fully dependent on it, paired with a clear, accessible reference guide covering the specific workflow differences from their old Zendesk habits.

Hands-on practice during the overlap window

Letting agents work directly in the new system on a portion of live traffic during the parallel-run period builds real familiarity before the old system is switched off entirely, rather than a rushed, single training session immediately before cutover.

After cutover, worth confirming: all live channels are correctly routing into the new system, key automation and routing rules are firing as expected, historical data is accurately searchable, and the team has a clear, working escalation path for any issue discovered after the old system is no longer the default.

Verifying the migration truly succeeded

A structured post-migration review, checking channel routing, automation behavior, and searchability of historical data against a checklist rather than assuming everything transferred correctly, catches issues while they're still easy to fix.

The best migration timing avoids a business's known peak season, aligns with an existing contract renewal date to avoid paying for two platforms simultaneously any longer than necessary, and gives the team enough lead time to plan properly rather than rushing under external pressure.

Avoiding peak season migrations

Migrating during a business's busiest period compounds the normal risk of a migration with the added pressure of unusually high support volume, making a quieter season a meaningfully safer window for the project.

Aligning migration with contract renewal dates

Timing a migration to complete before an existing platform's contract renews avoids paying for both systems simultaneously for longer than the planned overlap period actually requires.

Giving the team enough lead time

A migration planned and announced with adequate lead time lets the team properly prepare, rather than being rushed into a compressed timeline that increases the risk of skipped verification steps.

Most platform vendors offer some level of migration assistance, and knowing what that typically covers, what questions to ask before committing to a date, and who internally owns the project are all worth settling clearly before the migration actually begins.

What Chatboq's onboarding team typically helps with

Most platform onboarding teams can assist with field mapping guidance, bulk data import, and initial automation setup, though the specific scope of included support varies by plan, so confirming exactly what's covered before the project starts avoids surprises partway through.

Questions to ask before committing to a migration date

Worth confirming in advance: what data types are supported for automated import, what typically requires manual recreation, and what level of hands-on support is available during the actual cutover window.

Setting internal points of contact

Designating a clear internal project owner, and a small team responsible for verification and troubleshooting during the migration, prevents the kind of confusion that can arise when responsibility for catching issues isn't clearly assigned to anyone specific.

Beyond the core help desk data itself, a migration needs to account for every third-party integration connected to the old system: auditing what's currently connected, reconnecting CRM and ecommerce tools, migrating any custom-built apps, and thoroughly testing every integration before the final cutover.

Auditing existing Zendesk integrations

A full inventory of every connected integration, CRM, ecommerce platform, internal tools, ensures nothing is accidentally left disconnected after cutover simply because it wasn't on anyone's radar during the initial migration planning.

Reconnecting CRM and ecommerce integrations

Core business-critical integrations, particularly CRM and ecommerce platforms feeding customer and order data into support conversations, deserve early, dedicated attention to reconnect and verify well before the final cutover date.

Migrating custom apps or private integrations

Any custom-built app or private integration developed specifically for the old platform generally needs its own dedicated migration or rebuild plan, since it won't transfer automatically the way standard, widely-used integrations often do.

Testing integrations before full cutover

Verifying that every reconnected integration is pulling and pushing data correctly, ideally during the parallel-run period rather than only after full cutover, catches integration issues while the old system is still available as a fallback.

Maintaining meaningful historical reporting through a platform migration requires deliberate planning: exporting key historical reports before the migration begins, rebuilding the most important dashboards natively in the new platform, carefully reconciling how each platform defines its core metrics, and establishing a clear reporting baseline immediately after cutover to measure forward from.

Exporting historical reports before migration

Generating and saving a complete export of key historical reports from the old platform before migration begins provides a permanent, accessible record even if some historical data doesn't transfer perfectly into the new system's native reporting structure.

Rebuilding key dashboards in the new platform

Rather than assuming existing dashboards will translate automatically, deliberately rebuilding the most important ones natively in the new platform, using its own reporting capabilities, ensures the team has accurate, fully functional visibility from the moment of cutover rather than a partially broken approximation.

Reconciling metric definitions between platforms

Two platforms can define what appears to be the same metric, first response time, resolution time, slightly differently under the hood, making it worth explicitly confirming these definitions match, or documenting where they differ, before treating pre- and post-migration data as directly comparable.

Setting a reporting baseline post-migration

Establishing a clear, explicitly marked baseline period immediately following cutover gives the team a clean, unambiguous reference point for measuring future performance, rather than trying to draw a continuous trend line across a period where the underlying data structure meaningfully changed.