No native migration path exists. Use SurveySparrow's v3 API and HappyFox's v1.1 API for full-fidelity migration. CSV only works for low-risk backfills without comment history or attachments.
There is no native migration path between SurveySparrow Ticket Management and HappyFox — no built-in importer exists on either side, and no major third-party tool offers a verified connector. The fundamental data model challenge is translating SurveySparrow's flat, feedback-driven ticket structure (where tickets originate from survey responses, NPS detractors, and form submissions) into HappyFox's category-based helpdesk model, which requires every ticket to be assigned to a category and organizes contacts into contact groups. HappyFox's support-assisted CSV import only captures the ticket body and at most one collapsed private note — no threaded replies, no attachments — so a custom API-to-API migration using SurveySparrow's REST API v3 and HappyFox's REST API v1.1 is required for any migration demanding full data fidelity.
Read this first
Pair-specific gotchas that catch teams out. Each one has cost somebody a weekend.
No native importer exists
Neither SurveySparrow nor HappyFox offers a built-in migration tool for this direction. HappyFox's support-assisted CSV ticket import only captures the ticket body and optionally one bundled private note — no threaded replies, no attachments. Plan for a custom API-based migration from day one. (support.happyfox.com)
If the SurveySparrow desk was fed by survey submissions or NPS workflows, capture the
If the SurveySparrow desk was fed by survey submissions or NPS workflows, capture the original submission IDs in staging even if HappyFox never surfaces them to agents. They are invaluable for audit and rollback. Store them as a custom text field (e.g., source_submission_id) in HappyFox.
Create custom fields and picklist values in HappyFox before importing tickets
The HappyFox API returns a 400 error with body {"error": "Invalid value for custom field <field_name>"} when a ticket payload includes a custom field value that doesn't match pre-configured options. Use GET /api/1.1/json/ticket_custom_fields/ to retrieve field IDs and valid choices. Dropdown and multi-choice payloads must use target option IDs (integers), not source labels (strings). (developers.surveysparrow.com)
The 10-minute cooldown on HappyFox's 429 response is the single biggest bottleneck for
The 10-minute cooldown on HappyFox's 429 response is the single biggest bottleneck for large migrations. If you hit the rate limit, your entire API access is blocked for 10 full minutes — not just the offending endpoint. Implement exponential backoff and keep POST requests well under 300/min. Target 200/min as a safe operating ceiling. A single cooldown in a 10,000-ticket migration adds 10 minutes of dead time; three cooldowns add 30 minutes.
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 Surveysparrow Ticket Management
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 Surveysparrow Ticket Management → 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.
Surveysparrow Ticket Management → HappyFox specifics
- Scope definition
- Decide if you are migrating all history or only tickets from the last 24 months. Archiving older data reduces API load and migration time. Identify inactive, spam, or junk tickets to exclude. A common rule: exclude tickets with status "Spam" or "Junk" and tickets older than 3 years.
- Category strategy
- Because HappyFox requires categories, audit your SurveySparrow forms, surveys, and teams. Decide how these map to HappyFox Categories (e.g., "NPS Survey" → "Customer Success," "Billing Survey" → "Billing," "Support Form" → "Technical Support"). Document this mapping in a spreadsheet before writing code.
- CRM-like data
- If your SurveySparrow environment includes accounts, leads, or opportunities through custom fields or external syncs, decide where they land. HappyFox does not have a first-class CRM company model — these typically map to contact groups, contact custom fields, or stay in CRM with external ID references stored in a custom field.
- Unused data
- Closed junk tickets, empty custom fields, stale tags, and orphan contacts are cheaper to leave behind than to migrate and clean up later.
- Migration strategy
- Big bang for small desks (under 5,000 tickets); phased for department-by-department moves; incremental when the source must stay live through cutover.
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 Surveysparrow Ticket Management 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 Surveysparrow Ticket Management 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 Surveysparrow Ticket Management 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
Surveysparrow Ticket Management → HappyFox specifics
- Data audit
- Count tickets, public comments, private comments, contacts, attachments, custom fields, teams, statuses, and priorities in SurveySparrow. Export a sample (Settings → Ticket Management → Export Data) to understand field coverage. Record the counts — these become your validation baseline.
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 Surveysparrow Ticket Management → 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 Surveysparrow Ticket Management → 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 Surveysparrow Ticket Management 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 Surveysparrow Ticket Management 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 Surveysparrow Ticket Management read-only rather than cancelled — cancelling the old contract on day one removes your only fallback.
-
Use the source-to-target ledger
to identify all tickets created during the failed run.
Surveysparrow Ticket Management → HappyFox specifics
- HappyFox does not expose a bulk delete endpoint
- in its public API. Individual ticket deletion is available via DELETE /api/1.1/json/ticket/<ticket_id>/ — but this is rate-limited like all other endpoints.
- Contacts do not need rollback
- they are reusable across runs. Your idempotent contact creation logic handles this.
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 Surveysparrow Ticket Management 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 Surveysparrow Ticket Management 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.
Surveysparrow Ticket Management → HappyFox specifics
- API access verification
- Confirm your SurveySparrow plan includes API access (Business tier and above). Confirm your HappyFox plan includes API access — generate credentials via Apps → Goodies → API → Enable. HappyFox sandbox environments are available on Enterprise tiers; request one before starting test migrations.
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.
SurveySparrow Object Equivalent
| Surveysparrow Ticket Management field | HappyFox field | Notes |
|---|---|---|
| Ticket | Ticket | Must be assigned to a HappyFox category (required field) |
| Ticket Comment (public, by requester) | User Reply (user_reply) | Map by author type; use author role/email to distinguish |
| Ticket Comment (public, by agent) | Staff Update (staff_update) | Disable notifications during replay via notify_user: false |
| Ticket Comment (internal) | Private Note (staff_pvtnote) | Preserved via staff update API with private flag |
| Contact | Contact (User) | Email is the unique key on both sides; lowercase and dedupe |
| Contact List | Contact Group | Create groups first, then associate contacts |
| Ticket Field (custom) | Ticket Custom Field | Type matching required; picklist values must pre-exist |
| Contact Property | Contact Custom Field | Map by data type |
| Team | Category or ticket custom field | Routing vs. metadata — decide before migration |
| Ticket Workflow | Smart Rule | Cannot be migrated programmatically; document and rebuild |
| SLA Configuration | SLA Policy | Must be manually recreated; historical SLA breach data does not transfer |
SurveySparrow HappyFox
| Surveysparrow Ticket Management field | HappyFox field | Notes |
|---|---|---|
| ticket.id | Custom field source_ticket_id | Keep original ID for audit, delta sync, and rollback |
| subject | subject | Direct copy |
| description / description_html | text / html | Sanitize HTML (strip <script>, fix broken tags), keep plain text fallback |
| status | status | Map source label to HappyFox status ID via GET /api/1.1/json/statuses/ |
| priority | priority | Map source label to HappyFox priority ID via GET /api/1.1/json/priorities/ |
| assignee | assigned_to | Match by email, resolve to HappyFox staff ID via GET /api/1.1/json/staff/ |
| requester.email | Lowercase, strip whitespace, dedupe; contact must exist before ticket creation | |
| created_at | created_at | HappyFox API supports setting this on ticket creation; both platforms use UTC |
| tags | tags | HappyFox accepts comma-separated tags |
| Custom dropdown | Custom field (choice) | Picklist values must exist in HappyFox first; payload uses target option ID, not source label |
| Custom text | Custom field (text) | Direct copy |
| created_at (per comment) | Embedded in message body | HappyFox reply endpoints do not support per-update timestamp override; prepend [Originally posted: 2024-03-15T14:30:00Z] to message body, or store in a custom field |
Risk matrix
Per-object risk for this pair. Plan extra validation around anything marked high.
| Object | Risk | Notes |
|---|---|---|
| Tickets | medium | Ticket shells can be created via API, but each ticket must be assigned to a HappyFox category that has no direct equivalent in SurveySparrow's flat ticket structure, requiring a manual mapping strategy. |
| Threaded Comments/Replies | high | Each comment must be individually replayed as the correct update type (staff reply, client reply, or private note) via sequential API calls, and the CSV import path collapses all history into a single note. |
| Contacts | low | Contacts can be bulk-imported via CSV/XLS or created through HappyFox's API, though contact list-to-contact group mapping requires pre-planning. |
| Custom Fields | medium | SurveySparrow's ticket custom fields must be recreated in HappyFox with matching types, but HappyFox supports additional types like dependent fields that have no SurveySparrow equivalent, and category-specific scoping adds complexity. |
| Attachments | high | Attachments are completely excluded from the CSV import path and require individual download and multipart re-upload via API, with differing file size limits between platforms. |
| Ticket Statuses and Priorities | low | Both platforms support standard status and priority fields, though custom statuses in SurveySparrow may need to be mapped to HappyFox's configurable status list. |
| Automations/Workflows | high | SurveySparrow's ticket workflows are survey-driven and have no API export, so they must be manually recreated as HappyFox Smart Rules with entirely different trigger and action models. |
| Contact Groups | medium | SurveySparrow contact lists must be mapped to HappyFox contact groups, but the organizational logic differs and HappyFox lacks a first-class CRM company model for account-level data. |
| Agent/Team Assignments | medium | Agent and team assignments must be mapped between platforms, requiring agents to exist in HappyFox before ticket import and teams to be recreated to match the category-based assignment model. |
| Knowledge Base Articles | low | SurveySparrow does not have a core knowledge base feature, so this is typically a fresh content creation effort in HappyFox rather than a migration concern. |
The hard parts
What makes this specific migration difficult, beyond the mechanics.
No Native Migration Path
Neither platform offers a built-in migration tool for this direction, and no verified third-party connector exists, requiring a fully custom API-based approach.
Category Mapping Required
SurveySparrow uses a flat ticket list with no category concept, while HappyFox requires every ticket to be assigned to a category, necessitating a manual mapping strategy from surveys, forms, or teams to HappyFox categories.
Comment Thread Reconstruction
SurveySparrow stores ticket interactions as public and internal comments, which must be individually replayed as correctly typed updates (staff reply, client reply, or private note) in HappyFox via sequential API calls.
Strict HappyFox Rate Limits
HappyFox enforces a 300 POST/min rate limit with a 10-minute cooldown on 429 responses, making large migrations a multi-hour or multi-day process that requires throttling and checkpoint/restart logic.
Attachment Transfer Complexity
Attachments must be downloaded from SurveySparrow and re-uploaded to HappyFox via multipart/form-data POST requests, with differing size limits (15 MB per file vs. 25 MB per request total) adding validation overhead.
Contact Organization Mismatch
SurveySparrow organizes contacts into contact lists with contact properties, while HappyFox uses contact groups with a different custom field schema, requiring transformation of both the grouping structure and field definitions.
Tools used in this playbook
All free, all run entirely in your browser — nothing is uploaded.
FAQ
Can I migrate SurveySparrow tickets to HappyFox with CSV alone?
Only for low-fidelity moves. SurveySparrow can export ticket data in XLSX/JSON, and HappyFox documents a support-assisted CSV ticket migration path, but it treats the first message as the ticket body, can bundle remaining correspondence into one private note, and does not import attachments. An API-based migration is required for full history.
What are HappyFox's API rate limits for ticket migration?
HappyFox allows 500 GET requests per minute and 300 POST requests per minute. Exceeding either triggers a 429 error with a 10-minute cooldown. For bulk ticket creation, you can send up to 100 tickets per request, but attachments are not supported in bulk mode — those require individual multipart/form-data requests.
How do I map SurveySparrow tickets to HappyFox categories?
SurveySparrow does not use categories natively, so you must create routing logic in your migration script. Typically, teams map SurveySparrow form names, survey types, or team assignments to specific HappyFox Category IDs. Pre-create target categories and ensure they are public before loading tickets.
Will historical ticket timestamps be preserved during migration?
HappyFox's API lets you set ticket created_at on ticket creation, so original ticket timestamps can be preserved. However, reply and private-note endpoints do not document a per-update timestamp override, so exact per-reply chronology may require embedding the source timestamp into the message body.
Can I migrate SurveySparrow workflows to HappyFox Smart Rules?
No. SurveySparrow ticket workflows and HappyFox Smart Rules operate on different logic engines. Neither platform exposes automation rules in a format the other can consume. You need to manually document your SurveySparrow workflows and rebuild equivalent Smart Rules in HappyFox after migration.