There is no native import path from tawk.to to Freshchat. Every migration requires custom ETL — extract via dashboard export or gated REST API, transform to Freshchat's message_parts schema, and load via the v2 API.
There is no native migration path, vendor-supported connector, or one-click import tool between tawk.to and Freshchat—every migration is a custom engineering project. The fundamental data model challenge is translating tawk.to's session-based, property-centric chat architecture into Freshchat's persistent user-conversation model with structured message_parts. Custom work is required for data extraction (complicated by tawk.to's gated, beta-status REST API), schema transformation, attachment handling, agent attribution mapping, and API-driven import into Freshchat, with tawk.to Tickets and Knowledge Base articles having no direct Freshchat equivalent and requiring Freshdesk instead.
Read this first
Pair-specific gotchas that catch teams out. Each one has cost somebody a weekend.
tawk.to Tickets (email-based support threads) have no direct equivalent in Freshchat
Freshchat is a messaging platform, not a ticketing system. If you rely on tawk.to's ticketing, you need Freshdesk alongside Freshchat, or Freshworks Customer Service Suite.
The Timestamp Constraint
Freshchat's created_time on messages and conversations is system-generated and not exposed as a request input in the public API. (developers.freshchat.com) To preserve the historical timestamp of a tawk.to message, prepend the original timestamp as text within the message body during migration (e.g., [Original Time: 2023-04-12 14:32] Client: Hello). This is a workaround, not a native feature. Messages will appear in the Freshchat UI with their import timestamp, not their original timestamp.
Custom conversation properties with the cf_ prefix are documented only for chat accounts
Custom conversation properties with the cf_ prefix are documented only for chat accounts that are part of Freshsales Suite, not standalone Freshchat. (developers.freshchat.com) If you need custom data on conversations in standalone Freshchat, verify what your plan supports before building your mapping.
Freshchat's Messages API has a max items_per_page of 50
When importing conversations with more than 50 messages, create the conversation first, then append additional messages via POST /conversations/{id}/messages in batches.
This is an outline, not production code
Real implementations need exponential backoff, checkpoint/resume logic for recovering from mid-migration failures, attachment handling, dead-letter queues for failed records, and comprehensive error logging.
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 Freshchat can hold your support model
Walk your current workflow through Freshchat: 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 → Freshchat 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 → Freshchat specifics
- Omnichannel consolidation
- tawk.to is primarily web chat. Freshchat covers WhatsApp, Facebook Messenger, Instagram, Apple Business Chat, email, and mobile SDK — all in one inbox.
- Freshworks ecosystem integration
- Teams already on Freshdesk, Freshsales, or Freshworks CRM want their chat tool tightly coupled with ticketing and CRM data.
- AI and automation
- Freshchat's Freddy AI is included in paid plans. tawk.to charges separately for AI, and its automation capabilities are more limited.
- Scalability and routing
- As teams grow past 10+ agents, tawk.to's reporting and routing become limiting. Freshchat offers assignment rules, IntelliAssign, and CSAT flows natively.
- API maturity
- tawk.to's REST API is still in private beta with a gated approval process. Freshchat provides a documented, publicly accessible REST API.
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
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 → Freshchat 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 → Freshchat 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 Freshchat 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.
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 Freshchat sandbox that reconciles cleanly and has been reviewed by real agents.
Keep these open
-
Stand up a Freshchat 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 Freshchat'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.
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 Freshchat, 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 Freshchat'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.
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 Freshchat 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 Freshchat, 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.
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.
Data Type tawk.to Location
| Tawkto field | Freshchat field | Notes |
|---|---|---|
| Live chat conversations | Inbox → Chats | Core migration target |
| Chat messages + timestamps | Within each chat | Map to Freshchat message_parts |
| Tickets (email threads) | Inbox → Tickets | Freshchat doesn't handle tickets — route to Freshdesk if needed |
| Contacts | People → Contacts | CSV export lacks custom attributes |
| Organizations | Linked to contacts | Map to Freshchat contact properties |
| Tags | Applied to chats/tickets | Recreate as Freshchat conversation properties |
| Custom attributes | Contact profiles | Must extract via API or manual pull |
| Knowledge Base articles | KB section | KB belongs in Freshdesk, not Freshchat |
| Agents / Departments | Admin settings | Create manually in Freshchat |
| Shortcuts (canned responses) | Admin → Shortcuts | Recreate in Freshchat as canned responses |
| Automations / Triggers | Admin settings | No migration path — rebuild in Freshchat |
tawk.to Freshchat
| Tawkto field | Freshchat field | Notes |
|---|---|---|
| Contact Name | first_name + last_name | Split on first space |
| Contact Email | email + reference_id | Direct map; use email as dedup key |
| Contact Phone | phone | Direct map |
| Organization | properties.organization | Define as custom property first |
| Custom Attributes | properties.* | Define each in Freshchat before import |
| Country / City | properties.country, properties.city | Define as custom properties |
| Chat Message Text | message_parts [].text.content | Wrap in message_parts; prepend historical timestamp |
| Chat Sender (visitor) | actor_type: "user", actor_id | Lookup from contacts map |
| Chat Sender (agent) | actor_type: "agent", actor_id | Lookup from agents map |
| Chat ID | Custom property or reference_id | Store source ID for audit trails |
| Department | Group assignment (assigned_group_id) | Map via UUID lookup table |
| Tag | Conversation property | Recreate as property |
| Attachment URL | message_parts [].image.url or file | Download + re-upload |
Risk matrix
Per-object risk for this pair. Plan extra validation around anything marked high.
| Object | Risk | Notes |
|---|---|---|
| Chat Conversations | high | Translating tawk.to's session-based chats into Freshchat's persistent conversation model requires complex structural transformation, and dashboard exports are limited to 50 messages per batch, making large-scale extraction error-prone. |
| Contacts / Visitors | medium | Basic contact fields export via CSV, but custom attributes are excluded from dashboard exports, requiring API access or manual supplementation to preserve the full contact profile. |
| Custom Attributes | high | Custom attribute data is confirmed by tawk.to support to be absent from contact CSV exports, and API extraction may also require separate handling, creating a significant data loss risk. |
| Attachments | high | Exports contain only attachment metadata and URLs rather than actual files, and tawk.to-hosted URLs may expire or become inaccessible after account changes, requiring proactive download and re-upload. |
| Agent Attribution | medium | Agent names are included in chat exports but must be mapped to corresponding Freshchat agent IDs, requiring a pre-built crosswalk table and handling of agents who may not exist in the target system. |
| Tags | low | Tags export cleanly in chat JSON data and map relatively directly to Freshchat conversation properties or tags with minimal transformation required. |
| Departments / Groups | medium | tawk.to Departments must be mapped to Freshchat Groups, which requires pre-creating the group structure in Freshchat and maintaining an ID mapping table for conversation assignment. |
| Tickets | high | tawk.to's email-based Tickets have no equivalent in Freshchat and must be migrated to Freshdesk instead, requiring an entirely separate migration pipeline and target system. |
| Knowledge Base Articles | high | Freshchat has no native Knowledge Base feature, so tawk.to KB articles must be migrated to Freshdesk or another platform, adding scope and complexity to the project. |
| Timestamps / Chronology | medium | Original message timestamps are preserved in exports, but importing them into Freshchat requires careful handling to maintain conversation chronology and avoid the API defaulting to import-time timestamps. |
The hard parts
What makes this specific migration difficult, beyond the mechanics.
Gated tawk.to API Access
tawk.to's REST API requires a formal approval process with reported wait times of months to over a year, making programmatic data extraction unreliable to plan around.
Session-to-Persistent Model Mapping
tawk.to treats chats as discrete, isolated sessions tied to visitors and properties, while Freshchat organizes data around persistent users and ongoing conversation threads, requiring complex structural transformation.
Ticket and KB Incompatibility
tawk.to Tickets (email-based support threads) and Knowledge Base articles have no direct equivalent in Freshchat and must be migrated separately to Freshdesk or Freshworks Customer Service Suite.
Custom Attributes Data Loss
Custom attribute data on tawk.to contacts is not included in dashboard CSV exports and may require separate extraction even via the API, risking data loss during migration.
Attachment URL Expiration
tawk.to exports include attachment metadata and URLs but not the actual files, requiring separate downloads and re-uploads before source URLs expire or become inaccessible.
Message Schema Transformation
tawk.to's flat message structure with sender type and text fields must be transformed into Freshchat's message_parts schema with proper actor attribution, requiring significant mapping logic.
Tools used in this playbook
All free, all run entirely in your browser — nothing is uploaded.
FAQ
Can I directly import tawk.to chats into Freshchat?
No. There is no native import tool, connector, or CSV upload that maps tawk.to data into Freshchat. You need to export from tawk.to (JSON via dashboard or REST API), transform the data to match Freshchat's conversation schema, and import via the Freshchat REST API.
Does tawk.to have a public API for data export?
tawk.to has a REST API, but it is in private beta and requires a formal access request. Approval can take weeks to months, and some users report waiting over a year. The API documentation is only shared after approval. For migration purposes, you may need to rely on manual dashboard exports (JSON/CSV) as a fallback.
How do I retain the original timestamps of my tawk.to chats in Freshchat?
Freshchat's API sets created_time as a system-generated field and does not accept historical timestamps as input. The workaround is to prepend the original historical timestamp as text within the message body during migration (e.g., '[Original Time: 2023-04-12 14:32] Client: Hello').
What tawk.to data cannot be migrated to Freshchat?
Freshchat does not support ticketing or Knowledge Base articles — those belong to Freshdesk. tawk.to tickets, KB content, satisfaction survey results, and chat analytics have no direct equivalent in Freshchat. Custom attributes on contacts are also excluded from tawk.to's CSV export and require API access or manual extraction.
How long does a tawk.to to Freshchat migration take?
It depends on data volume and method. A small account (under 5,000 conversations) can be migrated in 1–3 days. Mid-size accounts (5K–50K conversations) typically take 3–7 days including validation. Enterprise-scale migrations may take 1–2 weeks. Working with a managed migration service typically compresses timelines.