A standard migration takes 2–3 weeks. The biggest risk is losing ticket history via native CSV exports; use the HappyFox REST API and Zendesk Ticket Import API instead.
There is no native migration path from HappyFox to Zendesk; the built-in CSV export only captures the initial ticket message and omits all subsequent replies, private notes, and staff responses, making full-fidelity migration dependent on the HappyFox REST API. The fundamental data model differences are significant: HappyFox Categories bundle routing, field scoping, and branding into a single object, while Zendesk splits these concerns across Groups, Brands, and Ticket Forms. Custom work is required to reconstruct full ticket threads via per-ticket API iteration, map category-scoped custom fields to Zendesk Ticket Forms, rebuild all Smart Rules and Canned Actions as Triggers and Macros, and handle attachment downloads before temporary URLs expire.
Read this first
Pair-specific gotchas that catch teams out. Each one has cost somebody a weekend.
Do not map HappyFox Contact Groups to Zendesk Groups
In Zendesk, Groups are agent queues used for ticket routing. HappyFox Contact Groups are end-user visibility constructs and belong in Organizations plus shared-ticket configuration, not in Groups. Confusing these is the single most damaging mapping error in this migration path. (support.happyfox.com)
HappyFox's rate limit penalty is severe
When you exceed the rate limit, the API returns HTTP 429 and blocks all requests for 10 minutes — not just the remaining seconds of the current window. Build conservative throttling (stay at 80% of your limit) or risk long extraction stalls. On a Pro plan (400 req/min), this means capping at ~320 req/min.
The High Volume API add-on replaces your current limit — it does not add to it
It is available on Growth plans and above, requires a minimum of 10 agent seats, and is included by default on Enterprise Plus.
Disable welcome emails before importing users
Zendesk sends verification emails to new users by default when Guide is enabled. Disable this in Admin Center → People → Configuration → "Also send a registration email" before bulk user creation or you will email every imported contact.
Handle empty comment bodies
Zendesk's Import API returns a 422 error for comments with empty or null body/html_body, even though attachment-only updates are valid in HappyFox. Insert placeholder text like "(Attachment only)" for these cases.
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 HappyFox
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 HappyFox → 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.
HappyFox → Zendesk specifics
- Ecosystem and integrations
- Zendesk's marketplace lists over 1,500 pre-built integrations (as of early 2025) compared to HappyFox's approximately 15 native integrations. Teams outgrow HappyFox when they need tighter connections to CRMs, BI tools, or developer platforms.
- API scalability
- HappyFox's API caps at 100–800 requests per minute depending on plan, and exceeding the threshold triggers a full 10-minute lockout. Zendesk's Enterprise plans support 700 req/min with a High Volume add-on path to 2,500 req/min, with no comparable lockout penalty.
- AI and automation maturity
- HappyFox's AI features (AI Copilot, Assist AI, Autopilot) are separate paid add-ons with workflow execution caps. Zendesk bundles AI-powered triage and agent copilot into its Suite plans.
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 HappyFox 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 HappyFox 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 HappyFox 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 -
Contact Group tagged domains
No native Zendesk field. Store as an Organization custom field or in notes.
-
Contact Group ticket visibility by category
Zendesk Organizations can share tickets, but they do not reproduce HappyFox's category-scoped sharing model. (support.happyfox.com)
HappyFox → Zendesk specifics
- Category prefixes and ticket numbers
- Zendesk assigns its own IDs. Preserve the original in external_id.
- Smart Rule and automation logic
- Must be manually reconstructed as Zendesk Triggers and Automations. For guidance, see how to handle automation migration.
- Historical SLA metrics
- Zendesk explicitly does not support SLA metrics on imported tickets. Tag imported tickets and exclude them from SLA reports. (developer.zendesk.com)
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 HappyFox → 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 HappyFox → 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.
HappyFox → Zendesk specifics
- HappyFox parent-child custom field dependencies
- Zendesk supports conditional fields, but the dependency logic must be rebuilt in Ticket Form configuration. Nested multi-level dependencies (3+ levels) may require flattening.
- Category-scoped custom fields
- Maps to Zendesk Ticket Forms, available on Professional plans and above.
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.
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 HappyFox 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 HappyFox 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 HappyFox 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 HappyFox 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 HappyFox 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.
How Do HappyFox Objects Map Zendesk
| HappyFox field | Zendesk field | Notes |
|---|---|---|
| Tickets | Tickets | Use /api/v2/imports/tickets to preserve created_at, updated_at, and solved_at |
| Ticket Updates (replies) | Public Comments | Preserve author_id and comment created_at |
| Ticket Updates (private notes) | Internal Comments | Set public: false |
| Categories | Groups + Ticket Forms | One Category may split across Group (routing) and Ticket Form (field visibility) |
| Contacts | Users (end-users) | Zendesk requires unique email addresses; deduplicate before import |
| Contact Groups | Organizations | tagged_domains has no native Zendesk equivalent — store as org custom field |
| Staff (Agents) | Users (agents) | Create before tickets; HappyFox category-level permissions have no Zendesk equivalent |
| Brands | Brands | Pre-create in Zendesk before cutover if you use multi-brand (Enterprise plan required) |
| Ticket Custom Fields | Custom Ticket Fields | Parent-child dependent fields require Zendesk conditional fields (Professional+) |
| Contact Custom Fields | Custom User Fields | Field type mapping: text→text, dropdown→dropdown, number→decimal, date→date |
| Tags | Tags | Direct 1:1 mapping; normalize casing and remove dead tags |
| Priorities | Priority (system field) | HappyFox supports custom priorities; Zendesk has 4 fixed levels (Low, Normal, High, Urgent) |
| Statuses | Ticket Statuses | HappyFox supports custom statuses; Zendesk added custom statuses — map names carefully |
| Canned Actions | Macros | Cannot be exported via API — must be rebuilt manually |
| Smart Rules | Triggers / Automations | Cannot be exported via API — must be rebuilt manually |
| SLAs | SLA Policies | Cannot be migrated; Zendesk does not support SLA metrics for imported tickets |
| Knowledge Base | Zendesk Guide (Articles) | Requires separate migration using Help Center API; HTML may need sanitization |
| Satisfaction Surveys | CSAT (built-in) | Historical survey data cannot be migrated; export and archive separately |
| Assets | Custom Objects | Requires Zendesk Custom Objects API (/api/v2/custom_objects) |
| Attachments | Attachments | Must be downloaded from HappyFox during extraction and re-uploaded via Zendesk Upload API |
Create Cus m Fields in Zendesk
| HappyFox field | Zendesk field | Notes |
|---|---|---|
| Text | Text | Direct mapping |
| Dropdown (choice) | Drop-down | Recreate all option values; HappyFox uses option IDs, Zendesk uses tag values |
| Number | Decimal or Integer | Zendesk distinguishes between decimal and integer |
| Date | Date | Format differences may require transformation (HappyFox uses ISO 8601) |
| Multi-select | Multi-select | Available on Professional+ plans |
| Checkbox | Checkbox | Direct mapping |
Risk matrix
Per-object risk for this pair. Plan extra validation around anything marked high.
| Object | Risk | Notes |
|---|---|---|
| Tickets | medium | Tickets can be migrated using Zendesk's Ticket Import API to preserve timestamps, but full thread extraction requires per-ticket API calls with careful rate-limit management. |
| Ticket Conversation History | high | The native CSV export excludes all replies and private notes after ticket creation, making full thread fidelity entirely dependent on API extraction and correct author-to-comment mapping. |
| Contacts | medium | Contacts map to Zendesk end-users but require deduplication on unique email addresses before import, as Zendesk enforces email uniqueness that HappyFox may not. |
| Custom Fields | high | HappyFox's category-scoped custom fields with parent-child dependencies and option-ID-based values require restructuring into globally defined Zendesk fields with Ticket Form visibility and tag-based dropdown values. |
| Categories | high | Categories have no single Zendesk equivalent and must be decomposed across Groups, Brands, and Ticket Forms, requiring structural design decisions that affect routing, field visibility, and portal separation. |
| Contact Groups | medium | Contact Groups map to Zendesk Organizations but lose tagged-domain functionality and category-scoped ticket visibility, which must be approximated through custom fields and shared-ticket settings. |
| Tags | low | Tags map directly 1:1 between platforms and require only case normalization and cleanup of unused tags before import. |
| Knowledge Base Articles | medium | Articles require separate migration via the Help Center API with HTML content sanitization, and the export process is decoupled from the ticket migration workflow. |
| Attachments | high | Attachment URLs from HappyFox expire within approximately 15–30 minutes, requiring real-time download during extraction and re-upload via Zendesk's Upload API with no opportunity for deferred processing. |
| Automations and Macros | high | Smart Rules and Canned Actions cannot be exported via the HappyFox API and must be manually audited and rebuilt as Zendesk Triggers, Automations, and Macros from scratch. |
The hard parts
What makes this specific migration difficult, beyond the mechanics.
Incomplete Native CSV Export
HappyFox's CSV export includes only the initial ticket message and omits all staff replies, client replies, and private notes, requiring full thread extraction via the REST API on a per-ticket basis.
Category-to-Multi-Object Mapping
HappyFox Categories combine routing, field scoping, brand association, and ticket prefixes into one object, which must be decomposed into Zendesk Groups, Brands, and Ticket Forms with no automated mapping path.
Severe API Rate Limit Penalties
Exceeding HappyFox's API rate limit triggers a full 10-minute lockout on all requests rather than a brief cooldown, requiring conservative throttling at 80% capacity to avoid prolonged extraction stalls.
Expiring Attachment URLs
HappyFox attachment URLs include temporary access credentials that expire within approximately 15–30 minutes, requiring attachments to be downloaded inline during extraction rather than in a separate pass.
Automation and SLA Rebuild
Smart Rules, Canned Actions, SLA policies, and satisfaction survey configurations cannot be exported via API and must be manually reconstructed as Zendesk Triggers, Macros, Automations, and SLA Policies.
Contact Group Mapping Complexity
HappyFox Contact Groups use tagged domains and category-scoped ticket visibility with no direct Zendesk equivalent, requiring mapping to Organizations with custom fields and manual shared-ticket configuration.
Tools used in this playbook
All free, all run entirely in your browser — nothing is uploaded.
FAQ
Can I migrate HappyFox to Zendesk without losing data?
Yes, but only if you use the HappyFox REST API for extraction and Zendesk's Ticket Import API for loading. HappyFox's native CSV export drops all replies and private notes after the initial message. The API path preserves full ticket threads, custom fields, tags, and attachments.
How long does a HappyFox to Zendesk migration take?
A typical migration of 10,000–50,000 tickets takes 2–3 weeks including discovery, development, testing, and cutover. Datasets under 5,000 tickets can complete in under a week. Enterprise migrations with 100K+ tickets and complex custom fields may take 3–4 weeks.
Can HappyFox ticket history be preserved in Zendesk?
Yes. The Zendesk Ticket Import API (/api/v2/imports/tickets) lets you set created_at, updated_at, and solved_at on both tickets and individual comments. This preserves the original timeline. The standard Tickets API does not support backdating — only the Import API does.
What data cannot be migrated from HappyFox to Zendesk?
Smart Rules (automations), SLA policies, Canned Actions (macros), satisfaction survey responses, and agent workflow configurations cannot be exported via API and must be rebuilt manually in Zendesk. Zendesk also warns that SLA metrics are not supported for imported tickets.
Does Zendesk have a native HappyFox import tool?
No. Zendesk's native Data Importer handles users, organizations, and custom object records but cannot import tickets. There is no built-in HappyFox connector. Full ticket migration requires the Ticket Import API.