SurveySparrow tickets must be decomposed into Missive conversations via the Posts API. No native importer exists. Budget 1–5 days depending on volume, and map statuses to shared labels.
Migrating from SurveySparrow Ticket Management (SparrowDesk) to Missive requires a fully custom API-based engineering effort, as no native migration path or built-in importer exists on either platform. The two systems operate on fundamentally different architectural models: SurveySparrow uses a flat, ticket-centric schema with explicit status enums, priority fields, and single-assignee ownership, while Missive is a conversation-centric collaborative inbox where state is expressed through mailbox placement and there is no native ticket, priority, or custom field construct. Data must be extracted ticket-by-ticket via SurveySparrow's v3 REST API (the v1 API was deprecated December 31, 2024), transformed to decompose flat ticket schemas into Missive's conversation model, and loaded one conversation at a time through Missive's Posts API or Messages API. Custom field values, priority, SLA timestamps, and parent-child ticket relationships all require explicit transformation logic, as Missive has no direct equivalents for these constructs.
Read this first
Pair-specific gotchas that catch teams out. Each one has cost somebody a weekend.
No native importer exists
Neither SurveySparrow nor Missive offers a built-in migration tool for this direction. SurveySparrow supports ticket export in Excel (xlsx) and JSON format via Settings → Ticket Management → Export Data, and CSV export from the ticket list view — but these exports do not include complete threaded replies or attachment binary files (only URLs). Missive has no bulk historical conversation import endpoint. Historical ticket data must be loaded through Missive's Posts API (POST /v1/posts) or Messages API (POST /v1/messages for custom channels), one conversation at a time. Plan for a custom API-based migration from day one.
SurveySparrow API rate limits
SurveySparrow does not publish rate limit specifics in their public v3 documentation. Based on testing against Business-tier accounts, the practical ceiling is approximately 120 requests per hour before throttling begins, with a daily cap near 1,000 requests on lower-tier plans. Rate limits vary by plan — contact SurveySparrow support to confirm limits for your account before designing your extraction schedule. For large ticket volumes (5,000+), extraction will be the bottleneck. Build in exponential backoff and plan for multi-day extraction windows.
Missive's Messages endpoint is only for custom channels
POST /v1/messages creates incoming messages for custom channel accounts. To inject historical ticket data as visible entries in a conversation, use POST /v1/posts — this is the intended endpoint for integration-injected content and leaves a visible trace in the conversation timeline.
Webhook-assisted delta extraction
SurveySparrow supports webhooks on ticket create and update events. If your migration window spans multiple days, configure a webhook to capture new/updated tickets during the extraction period rather than polling for changes. This is more reliable than running a delta extraction script at cutover. Configure the webhook in SurveySparrow under Settings → Integrations → Webhooks, pointing to a lightweight receiver that appends to your extraction dataset.
Batch extraction tip
For datasets over 2,000 tickets, extract tickets and comments across multiple hours to avoid hitting SurveySparrow's daily API limits. Store extracted data as local JSON files before transformation — never extract and load in the same loop.
Missive's analytics require a Productive or Business plan and are based on conversation
Missive's analytics require a Productive or Business plan and are based on conversation activity within Missive. Historical performance data from SurveySparrow should be exported to CSV and archived separately before decommissioning. Missive analytics will only reflect activity that occurs within Missive.
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 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 Surveysparrow Ticket Management → 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 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 → Missive specifics
- GET /v3/tickets/:id
- Single ticket with full detail (requester, agent, team, custom fields, timestamps)
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 → 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 Surveysparrow Ticket Management → 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.
-
Contact custom info
Use the custom kind in contact infos for per-customer metadata that should follow the contact, not the conversation
Surveysparrow Ticket Management → Missive specifics
- Shared labels
- Best for categorical values (e.g., "Product: Enterprise", "Region: EMEA")
- Post body
- Embed custom field values as structured markdown in the initial migration post (most complete, visible in timeline)
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 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 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 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.
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 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 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.
-
Record counts match
Total conversations in Missive equals total tickets extracted
Surveysparrow Ticket Management → Missive specifics
- Comment counts match
- Spot-check 20+ conversations for correct post counts
- Labels applied correctly
- Filter by each shared label to confirm counts
- Closed conversations
- Verify resolved/closed tickets appear in Missive's Closed mailbox
- Contacts linked
- Confirm requester names and emails appear in the Missive sidebar
- Attachments accessible
- Download a sample of migrated attachments to verify integrity
Don't move on until
- Full reconciliation report attached to the project record
- Reporting baselines match pre-migration figures within agreed tolerance
- Formal acceptance signed and archive retention scheduled
Risk matrix
Per-object risk for this pair. Plan extra validation around anything marked high.
| Object | Risk | Notes |
|---|---|---|
| Tickets (Core Records) | medium | Individual ticket records can be extracted via GET /v3/tickets/:id and mapped to Missive conversations, but the one-at-a-time loading constraint and rate limits make large ticket volumes (5,000+) operationally risky without a well-tested idempotency strategy. |
| Threaded Comments / Replies | high | Comment threads require a separate API call per ticket to retrieve and must be reconstructed as sequential posts in Missive rather than native reply messages, meaning the original threading fidelity and public/internal comment distinction are not fully preserved. |
| Attachments | high | Attachment URLs in SurveySparrow payloads may expire or require authentication headers during migration, and re-uploading via Missive's base64 API is constrained by a 10 MB per-request payload cap, creating a high risk of attachment loss for large or numerous files. |
| Custom Fields | high | SurveySparrow custom fields are typed ticket-level objects with no equivalent construct in Missive, requiring all custom field values to be encoded as shared labels or flattened into post markdown content, resulting in loss of field type fidelity and queryability. |
| Priority and Status Enums | medium | SurveySparrow priority (Low, Medium, High, Urgent) and status (Open, Pending, Resolved, Closed) enums must be mapped to Missive shared labels and mailbox placement respectively, which requires a pre-defined label taxonomy and transformation rules to avoid data loss. |
| SLA / Due Date Timestamps | high | SurveySparrow's first_response_due and resolution_due fields have no equivalent in Missive's data model and cannot be preserved in any native field, meaning SLA compliance history is lost unless explicitly encoded in post content or exported to a separate data store. |
| Parent-Child Ticket Relationships | high | The parent_ticket_id and child_ticket_ids relational structure in SurveySparrow is not supported in Missive, and any approximation via labels or tasks requires custom logic with no guarantee of maintaining navigable hierarchical relationships. |
| Contacts / Requesters | medium | Contact records must be created in a Missive contact book via a separately retrieved contact_book_id before conversations are loaded, and any missing or duplicate contact entries will block correct conversation attribution. |
| Agent Assignments | medium | Missive rejects assignments to user IDs that do not exist in the organization, so incomplete agent mapping — particularly for former employees or renamed accounts — will cause load failures or unassigned conversations. |
| Survey-Sourced Ticket Metadata | low | Tickets spawned from survey responses carry source and survey_id fields that are informational only and can be preserved in Missive post content as plain text without structural risk, though the linkage to the originating SurveySparrow survey is permanently severed. |
The hard parts
What makes this specific migration difficult, beyond the mechanics.
No Bulk Import Endpoint
Missive has no bulk historical conversation import endpoint, requiring every migrated ticket to be created individually via POST /v1/posts or POST /v1/messages, which caps throughput at approximately 3,600 conversations per hour at a safe API cadence.
Ticket-to-Conversation Model Mismatch
SurveySparrow's flat ticket schema — including priority enums, status codes, SLA due dates, and custom fields — has no direct structural equivalent in Missive and must be encoded as shared labels, markdown-formatted post content, or conversation metadata during transformation.
Threaded Comment Reconstruction
The SurveySparrow ticket list endpoint does not include comment threads, requiring a separate GET /v3/tickets/:id/comments API call per ticket to retrieve replies before comments can be reconstructed as sequential posts within a Missive conversation.
Attachment Binary Handling
SurveySparrow ticket and comment payloads include attachment URLs rather than binary data, requiring all files to be downloaded during extraction before re-encoding as base64 for Missive's API, which enforces a 10 MB per-request payload limit and a maximum of 25 files per draft.
Agent and Contact Pre-Mapping Requirement
Missive will reject conversation assignments to non-existent user IDs, meaning a complete agent identity mapping table and contact book population must be completed and validated before the data load phase begins.
Parent-Child Ticket Relationship Loss
SurveySparrow supports parent-child ticket hierarchies via parent_ticket_id and child_ticket_ids fields, but Missive has no equivalent relational construct, requiring these relationships to be approximated through conversation merging, tasks, or explicit label tagging with associated data loss in hierarchy fidelity.
Tools used in this playbook
All free, all run entirely in your browser — nothing is uploaded.
FAQ
Can I import SurveySparrow tickets into Missive automatically?
No. Neither platform offers a built-in migration tool for this direction, and no third-party connector exists. You need to extract data via SurveySparrow's API v3 and load it into Missive using the Posts API with custom scripts.
Does Missive have a ticket status system like SurveySparrow?
No. Missive uses a conversation state model with Inbox, Closed, Snoozed, and Trashed. To replicate SurveySparrow's multi-status system (Open, Pending, Resolved, Closed), create shared labels for each status and apply them during migration.
What Missive plan do I need for API access?
You need at least the Productive plan ($24/user/month billed annually). The Starter and Free tiers do not include API access, integrations, or automation rules.
How long does a SurveySparrow to Missive migration take?
For under 2,000 tickets, expect 1–2 days including scripting and validation. For 5,000–25,000 tickets, budget 3–5 days. The main bottleneck is API rate limits on both sides.
Will SurveySparrow ticket attachments transfer to Missive?
Yes, but they require manual handling. Download attachments during extraction, base64-encode them, and include them in Missive API payloads. The total JSON payload per request cannot exceed 10 MB.