HappyFox to Missive requires an API pipeline — CSV exports lose history. Rate limits and 5-minute attachment URL expiry are the top technical constraints.
There is no native migration path from HappyFox to Missive. HappyFox is a traditional ticket-based helpdesk built around numbered, stateful tickets with rich metadata (priorities, SLAs, custom fields, categories), while Missive is a collaborative email client organized around lightweight conversations in shared inboxes. Migrating between them requires an API-based or custom ETL approach to extract full ticket threads from HappyFox's REST API and reconstruct them as Missive conversations via the Posts or Custom Channel Messages endpoint, with significant metadata loss or flattening inevitable due to fundamental data model differences.
Read this first
Pair-specific gotchas that catch teams out. Each one has cost somebody a weekend.
The biggest structural gap
HappyFox tickets carry rich metadata — priority, SLA timers, custom fields, due dates, satisfaction ratings. Missive conversations are intentionally lightweight. Much of this metadata will be lost or must be flattened into labels, contact notes, or posts. Define what you are willing to lose before you start.
Category → Label vs. Team decision
If your HappyFox categories represent routing queues (Sales, Support, Billing), map them to Missive Teams. If they represent topic tags that can overlap, map them to Shared Labels. Most teams use a combination.
Rate limit math
At a sustained 1 request/second (the safe rate for Missive), migrating 30,000 tickets with an average of 5 messages each requires ~240,000 API calls. That is roughly 67 hours of continuous, throttled API calls — just for the message import. See the throughput calculation section above for full sizing methodology.
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 Missive can hold your support model
Walk your current workflow through Missive: 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 → Missive 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 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
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 → Missive 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 → Missive 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 Missive 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.
-
Map to Labels
Convert custom field values into Missive labels (e.g., a "Plan Type: Enterprise" field becomes a "Plan: Enterprise" label).
Data Format Converter Reshape the export into the format Missive's importer expects -
Flatten into the first Post body
as structured text for historical reference.
JSON to CSV Converter Flatten nested API responses into a reviewable sheet
HappyFox → Missive specifics
- Store in contact-level fields
- if the data belongs to the customer rather than the ticket.
- Accept the loss
- if the field data is no longer operationally relevant.
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 Missive sandbox that reconciles cleanly and has been reviewed by real agents.
Keep these open
-
Stand up a Missive 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 Missive'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 Missive, 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 Missive'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 Missive 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 Missive, 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.
Object Equivalent
| HappyFox field | Missive field | Notes |
|---|---|---|
| Ticket | Conversation | Core unit. Each ticket becomes one conversation. |
| Ticket Updates (replies, notes) | Messages / Posts within a conversation | Use Messages endpoint for custom channels or Posts for injected content. |
| Contact | Contact (in a Contact Book) | Direct mapping. Create shared contact books first. |
| Contact Group | Contact Group or Company | HappyFox contact groups can affect ticket visibility; Missive companies provide organization context, groups act as tags, and routing belongs in team inboxes. (support.happyfox.com) |
| Category | Shared Label or Team | Structural decision — see callout below. |
| Status | Conversation state | Open → Inbox, Closed → Closed, Pending → Snoozed |
| Priority | Shared Label | No native priority. Use labels like "Priority: High". |
| Agent | User (assignee) | Map HappyFox agent emails to Missive user IDs. |
| Agent Group | Team | HappyFox agent groups map to Missive teams. |
| Tag | Shared Label | Tags become organization labels. |
| Custom Field (ticket) | Post content or Contact field | Ticket-level custom fields have no native home — flatten into post body or contact metadata. |
| Custom Field (contact) | Contact field | Direct mapping where types align. |
| Knowledge Base Article | No equivalent | Missive has no built-in KB. Export to a separate tool. |
| Canned Action | Canned Response | Manual recreation required. |
| Smart Rule | Rule | Manual recreation required. Rules require Productive plan or higher. |
| SLA | No equivalent | Use Rules with time-based conditions as a workaround. |
HappyFox Missive
| HappyFox field | Missive field | Notes |
|---|---|---|
| id (ticket) | External reference in Post body | Store as metadata for traceability |
| display_id | Label or subject prefix | Preserves original ticket ID for search |
| subject | Conversation subject | Direct |
| text (initial message) | First message body | Direct |
| updates [].message | Subsequent messages | Ordered by timestamp |
| updates [].timestamp | delivered_at (Unix timestamp) | Convert to epoch seconds |
| updates [].by | from_field | Map to contact or agent |
| status.name | Conversation state | Map: Open → inbox, Closed → close action |
| priority.name | Shared label | Create "Priority: X" labels |
| category.name | Shared label or Team | Structural decision |
| tags [] | Shared labels | One label per tag |
| assigned_to.email | add_assignees | Map to Missive user ID |
| contact.name | first_name + last_name | Split on space |
| contact.email | Contact email | Direct |
| contact.phone | Contact phone | Direct |
| attachments [].url | Re-uploaded attachment | Download immediately, re-attach |
| custom_fields [] | Contact field / Label / Post body | Flatten only high-value fields |
Risk matrix
Per-object risk for this pair. Plan extra validation around anything marked high.
| Object | Risk | Notes |
|---|---|---|
| Tickets / Conversations | high | Tickets must be reconstructed as Missive conversations via API with significant metadata loss (priority, SLA timers, due dates, satisfaction ratings), and threads exceeding 400 messages must be split. |
| Contacts | low | Contact data (name, email, phone, company) maps well between platforms and can be migrated via CSV import or Missive's Contacts API with minimal transformation. |
| Contact Groups | low | HappyFox contact groups can be mapped to Missive's contact books, companies, and groups with straightforward relational mapping. |
| Custom Fields | high | Ticket-level custom fields have no equivalent in Missive and must be flattened into labels, contact notes, or post body content, resulting in loss of structured queryability. |
| Categories | medium | HappyFox's hierarchical categories must be flattened into Missive's shared labels, losing parent-child relationships and requiring a deliberate naming convention to preserve hierarchy context. |
| Tags | low | HappyFox tags map naturally to Missive shared labels, though deduplication against migrated categories is needed to avoid label sprawl. |
| Attachments | high | HappyFox attachment URLs expire in 5 minutes, requiring immediate download and re-upload during extraction, with any pipeline delay risking permanent attachment loss. |
| Knowledge Base Articles | high | Missive has no built-in knowledge base, so KB articles cannot be migrated and must be redirected to an entirely separate platform. |
| Automations / Smart Rules | medium | HappyFox smart rules and SLA workflows must be manually recreated as Missive rules, with some trigger and action types having no equivalent — and custom channel conversations do not support Missive Rules at all. |
| Ticket Statuses and Priorities | medium | HappyFox's granular statuses (Open, Pending, On Hold, Resolved, Closed) and four-tier priorities must be compressed into Missive's simpler Inbox/Closed/Snoozed/Trashed states with no native priority field. |
The hard parts
What makes this specific migration difficult, beyond the mechanics.
Fundamentally Different Data Models
HappyFox's stateful tickets with priorities, SLAs, due dates, and hierarchical categories must be mapped to Missive's intentionally lightweight conversations that lack native priority fields, SLA tracking, and ticket-level custom fields.
Attachment URL Expiration
HappyFox attachment download URLs expire in just 5 minutes, requiring the migration pipeline to download and re-upload attachments in near-real-time during extraction.
Missive API Rate Limits
Missive enforces a hard limit of 900 requests per 15 minutes (effectively 1 request/second sustained), making large migrations extremely time-intensive — a 30,000-ticket migration requires approximately 67 hours of continuous API loading.
Conversation Message Hard Limit
Missive enforces a 400-message-per-conversation limit, meaning long-running HappyFox tickets with extensive update histories may need to be split across multiple conversations, breaking thread continuity.
Custom Field Model Mismatch
HappyFox supports custom fields at both the ticket level and contact level, while Missive only supports contact-level custom fields, forcing ticket-level metadata to be flattened into labels, contact notes, or posts.
No Knowledge Base Equivalent
Missive has no built-in knowledge base, so HappyFox KB articles with categories cannot be migrated into Missive and must be redirected to an external documentation platform.
Tools used in this playbook
All free, all run entirely in your browser — nothing is uploaded.
FAQ
Can I migrate HappyFox tickets to Missive using CSV export?
Not if you need conversation history. HappyFox's native CSV export only includes the initial message and subject — it strips staff replies, client replies, and private notes. Missive's self-serve CSV import only supports contacts, not conversations. You must use the HappyFox REST API (v1.1) to extract full ticket threads for any meaningful migration.
Does Missive have a ticket import API?
No. Missive has no dedicated ticket import endpoint. You need to use the Messages endpoint (for custom channels) or the Posts endpoint to inject historical conversation data. Each message requires a separate API call, and rate limits cap you at 300 requests per minute and 900 requests per 15 minutes.
How long does a HappyFox to Missive migration take?
For a mid-size dataset of 10,000–50,000 tickets, expect 2–4 weeks including planning, scripting, test migration, validation, and cutover. The actual data transfer can take multiple days due to Missive's API rate limits.
What HappyFox data cannot be migrated to Missive?
Missive has no equivalent for HappyFox's SLA timers, satisfaction survey results, ticket priority fields, knowledge base, asset management, or ticket-level custom fields. Priority can be approximated with labels, but SLA and CSAT data must be archived separately.
Do I need a paid Missive plan to migrate data via API?
Yes. Missive API access requires the Productive plan or higher. All API tokens are personal — there is no organization-level service account — so you need a licensed user to generate the token used for migration.