tawk.to has no native Zendesk migration path. Export chats/tickets as JSON (50 at a time or via gated REST API), transform to Zendesk's ticket format, and import with preserved timestamps via the Ticket Import API.
Migrating from tawk.to to Zendesk is a fully custom engineering project with no native migration path, no vendor-built connector, and no shared data format between the two platforms. tawk.to is architecturally centered on discrete chat sessions and anonymous website visitors organized by Properties, while Zendesk is built around persistent, named end-user records tied to tickets — meaning every chat session must be transformed into a ticket with a valid requester before import. The tawk.to REST API remains in private beta, making bulk data extraction non-trivial and requiring either manual dashboard exports (capped at 50 messages per batch) or negotiated API access. Custom transformation logic is required to handle anonymous visitors, attachment re-uploads via the Zendesk Uploads API, status remapping, and fields with no Zendesk equivalent such as chat ratings, browser metadata, and agent response times.
Read this first
Pair-specific gotchas that catch teams out. Each one has cost somebody a weekend.
tawk.to chats and tickets are separate object types in the Inbox
Decide early whether you're migrating both, or only tickets. Chats without an associated email address cannot create a valid Zendesk end-user, which means the Ticket Import API will reject them unless you handle anonymous visitors explicitly.
If REST API access is delayed and a support data dump isn't forthcoming, your fallback is
If REST API access is delayed and a support data dump isn't forthcoming, your fallback is the 50-at-a-time dashboard export. For large accounts (10,000+ chats), consider scripting a browser automation tool to batch the manual exports — though this is fragile and not officially supported.
Create a dedicated tag like tawkto_import for all migrated tickets
Zendesk recommends adding a tag to signify these tickets were imported into Zendesk Support and excluding them from any reports that rely on Zendesk-native metrics.
If you're running the import against a production Zendesk instance, disable all triggers
If you're running the import against a production Zendesk instance, disable all triggers and automations before importing. Triggers won't run on imported tickets during import, but if any ticket is updated after import — including by a bulk operation during validation — triggers will resume. An accidental update during validation could fire auto-replies to customers referencing years-old conversations.
The runbook
Work top to bottom. Tick steps as you go — your progress is saved in this browser.
01 Discovery Establish why you are moving, what "done" means, and who signs off.
Objective A written scope with agreed success criteria, a named owner per workstream, and a budget approved by finance.
Keep these open
-
Pull the real numbers out of Tawkto
Export counts for tickets (open and closed separately), contacts, organisations, attachments, macros, triggers, automations, views and SLA policies. Note the oldest ticket date — history depth drives the whole timeline. Estimating from memory is the single most common cause of a blown migration window.
Data Profiler Get real record counts instead of estimating from memory -
Decide what history actually moves
Agree a cut-off with the support lead: all history, last 24 months, or open tickets plus a read-only archive. Every extra year of closed tickets adds API time and cost without adding much agent value. Get this in writing — it is the decision people relitigate mid-cutover.
A "move everything" default is what turns a two-week migration into a two-month one.
COI & ROI Calculator Build the 36-month business case you will need for sign-off -
Confirm Zendesk can hold your support model
Walk your current workflow through Zendesk: multi-brand, business hours, SLA targets, CSAT, side conversations, public vs internal notes, and any channel you depend on (voice, chat, WhatsApp, social). List anything with no native equivalent — those are project risks, not configuration details.
-
Build the business case
Model licence delta, migration effort, agent retraining, and the cost of staying put (Cost of Inaction). Executives approve a number, not a plan, and you will be asked for it again at the go/no-go.
Helpdesk Migration Planner Turn ticket volume into a dated Tawkto → Zendesk timeline -
Name owners and set the go/no-go date
One named owner each for data, configuration, integrations, and agent enablement, plus a decision-maker who can call a rollback. Put the go/no-go meeting in calendars now, 48 hours before the freeze.
Tawkto → Zendesk specifics
- Ticketing maturity
- tawk.to's ticketing is basic — no SLA tracking, no custom ticket statuses, no multi-level prioritization. Zendesk provides full lifecycle ticket management with SLA policies, custom statuses, and conditional forms.
- Reporting and analytics
- tawk.to offers a reporting dashboard but nothing close to Zendesk Explore's custom report builder, cross-channel analytics, or data warehouse export.
- Omnichannel beyond chat
- tawk.to is chat-first. Zendesk Suite bundles email, chat, phone, WhatsApp, social messaging, and a help center into a single agent workspace.
- Integrations ecosystem
- Zendesk's marketplace has 1,500+ apps. tawk.to integrates with fewer tools, and its REST API is still in private beta.
- Scale and compliance
- Larger teams or regulated industries need audit logs, HIPAA eligibility, and role-based access that tawk.to doesn't offer.
Don't move on until
- Record counts confirmed for tickets, contacts, organisations and macros
- Success criteria signed off by the support lead
- Freeze window provisionally booked with the business
02 Data Audit Find out what is actually in the data before you try to move it.
Objective A profiled, cleaned export with every quality defect either fixed at source or explicitly accepted.
Keep these open
-
Take a full Tawkto export and profile it
Export to CSV or JSON and profile every file: row counts, null rates per column, distinct values, and type consistency. Compare row counts against the API totals from Discovery — a gap here means your export is silently truncated, usually by pagination.
Data Profiler Profile the Tawkto export for nulls, outliers and type drift -
Validate file structure before anyone writes a transform
Check delimiters, quoting, encoding (expect UTF-8, watch for BOMs and Latin-1), duplicate headers, and embedded newlines in ticket bodies. Ticket descriptions with raw newlines and commas break naive CSV parsers and silently shift columns.
A single unescaped quote in one ticket body can shift every subsequent column without any error.
CSV Validator Catch broken headers and ragged rows in the raw export -
Inventory PII and set retention
Scan for emails, phone numbers, payment card fragments, national IDs and anything else regulated in ticket bodies and custom fields — support tickets are where customers paste things they should not. Decide what gets migrated, masked, or dropped, and record the legal basis.
Ticket bodies and attachments routinely contain card and ID data that never appears in a structured field.
PII & Compliance Scanner Find regulated fields before they land in a new system -
Quantify duplicates, orphans and dead references
Count duplicate contacts (same email, different casing), tickets whose requester no longer exists, organisations with no members, and attachments whose parent ticket is gone. Fix these in Tawkto where you can — migrating them just moves the mess.
Data Cleaner Strip empty rows, stray whitespace and dead columns -
Clean and normalise the export
Trim whitespace, drop empty rows and columns, normalise casing on emails and tags, and standardise every timestamp to UTC ISO 8601. Timezone drift is invisible at load time and shows up weeks later as SLA reports nobody can reconcile.
-
Produce a masked copy for sandbox work
Generate a realistic but fake version of the export for testing and for any vendor who needs sample data. Loading real customer PII into a sandbox is a breach in most jurisdictions, and sandboxes are rarely covered by your DPA.
PII Masker Generate a safe copy for sandbox and vendor testing
Tawkto → Zendesk specifics
- Pre-migration export
- Export your historical tawk.to data up to a specific cutoff (e.g., Friday at midnight). Set up your webhook receiver to capture anything new during the transition window.
Don't move on until
- Export parses cleanly with no ragged rows or encoding errors
- PII inventory complete and retention decisions recorded
- Duplicate and orphan records quantified and triaged
03 Field Mapping Turn two schemas into one signed-off mapping spec.
Objective A reviewed field-level mapping covering every object, with an explicit decision for every field that has no target.
Keep these open
-
Generate the first-pass Tawkto → Zendesk field map
Start from an automated match on both schemas, then review every row by hand. Automated matching gets the obvious 70% right and is confidently wrong on the rest — especially anything named "type", "status" or "custom_field_1".
Schema Mapper Opens pre-loaded with the Tawkto → Zendesk field pair -
Map status, priority and channel values, not just field names
Enumerate every value in each picklist on both sides and map them explicitly. Value-level mismatches are the defect class that survives all the way to production because the field itself mapped fine — a ticket that should be "Pending" arriving as "Open" reopens SLA clocks.
Statuses with no target equivalent (on-hold, pending-customer) need a policy decision, not a best guess.
-
Decide how custom fields land
Create the target custom fields first, matching type exactly (a dropdown mapped to free text can never be mapped back). Where Zendesk has no equivalent, decide between a new custom field, a tag, or a note appended to the ticket body — and record which.
-
Resolve identity and threading
Decide how source IDs are preserved — most platforms will not let you set the primary key, so keep the original ID in a custom field. Without it, reconciliation becomes fuzzy matching and every future support question about an old ticket is unanswerable.
Losing the original ticket ID makes reconciliation and rollback effectively impossible.
-
Plan attachments, inline images and threading order
Confirm size limits, allowed MIME types, and whether inline images survive as attachments or need rehosting. Decide the comment ordering and author attribution rules: comments loaded out of order, or all attributed to the API user, destroy the conversation history agents rely on.
-
Freeze and sign off the mapping spec
Version the spec, walk the support lead through it row by row, and get explicit sign-off. Any change after this point goes through change control — mid-flight mapping edits are how partial loads happen.
Tawkto → Zendesk specifics
- Custom fields and ticket forms
- If you need custom fields (e.g., tawk.to pageUrl mapped to a URL field, or chat rating mapped to a dropdown), create them now and note the field IDs — you'll need them in the import payload.
Don't move on until
- Every source field is mapped, deliberately dropped, or parked in a custom field
- Status, priority and channel value maps agreed with the support lead
- Mapping spec version-controlled and signed off
04 Test Migration Prove the pipeline on a small, representative slice.
Objective A pilot load into a Zendesk sandbox that reconciles cleanly and has been reviewed by real agents.
Keep these open
-
Stand up a Zendesk sandbox that matches production config
Create the custom fields, groups, brands, business hours and SLA policies first. A pilot into a default sandbox tests nothing, because the failures you care about are all configuration mismatches.
-
Pick a deliberately nasty pilot sample
Take 500-1000 records chosen for difficulty, not convenience: the longest ticket threads, tickets with the most attachments, non-Latin character sets, merged and split tickets, deleted requesters, and every status value. A clean random sample proves only that easy records are easy.
-
Run the load with masked data and instrument everything
Log every API request and response with its source record ID. When 40 records fail out of 10,000 you need to know exactly which ones and why, without re-running the whole batch.
PII Masker Never load real customer PII into a sandbox -
Measure real throughput against the rate limit
Record achieved records-per-hour under Zendesk's actual rate limits, including retries and backoff. Extrapolate to the full volume: if the maths says the full load exceeds your freeze window, you fix that now, not on cutover night.
Published rate limits are ceilings, not throughput. Assume real-world rates are meaningfully lower once retries and backoff are counted.
-
Reconcile the pilot and triage every failure
Diff source against target on record counts and field-level values. Every discrepancy gets a root cause and a fix — "probably fine" at pilot scale becomes thousands of broken records at full scale.
Migration Validation Tool Diff the pilot batch against source before scaling up -
Put real agents in front of the pilot data
Have two or three agents work sample tickets end to end in the sandbox. They find the things reconciliation cannot see: unreadable threading, missing context, macros that no longer make sense. Fix the mapping, then re-run.
-
Enable Sandbox
Zendesk provides a Sandbox environment (available on Suite Growth and above) that mirrors your production configuration. Run your full import pipeline against the Sandbox first.
-
Create a Sandbox reset script
Your import will likely fail on the first run. Script the teardown: delete all tickets tagged tawkto_import, delete synthetic end-users, and reset custom fields before each retry.
-
Import a representative 1% sample first
Before running 50,000 tickets, run 500. Validate the output thoroughly, fix transformation errors, then run the full import.
Tawkto → Zendesk specifics
- Sandbox validation
- Run your full import pipeline against Zendesk Sandbox over the weekend. Fix any errors found.
Don't move on until
- Pilot batch reconciles to 100% on record counts
- Agents have reviewed sample tickets and confirmed they are workable
- Measured throughput extrapolates to a viable full-load window
05 Cutover Execute the switch inside a controlled, reversible window.
Objective All in-scope data live in Zendesk, agents working in the new system, and a rollback path that stayed available throughout.
Keep these open
-
Pre-load history before the freeze
Load closed tickets and contacts days or weeks ahead while Tawkto stays live. Only open tickets and the final delta need to move inside the freeze — this is the single biggest lever on window length.
Helpdesk Migration Planner Size the freeze window from Zendesk's real API limits -
Publish the runbook with times, owners and abort criteria
A timed sequence: freeze start, final export, delta load, channel switch, smoke test, go/no-go, agent switch. Name who does each step and the explicit condition that triggers a rollback. Decide the abort criteria before the night, when nobody wants to be the one to call it.
-
Freeze Tawkto and take the final delta
Stop new ticket creation, let agents finish in-flight replies, then export everything changed since the pre-load. Announce the freeze to the whole business, not just support — someone always tries to raise a ticket during it.
Tickets created during an unenforced freeze land in the old system and are the most common source of permanently lost data.
-
Load the delta and open tickets
Run the delta load, then reconcile counts before touching any channel. Do not repoint email until the delta has verified — an inbound ticket arriving mid-load is far harder to untangle than a few extra minutes of freeze.
Migration Validation Tool Confirm the final delta landed before you reopen -
Repoint channels and verify with live traffic
Switch email forwarding and MX or connector settings, update chat widgets and web forms, and re-authorise integrations. Then send real test tickets through every channel and confirm each lands, routes and triggers the right automation.
Email forwarding changes can take up to a full DNS TTL to propagate — check the TTL days in advance and lower it if needed.
Cron Expression Builder Schedule the delta syncs that run through the freeze -
Run the go/no-go and switch the agents
Walk the exit criteria with the decision-maker, call it explicitly, then move agents over with a named person on hand for the first few hours. Keep Tawkto read-only rather than cancelled — cancelling the old contract on day one removes your only fallback.
Tawkto → Zendesk specifics
- Production import
- Once Sandbox validation passes all checks, run the import against production.
- Widget swap
- Replace the tawk.to JavaScript snippet on your website with the Zendesk Web Widget snippet.
Don't move on until
- Full historical load complete and counts matched
- Inbound channels repointed and verified with live test tickets
- Rollback decision point passed explicitly, not by default
06 Validation Prove the migration is complete, then close it out.
Objective Documented evidence that data, workflow and reporting all survived, and a signed acceptance.
Keep these open
-
Run the full reconciliation
Compare source and target on every object: total counts, counts by status, counts by group, attachment counts, and field-level spot checks on a random sample. Produce one report you can hand to an auditor.
Migration Validation Tool Reconcile Tawkto and Zendesk record-for-record -
Verify field completeness, not just record counts
Re-profile the loaded data and compare null rates per field against the source profile. Matching record counts with a field that silently arrived empty is the failure mode counts alone will never catch.
Data Profiler Prove field completeness held up through the load -
Rebuild reporting and compare against baselines
Recreate your core dashboards — volume, first response time, resolution time, CSAT — and compare to pre-migration figures for the same period. Explain every variance; a changed SLA calculation is a real finding, not a rounding error.
SLA and first-response metrics are usually recalculated from the loaded timestamps, so they will differ if any timestamp mapping was approximate.
-
Test the workflow layer end to end
Fire every trigger, automation, SLA escalation, macro and notification with a live ticket. Workflow does not migrate — it gets rebuilt — so it is untested until someone has actually watched it run.
-
Confirm compliance and produce the audit trail
Re-scan the loaded data for regulated fields, confirm retention and deletion policies are configured in Zendesk, and file the evidence with your PII decisions from the audit phase.
PII & Compliance Scanner Produce the compliance evidence your auditor will ask for -
Sign off, then decommission on a schedule
Get written acceptance against the Discovery success criteria. Keep Tawkto read-only for an agreed period (30-90 days is typical), take a final archive export, and only then cancel. Diarise the decommission date so it does not quietly renew.
-
Record counts
Compare the number of chats + tickets in tawk.to against Zendesk tickets tagged tawkto_import. They must match. If there's a discrepancy, check your import script's error log — 422 rejections are silent unless you capture the response body.
Tawkto → Zendesk specifics
- Timestamp integrity
- Spot-check 20–30 tickets across different date ranges. Verify created_at and comment timestamps match the source data. Pay particular attention to timezone handling — tawk.to exports UTC; confirm your transformation script is not applying local timezone offsets.
- User linkage
- Search for tickets assigned to "(deleted user)" or your default API account. Any such tickets indicate failed requester_id or assignee_id lookups during import.
- Attachment availability
- Open 10–15 tickets with known attachments and verify the files download correctly from Zendesk's CDN. Confirm you're not seeing 404 errors on tawk.to CDN URLs.
- Comment ordering
- Verify that multi-message chats display comments in chronological order. Zendesk orders comments by created_at — if any timestamps are identical or inverted, comments will appear out of order.
- Tag and field accuracy
- Filter by tawkto_import and confirm the tag imported. Spot-check custom field values (e.g., source URL field) on 10 tickets.
Don't move on until
- Full reconciliation report attached to the project record
- Reporting baselines match pre-migration figures within agreed tolerance
- Formal acceptance signed and archive retention scheduled
Field mapping reference
The field-by-field mapping for each object. Use this as the starting point for your mapping spec.
tawk.to Concept Equivalent
| Tawkto field | Zendesk field | Notes |
|---|---|---|
| Property | Brand / Subdomain | tawk.to organizes by "Property" (site). Zendesk uses Brands for multi-site setups. |
| Chat (session) | Ticket | tawk.to chats are discrete sessions. Zendesk treats every interaction as a ticket. |
| Ticket | Ticket | tawk.to tickets are email-based threads; maps directly to Zendesk tickets. |
| Contact / Visitor | End-user | tawk.to auto-creates contacts from chats. Zendesk requires users to exist before ticket import. |
| Department | Group | tawk.to departments → Zendesk groups. |
| Agent | Agent (user role) | Agents must be created in Zendesk before importing tickets they're assigned to. |
| Tag | Tag | Direct 1:1 mapping. |
| Knowledge Base article | Help Center article | No native export for tawk.to KB articles; manual or scrape-based extraction. |
| Shortcut (canned response) | Macro | Must be rebuilt manually in Zendesk. No automated migration path. |
| Priority (Low/Medium/High) | Priority (Low/Normal/High/Urgent) | Zendesk adds "Urgent" level. Map tawk.to's three levels to Zendesk's four. |
Risk matrix
Per-object risk for this pair. Plan extra validation around anything marked high.
| Object | Risk | Notes |
|---|---|---|
| Chat Sessions (Tickets) | high | Chat sessions require the most transformation work of any entity — they must be restructured into Zendesk tickets with valid requesters, have system messages stripped, have statuses remapped, and have attachments separately re-uploaded before the ticket record can be created. |
| Anonymous Visitor Contacts | high | Chat sessions originating from visitors with no captured email address cannot be imported into Zendesk without a placeholder or deduplication strategy, and mishandling them risks either rejected imports or polluted end-user records. |
| Attachments | high | Each attachment must be individually downloaded from the tawk.to CDN and re-uploaded via the Zendesk Uploads API before ticket creation, making this the most operationally fragile step and a likely point of data loss if CDN links expire or rate limits are hit. |
| Email Tickets | medium | tawk.to email tickets map relatively cleanly to Zendesk tickets in terms of subject, body, and status, but status values require transformation ("Closed" → "Solved") and tickets still depend on pre-existing end-user records. |
| Contacts / End-Users | medium | Named contacts with email addresses export cleanly via CSV and map directly to Zendesk end-users, but deduplication must be handled carefully since tawk.to may have created multiple contact records for the same visitor across sessions. |
| Agents | low | Agent records map cleanly by email address and must simply be provisioned in Zendesk before ticket import begins, with no data loss expected for this entity. |
| Tags | low | Tags have a direct 1:1 mapping between tawk.to and Zendesk and can be applied to imported tickets without transformation. |
| Departments / Groups | low | tawk.to departments map cleanly to Zendesk groups and can be created ahead of ticket import with no structural transformation required. |
| Knowledge Base Articles | high | tawk.to provides no UI or API export path for knowledge base articles, requiring web scraping or manual copy-paste as the only extraction methods, making this entity the highest risk for content loss and the most labor-intensive to migrate. |
| Canned Responses / Shortcuts | medium | tawk.to shortcuts have no automated migration path to Zendesk macros and must be rebuilt entirely by hand, with risk proportional to the volume of shortcuts the team has accumulated. |
The hard parts
What makes this specific migration difficult, beyond the mechanics.
No Native Migration Path
There is no vendor-built connector, one-click import tool, or shared data format between tawk.to and Zendesk, requiring a fully custom extraction, transformation, and load pipeline.
Restricted API Data Access
tawk.to's REST API is in private beta and requires a formal access request, leaving dashboard export — capped at 50 messages per batch — as the primary extraction method for most accounts.
Anonymous Visitor Resolution
tawk.to frequently creates chat sessions without capturing a visitor email address, and Zendesk's Ticket Import API requires every ticket to have a valid end-user record with an email, making anonymous chats a blocking data quality problem.
Attachment Re-Upload Requirement
Files attached to tawk.to chats and tickets cannot be bulk-transferred; each attachment must be individually downloaded from tawk.to's CDN and re-uploaded to Zendesk via the Uploads API before the parent ticket is created.
Irrecoverable Field Data Loss
Multiple tawk.to fields — including chat ratings, agent response times per session, visitor browser and OS metadata, and IP addresses — have no equivalent in Zendesk's data model and are permanently dropped unless pre-mapped to custom ticket fields before migration begins.
Pre-Migration User Provisioning
Zendesk requires all end-users and agents to exist as records before tickets referencing them can be imported, meaning a full agent and contact sync must complete successfully before any ticket or chat data is loaded.
Tools used in this playbook
All free, all run entirely in your browser — nothing is uploaded.
FAQ
Can I migrate tawk.to chat history to Zendesk automatically?
No. There is no native connector or one-click tool. You must export tawk.to chats as JSON (manually or via the gated REST API), write a transformation script to map the data to Zendesk's ticket format, and import via the Zendesk Ticket Import API.
How do I export all my data from tawk.to?
Chat and ticket exports are done from the tawk.to Inbox dashboard as JSON files, 50 messages at a time per batch. Contacts export as CSV. For bulk programmatic export, you can request access to tawk.to's private beta REST API, though approval timelines vary. You can also request a full data dump from tawk.to support for high-volume accounts.
Why should I use the Ticket Import API instead of the standard Zendesk Tickets API?
The standard Tickets API overwrites historical timestamps with the current date, triggers all active automations (potentially sending mass emails to customers), and marks all comments as authored by the API administrator. The Ticket Import API preserves created_at timestamps, bypasses triggers, and lets you set author_id per comment.
What happens to tawk.to chats from anonymous visitors without email?
Zendesk requires every ticket to have a valid requester. For anonymous tawk.to visitors, you can create a placeholder end-user, generate synthetic email addresses per visitor ID, or skip anonymous chats entirely if they have no operational value.
How long does a tawk.to to Zendesk migration take?
Small accounts (under 5,000 conversations) can finish in 2–4 days with manual export. Medium accounts (5,000–50,000) typically take 1–2 weeks with scripted extraction. Large accounts (50,000+) may require 2–4 weeks due to tawk.to's export limitations and attachment handling.