A Zendesk to HappyFox migration takes 3–10 days for most teams. Biggest risks: Zendesk's 10 req/min limit, expiring attachment URLs, and HappyFox's choice-ID custom field format.
There is no native migration path from Zendesk to HappyFox; all data must be extracted via Zendesk's rate-limited Incremental Export API (10 req/min) and loaded through HappyFox's REST API. The two platforms differ fundamentally in custom field referencing (Zendesk's flat {id, value} pairs vs. HappyFox's t-cf-{id} pattern with choice IDs), organizational hierarchy (Organizations vs. Contact Groups), and ticket ID formatting (sequential numeric vs. category-prefixed composite IDs). Workflow objects such as Triggers, Automations, Macros, and Views have no automated migration path and must be manually rebuilt as Smart Rules, Canned Actions, and Ticket Queues in HappyFox.
Read this first
Pair-specific gotchas that catch teams out. Each one has cost somebody a weekend.
Quick Answer
A Zendesk to HappyFox migration is moderately complex. The hard part is not exporting ticket rows — it is rebuilding comment history, attachments, and custom field mappings between two different help desk models. Zendesk's Incremental Export API caps at 10 requests per minute (30 with the High Volume add-on), attachments must be extracted from individual ticket comments, and HappyFox's custom fields use a t-cf-{id} reference pattern with choice IDs instead of Zendesk's flat {id, value} format. Realistic timeline: 3–10 days for most teams under 100K tickets, 2–4 weeks for enterprise volumes above 250K tickets. The single biggest risk is losing ticket attachments and inline images during extraction. Zendesk Triggers, Automations, Macros, and Views cannot be migrated programmatically — they must be rebuilt manually in HappyFox.
HappyFox's create-ticket API only works in public or contact-visible categories
If your final destination category is private, create the ticket in a temporary public category and move it after creation. This is a documented limitation, not a bug. (support.happyfox.com)
Contact custom field updates can clear omitted values
When updating HappyFox contact custom fields via PUT, send the complete set of custom field values — the API resets fields you omit from the request payload to their defaults. Always merge existing field values with your updates before submitting. (support.happyfox.com)
Concurrent API calls to the same HappyFox ticket are not supported
Parallel writes to the same ticket will fail silently or cause data corruption (duplicate comments, lost attachments, out-of-order threading). Serialize all comment replay calls per ticket. You can parallelize across different tickets — use a worker pool where each worker owns a ticket and processes its comments sequentially. (support.happyfox.com)
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 Zendesk
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 HappyFox can hold your support model
Walk your current workflow through HappyFox: 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 Zendesk → HappyFox 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.
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 Zendesk 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 Zendesk 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 Zendesk 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 Zendesk → HappyFox 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 Zendesk → HappyFox 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 HappyFox 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 HappyFox sandbox that reconciles cleanly and has been reviewed by real agents.
Keep these open
-
Stand up a HappyFox 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 HappyFox'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 HappyFox, 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 Zendesk 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 HappyFox'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 Zendesk 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 Zendesk 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 Zendesk and HappyFox 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 HappyFox, 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 Zendesk 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.
Zendesk HappyFox Object and Field Mapping
| Zendesk field | HappyFox field | Notes |
|---|---|---|
| Tickets | Tickets | Status, priority, and category IDs must be mapped by HappyFox internal ID. HappyFox generates a new id and display_id. |
| Ticket Comments (public, from agent) | Staff Updates (staff_update) | Separate endpoint from private notes. Suppress customer notifications during migration. |
| Ticket Comments (public, from requester) | Contact Replies (user_reply) | Preserves end-user conversation chronology. |
| Internal Notes | Private Notes (staff_pvtnote) | Separate endpoint from public replies. |
| Users (end-users) | Contacts | Email is the unique identifier. Phone fields differ structurally. |
| Users (agents) | Staff | Role and category permissions must be configured manually. |
| Organizations | Contact Groups | Domain-tagged; many-to-many association vs. Zendesk's one-to-one. |
| Groups | Categories + Smart Rules | Agent-routing object, not a customer grouping. HappyFox Categories also control ticket ID prefixes and SLAs. |
| Tags | Tags | Direct migration; tag management permissions may differ. |
| Custom Fields (ticket) | Ticket Custom Fields (t-cf-{id}) | Dropdown/multi-select values must use HappyFox choice IDs, not display text. |
| Custom Fields (user) | Contact Custom Fields (c-cf-{id}) | Same ID-based reference pattern. |
| Attachments | Attachments | Must use multipart/form-data POST; inline images need a separate upload endpoint. |
| Triggers / Automations | Smart Rules | No automated migration path. One Zendesk rule may become multiple Smart Rules. |
| Macros | Canned Actions | Manual recreation required. |
| Views | Ticket Queues / Filters | Manual recreation required. |
| SLA Policies | SLA Configurations | Available on all HappyFox plans; manual setup required. |
| Satisfaction Ratings | Custom Field (text/numeric) | Stored as data but will not drive HappyFox's native survey system. |
| Side Conversations | ❌ No equivalent | Must be flattened into private notes or lost. |
| Webhooks / Targets | ❌ Manual rebuild | See integration migration section below. |
Risk matrix
Per-object risk for this pair. Plan extra validation around anything marked high.
| Object | Risk | Notes |
|---|---|---|
| Tickets | medium | Ticket shells export reliably via the Incremental API, but status, priority, and category IDs must be remapped to HappyFox internal IDs, and original Zendesk ticket IDs cannot be preserved natively. |
| Ticket Comments / Conversation History | medium | Public comments, private notes, and contact replies must be loaded via separate HappyFox endpoints with notification suppression, and long-lived tickets with thousands of comments can dominate extraction time. |
| Attachments | high | Attachments require per-comment extraction with authenticated short-lived URLs that expire if not downloaded immediately, and HappyFox plan-specific size limits can cause silent upload failures. |
| Contacts | low | End-user records map to HappyFox Contacts with email as the unique identifier, though phone field structures differ and contact custom fields require the same ID-based transformation as ticket fields. |
| Custom Fields | high | Every dropdown and multi-select value must be transformed from Zendesk's text-based format to HappyFox's internal choice ID format, with mismatches causing 400 errors and no partial-success fallback. |
| Organizations / Contact Groups | medium | Zendesk's one-to-one Organization model must be restructured into HappyFox's many-to-many Contact Group model with domain-tagged associations, requiring careful relationship remapping. |
| Tags | low | Tags migrate directly between platforms with minimal transformation, though tag management permissions may differ and should be verified post-migration. |
| Triggers / Automations / Macros | high | No automated migration path exists; each rule must be manually rebuilt in HappyFox, and Zendesk's multi-action rules typically expand into 2–5 separate HappyFox Smart Rules. |
| Satisfaction Ratings (CSAT) | medium | Historical CSAT data can only be stored in a custom text or numeric field and will not integrate with HappyFox's native survey system, losing functional continuity. |
| Side Conversations | high | HappyFox has no equivalent to Zendesk Side Conversations; these must be flattened into private notes on the parent ticket or the data will be permanently lost. |
The hard parts
What makes this specific migration difficult, beyond the mechanics.
Custom Field Value Transformation
Every Zendesk custom field value must be converted from flat text-based pairs to HappyFox's choice-ID-based references, requiring a pre-built lookup table mapping display text to internal HappyFox choice IDs to avoid 400 errors.
Attachment Extraction Bottleneck
Attachment binaries are not included in Zendesk's bulk ticket exports and must be downloaded individually from authenticated, short-lived URLs in each ticket comment, making them the single largest source of data loss risk and extraction time.
API Rate Limit Constraints
Zendesk's Incremental Export API is capped at 10 requests per minute globally (30 with the High Volume add-on), which severely throttles extraction speed especially when comments and attachments require per-ticket API calls.
Workflow Rules Manual Rebuild
Zendesk Triggers, Automations, Macros, and Views cannot be migrated programmatically and must be manually recreated in HappyFox, where a single Zendesk rule often expands into 2–5 Smart Rules due to HappyFox's one-action-per-rule limitation.
Status and Ticket ID Mapping
Zendesk's sequential numeric ticket IDs cannot be preserved in HappyFox's category-prefixed composite ID system, and Zendesk's solved/closed statuses must be explicitly mapped to HappyFox's Pending or Completed behavior model.
Organization to Contact Group Mismatch
Zendesk's one-to-one Organization-to-user model must be restructured into HappyFox's many-to-many Contact Group association model with domain-tagged auto-association, requiring careful deduplication and remapping.
Tools used in this playbook
All free, all run entirely in your browser — nothing is uploaded.
FAQ
Can I migrate Zendesk to HappyFox without losing data?
Yes, but only if attachments and inline images are handled correctly during extraction. Zendesk attachment URLs expire quickly and must be downloaded immediately — not queued. Custom field values, tags, and conversation history can all be preserved with proper field mapping. Automation rules (Triggers, Macros, Views) cannot be migrated and must be rebuilt manually in HappyFox.
How long does a Zendesk to HappyFox migration take?
Typical migrations under 100,000 tickets complete in 3–10 days including extraction, transformation, loading, and validation. Enterprise migrations exceeding 250,000 tickets with attachments may take 2–4 weeks. The primary bottleneck is Zendesk's 10 request-per-minute incremental export limit.
What data cannot be migrated from Zendesk to HappyFox?
Zendesk Triggers, Automations, Macros, Views, and Side Conversations have no import path into HappyFox. Ticket metrics like first-reply time are Zendesk-internal audit fields with no write target in HappyFox. CSAT survey responses can be stored in a custom field but won't integrate with HappyFox's native survey system.
Will my Zendesk ticket IDs be preserved in HappyFox?
No. HappyFox generates its own ticket IDs using a category prefix plus a sequential number (e.g., #HFS00000001). To retain the original Zendesk ticket ID for reference, create a custom text field in HappyFox and map the Zendesk ID to it during migration.
Is a CSV export enough for a Zendesk to HappyFox migration?
Usually not if you care about full history. CSV exports strip attachments, break conversation threading, and lose timestamps. A full-fidelity migration requires comment threading, attachment downloads, public/private separation, and endpoint-aware replay via the APIs.