Dixa-to-Freshdesk migration requires API-based data transfer in 31-day batches, manual Flow decomposition into three automation engines, and a separate telephony product decision. Plan 4–8 weeks.
There is no native migration path from Dixa to Freshdesk; all data transfer requires API-based extraction, CSV imports, or a combination of both. The fundamental architectural difference is a shift from Dixa's conversation-centric, real-time push-routing model (Flows and Queues) to Freshdesk's ticket-centric helpdesk with three separate automation engines (Dispatch'r, Supervisor, and Observer). Custom work is required to decompose Dixa's unified Flow builder logic across Freshdesk's automation layers, replace Dixa's native telephony with the separate Freshdesk Contact Center product, handle Dixa's 31-day extraction window API constraints, and pre-create all custom field values and dropdown dependencies before data import.
Read this first
Pair-specific gotchas that catch teams out. Each one has cost somebody a weekend.
Timestamp preservation is not straightforward
Freshdesk's Create Ticket API lists created_at and updated_at as response attributes, but community reports and official forums indicate these fields have historically returned validation errors when passed as request parameters on some plans. Test timestamp override in a Freshdesk sandbox before committing to this approach. If per-ticket timestamp override is not available, the fallback is to include the original Dixa timestamp in the ticket subject or a custom field. Per-message timestamp override for replies and notes is even less documented — test this separately.
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 Dixa
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 Freshdesk can hold your support model
Walk your current workflow through Freshdesk: 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 Dixa → Freshdesk 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.
Dixa → Freshdesk specifics
- Routing paradigm shift
- Dixa pushes conversations to agents in real-time via Flows and Queues — the agent accepts or declines. Freshdesk agents work from filtered ticket views, with tickets assigned via Dispatch'r rules, Omniroute (Enterprise only), or manual assignment. The real-time push model does not survive the transition.
- Telephony is a separate product
- Dixa has native built-in telephony. Freshdesk does not — it requires Freshdesk Contact Center (Freshcaller), a separate Freshworks product with its own per-agent and per-minute pricing. (dixa.com)
- Single Flow builder vs. three automation engines
- Dixa has one visual Flow builder for all routing logic. Freshdesk splits automation across Dispatch'r (on-create), Supervisor (time-based, runs hourly), and Observer (on-update events). A single Dixa Flow branch may require rules across all three engines.
- Enterprise plan
- Freshdesk Enterprise includes a built-in sandbox environment (Admin → Account → Sandbox). This creates an isolated copy of your production instance where you can test imports, automations, and field configurations without risk. Changes can be promoted to production selectively.
- Pro plan and below
- No native sandbox. Workarounds: (1) Create a free trial Freshdesk account as a test instance — this gives you 21 days with full feature access. (2) Request a temporary sandbox from Freshdesk sales during migration planning. (3) Use a low-tier paid instance as a dedicated test account.
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 Dixa 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 Dixa 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 Dixa 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
Dixa → Freshdesk specifics
- Assess scope
- Is the issue data-level (field mapping error), automation-level (rules misconfigured), or platform-level (missing feature)?
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 Dixa → Freshdesk 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 Dixa → Freshdesk 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 Freshdesk 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.
Dixa → Freshdesk specifics
- Dixa Conversations → Freshdesk Tickets
- Each conversation becomes one ticket. Map Dixa's open/closed states to Freshdesk's lifecycle statuses (Open = 2, Pending = 3, Resolved = 4, Closed = 5). Dixa's priority levels map to Freshdesk's numeric values (1 = Low, 2 = Medium, 3 = High, 4 = Urgent). Multi-channel Dixa conversations spanning chat and email get a single source field in Freshdesk — set it based on the originating channel.
- Dixa Messages → Freshdesk Ticket Conversations
- Customer replies and agent messages map to Freshdesk public Replies. Internal notes map to Private Notes. Author attribution and timestamps must be set explicitly per message. Important: Dixa's bulk message export does not include internal notes — those are found under conversation_wrapup_notes in the conversations endpoint. (docs.dixa.io)
- Dixa Contacts → Freshdesk Contacts
- Freshdesk contacts are unique by email address and also support unique_external_id, which enables idempotent reloads if you store Dixa source IDs. Dixa's contact model is simpler — map base fields (name, email) and push the rest to custom contact fields. (developers.freshdesk.com)
- Dixa Companies → Freshdesk Companies
- Freshdesk can auto-associate contacts to companies by email domain, simplifying this mapping.
- Dixa Agents → Freshdesk Agents
- Profiles must be recreated. Freshdesk roles are Account Admin, Admin, Supervisor, and Agent. Dixa's agent skill model maps to Freshdesk's Omniroute (Enterprise plan only).
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 Freshdesk sandbox that reconciles cleanly and has been reviewed by real agents.
Keep these open
-
Stand up a Freshdesk 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 Freshdesk'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 Freshdesk, 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 Dixa 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 Freshdesk'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 Dixa 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 Dixa read-only rather than cancelled — cancelling the old contract on day one removes your only fallback.
-
Stop the load process
Log the last successfully migrated record.
Dixa → Freshdesk specifics
- Data-level fix
- Correct the transformation logic, delete affected records via DELETE /api/v2/tickets/{id} (rate-limited; batch carefully), and re-import the corrected subset.
- Automation-level fix
- Disable the misconfigured rules, correct them, and re-test. This doesn't require data rollback.
- Platform-level blocker
- If Freshdesk fundamentally cannot support a critical workflow, pause migration, revert to Dixa operations, and re-evaluate scope.
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 Dixa and Freshdesk 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 Freshdesk, 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 Dixa 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
Risk matrix
Per-object risk for this pair. Plan extra validation around anything marked high.
| Object | Risk | Notes |
|---|---|---|
| Tickets (Conversations) | medium | Conversations map 1:1 to tickets via API, but multi-channel conversations lose channel granularity as Freshdesk reduces them to a single source field, and Dixa's 31-day extraction windows slow the process. |
| Threaded Replies and Notes | medium | Public replies and private notes can be recreated via the Freshdesk Conversations API, but internal notes require a separate Dixa endpoint (conversation_wrapup_notes) and author attribution must be set explicitly per message. |
| Contacts | low | Contacts map cleanly with CSV or API import, Freshdesk enforces uniqueness by email (HTTP 409 on duplicates), and unique_external_id supports idempotent reloads. |
| Companies | low | Companies transfer straightforwardly with Freshdesk's auto-association by email domain simplifying contact-company linkage. |
| Custom Fields | medium | All custom field types require careful type matching, and all dropdown values and dependency trees must be pre-created in Freshdesk before import as the API rejects unrecognized values. |
| Tags | low | Tags transfer directly between platforms, though Freshdesk tags are case-insensitive which may collapse case-variant tags from Dixa. |
| Knowledge Base Articles | medium | Articles can be migrated via the Solutions API into Freshdesk's Category → Folder → Article hierarchy, but images must be re-hosted and all internal links updated. |
| CSAT Scores | high | Historical CSAT scores can only be stored as custom ticket field values and will not appear in Freshdesk's native satisfaction reporting dashboards, losing analytical continuity. |
| Call Recordings | high | Historical recordings cannot be imported into Freshcaller's native storage and must be attached as audio files on tickets or linked as URLs in private notes, breaking native telephony reporting. |
| Routing Rules and Queues | high | Dixa's real-time queue model (offer timeouts, offer algorithms, preferred-agent settings) has no Freshdesk parallel and must be manually redesigned across Groups, Views, Dispatch'r, and Omniroute. |
The hard parts
What makes this specific migration difficult, beyond the mechanics.
Routing Paradigm Redesign Required
Dixa's real-time offer-based routing via Flows and Queues has no direct equivalent in Freshdesk, requiring a complete redesign using Groups, Views, Dispatch'r rules, and Omniroute (Enterprise only).
Three Automation Engines Replace One
A single Dixa Flow branch may need to be decomposed across Freshdesk's Dispatch'r (on-create), Supervisor (hourly time-based), and Observer (on-update) engines, making logic replication complex and error-prone.
Telephony Requires Separate Product
Dixa's native built-in telephony must be replaced by Freshdesk Contact Center (Freshcaller), a separately licensed product requiring IVR rebuilds and number porting that can take 1–3 weeks.
Dixa API Extraction Constraints
Dixa's Exports API enforces 31-day extraction windows with low request rates, meaning large conversation histories must be extracted in sequential time-bounded batches.
Internal Notes in Separate Endpoint
Dixa's bulk message export does not include internal notes, which are stored under conversation_wrapup_notes in a separate conversations endpoint, requiring additional extraction logic to preserve complete conversation context.
Chat Channel Product Split
Dixa's built-in chat widget and in-flow chatbot must be replaced by either Freshdesk Messaging (basic) or Freshchat (full-featured), a separate Freshworks product requiring bot rebuilds with no programmatic migration path.
What breaks
Known failure modes. Have a recovery plan for each before you cut over.
Per-message timestamp preservation:
The Ticket Create API may support created_at, but timestamp override for individual replies via the /reply endpoint is inconsistently documented across API versions. Test in the Freshdesk sandbox. If unsupported, historical replies display the migration date, distorting thread chronology.
Duplicate contacts:
Dixa permits contacts with identical emails; Freshdesk rejects them (HTTP 409). Define a merge strategy — typically retain the most recently updated record — before bulk importing.
Dependent dropdowns:
Freshdesk Pro+ supports cascading dropdowns. The entire dependency tree must be defined and created in the Freshdesk UI before the API will accept payloads referencing those fields.
Attachment size limits:
Freshdesk's API enforces 20MB per attachment. (developers.freshdesk.com) Oversized call recordings and heavily threaded tickets with many files need special handling — consider linking to external storage (S3, GCS) in private notes.
Freshdesk plan feature gaps:
Omniroute (skill-based routing), custom ticket forms, sandbox environments, and higher API rate limits are tier-dependent. Map required features to plan tiers during discovery to avoid surprises mid-migration. Pro ($49/agent/mo) is the minimum for most migrations (custom forms, parent-child tickets, CSAT customization, multilingual KB). Enterprise ($79/agent/mo) adds Omniroute, sandbox, and 700 req/min. Prices as of 2024; verify current pricing.
Freshchat dependency:
If your team relies on Dixa's built-in chat, decide during planning whether Freshdesk's native messaging or a full Freshchat rollout (a separate Freshworks product) is the right replacement. See the Freshchat vs. Freshdesk Messaging analysis above.
Webhook migration:
Dixa webhooks feeding downstream systems (analytics platforms, CRM sync, Slack notifications, custom dashboards) will stop working at cutover. Inventory all webhooks during discovery and rebuild them as Freshdesk webhooks or automation-triggered API calls.
Tools used in this playbook
All free, all run entirely in your browser — nothing is uploaded.
FAQ
How long does a Dixa to Freshdesk migration take?
A typical migration for a 40-agent team with 200K conversations takes 4–8 weeks including discovery, automation redesign, data migration, telephony setup, and validation. The conversation data load alone runs 3–10 days depending on volume and Freshdesk plan rate limits. Flow decomposition is often the critical path at 1–3 weeks.
Can I preserve full Dixa conversation history in Freshdesk?
Yes. Full conversation threads — replies, private notes, and attachments — can be migrated via the Freshdesk API. Each Dixa conversation becomes one Freshdesk ticket with threaded conversations. Ticket-level timestamp preservation via created_at requires testing in a Freshdesk sandbox, as behavior varies by plan. Per-message timestamp override is less documented.
What data can't be migrated from Dixa to Freshdesk?
Dixa Flows, IVR trees, chatbot logic, queue configurations, offer-based assignment, real-time queue metrics, and native telephony infrastructure cannot be migrated programmatically. They must be manually rebuilt in Freshdesk's three automation engines and Freshcaller.
Does Freshdesk replace Dixa's built-in phone system?
No. Freshdesk does not include telephony. You need Freshdesk Contact Center (Freshcaller) — a separate Freshworks product with per-agent and per-minute pricing — or a third-party provider like Aircall or Talkdesk.
Can Dixa Flows be migrated to Freshdesk automations automatically?
No. Each Dixa Flow must be manually decomposed into Freshdesk's three automation engines: Dispatch'r (on-create rules), Supervisor (hourly time-based rules), and Observer (on-update event rules). A single complex Flow may require 5–10 separate Freshdesk rules across all three engines.