Kustomer to Missive migration requires API-based extraction (CSV exports lose message bodies), KObject flattening into contact fields, and careful rate-limit management at ~1 req/sec on Missive's API.
Migrating from Kustomer to Missive is a data model compression problem with no native migration path, no import wizard, and no built-in connector between the two platforms. Kustomer is a CRM-first helpdesk built around a customer-centric timeline with extensible custom objects (KObjects), while Missive is a conversation-centric collaborative team inbox with no custom object layer — meaning KObject data for orders, subscriptions, or policies must be flattened into contact fields, moved to an external system, or abandoned entirely. The practical migration path requires Kustomer REST API extraction, a custom transformation layer, and loading via Missive's REST API using the custom channel Messages API for conversation history. Custom ETL work is required for any migration involving conversation history, attachments, or structured contact data beyond a basic CSV contact import.
Read this first
Pair-specific gotchas that catch teams out. Each one has cost somebody a weekend.
Missive's infos array with kind
"custom" only supports string values. There are no typed fields (date, number, picklist). If your Kustomer KObjects have structured data types, you'll lose type enforcement in Missive.
Custom channels in Missive do not currently support the rule engine (missiveapp.com)
Migrated historical threads imported via custom channel will not trigger rules. Only new conversations arriving through native channels (email, SMS, chat) will be processed by rules.
For conversations with more than 380 messages, split into segments
Use deterministic external IDs (e.g., kustomer-conv-123-part-1, kustomer-conv-123-part-2) and add a message at the boundary: "Continued in Part 2 — [original Kustomer conversation ID: 123]". Missive caps conversations at 400 messages and starts a new thread after that limit. Leave headroom below the cap for future replies.
Missive's API cannot set the "snoozed" state on conversations programmatically
Snoozed conversations from Kustomer should be imported as closed with a "Previously Snoozed" label for agent visibility.
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 Kustomer
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 Kustomer → 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.
Kustomer → Missive specifics
- Cost structure mismatch
- Kustomer's per-seat pricing on Enterprise ($89/agent/month) and Ultimate ($139/agent/month) tiers creates a significant gap versus Missive's per-user pricing ($14–$36/user/month as of 2024). A 30-agent team on Kustomer Enterprise paying ~$32,000/year could run Missive's Productive plan at ~$12,960/year — a ~60% reduction in licensing cost alone. The savings scale linearly with headcount.
- CRM weight without CRM use
- Many teams don't use Kustomer's CRM depth — KObjects, custom timelines, workflow builders. Missive's lighter model (shared inbox + labels + rules) fits teams that want fast collaboration without configuration overhead. If your CRM and marketing automation already live in HubSpot, Salesforce, or a similar system, Kustomer's built-in CRM layer is redundant.
- Agency and multi-client workflows
- Missive's multi-organization model and per-conversation collaboration features (shared drafts, @mentions, internal comments) work well for agencies managing multiple client brands from one account.
- Channel consolidation without routing overhead
- Missive unifies email, SMS, WhatsApp, Messenger, Instagram, and live chat in a single collaborative inbox — appealing for teams that don't need Kustomer's queue-based routing and SLA enforcement.
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 Kustomer 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 Kustomer 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 Kustomer 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
Kustomer → Missive specifics
- Authentication
- Bearer token via API key. Create under Settings → Security → API Keys.
- Rate limits
- Vary by plan. Enterprise: 1,000 RPM for machine users. Ultimate: 2,000 RPM. The limit is org-wide across all API keys. Machine searches have a separate 100 RPM limit (help.kustomer.com).
- Parallel extraction
- At 1,000 RPM (Enterprise), you can run 10 concurrent extraction workers at 100 RPM each, or 5 workers at 200 RPM each. Partition by customer ID range or conversation date range. This reduces extraction time for 1M messages from ~17 hours (single-threaded at 1,000 RPM) to the same ~17 hours but with better fault isolation per partition.
- Pagination
- Cursor-based using page [size] (max 100) and page [after] parameters.
- Data completeness
- CSV exports only include message previews. You must use the API for full message bodies.
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 Kustomer → 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 Kustomer → 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.
-
Split names
Kustomer stores name as a single field. Split into first_name and last_name for Missive. Handle edge cases: single-word names (put in first_name, leave last_name empty), names with multiple spaces (split on first space only).
-
Map emails/phones
Kustomer's emails array → Missive's infos array with kind: "email".
-
Map companies
Kustomer company associations → Missive memberships with kind: "organization".
Kustomer → Missive specifics
- Reformat HTML
- Convert <p>...</p> tags to <div>...</div> with <br> for Missive's rendering engine. Strip Kustomer-specific HTML classes or inline styles that won't render in Missive.
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 Kustomer 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 Kustomer 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 Kustomer 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 Kustomer 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 Kustomer 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
Kustomer's KObject layer has no equivalent in Missive, meaning all custom object data for entities like orders, subscriptions, or shipments must be rearchitected into an external system or partially flattened before any migration work begins.
| Kustomer field | Missive field | Notes |
|---|---|---|
| Customer | Contact | Map to Missive contact in a shared contact book |
| Company | Contact Organization | Use memberships array with kind: "organization" |
| Conversation | Conversation | Created implicitly via custom channel Messages API |
| Message | Message (custom channel) | Use POST /v1/messages with custom channel account |
| Note | Comment or Post | Internal notes → Comments; system events → Posts |
| KObject | Contact custom fields / Notes / External | No direct equivalent. Flatten key fields into contact infos |
| Tag (conversation) | Shared Label | Create labels first, apply via add_shared_labels |
| Tag (customer) | Contact Group | Use memberships with kind: "group" |
| Team | Team | Create via POST /v1/teams |
| Snippet | Response | Create via POST /v1/responses |
| Agent/User | User | Manual setup — no user creation API in Missive |
Cus mer
Kustomer's KObject layer has no equivalent in Missive, meaning all custom object data for entities like orders, subscriptions, or shipments must be rearchitected into an external system or partially flattened before any migration work begins.
| Kustomer field | Missive field | Notes |
|---|---|---|
| name | first_name + last_name | Split on first space; handle single-word names gracefully |
| emails [].email | infos [{kind: "email"}] | Map all emails; first becomes primary |
| phones [].phone | infos [{kind: "phone_number"}] | Map all phones |
| socials.twitter | infos [{kind: "twitter"}] | If present |
| urls | infos [{kind: "url"}] | Map all URLs |
| custom.fieldName | infos [{kind: "custom", custom_label: "fieldName"}] | Custom attributes → custom infos |
| company | memberships [{group: {kind: "organization"}}] | Company association |
| tags | Contact group memberships | kind: "group" |
| notes | notes field on contact | Free text |
Risk matrix
Per-object risk for this pair. Plan extra validation around anything marked high.
| Object | Risk | Notes |
|---|---|---|
| Conversations | high | Conversations are top-level objects in Missive but hang off Customer records in Kustomer, requiring a structural model inversion and custom channel API usage since Missive has no native ticket import endpoint. |
| Messages | high | Full message bodies are not available in Kustomer CSV exports and must be extracted via the REST API, then loaded through Missive's custom channel Messages API with base64-encoded attachments subject to a 10 MB per-request payload limit. |
| KObjects (Custom Objects) | high | Kustomer's KObject layer has no equivalent in Missive, meaning all custom object data for entities like orders, subscriptions, or shipments must be rearchitected into an external system or partially flattened before any migration work begins. |
| Attachments | high | Attachments must be base64-encoded and are subject to a 10 MB payload limit per API request, making large or numerous attachments a significant source of migration failures requiring custom batching logic. |
| Contacts | medium | Contacts can be imported via CSV or API, but Kustomer's CSV exports are limited to 25 attributes and 50,000 rows, and custom attributes on Customer records must be remapped to Missive's contact custom info fields. |
| Internal Notes | medium | Kustomer internal notes map to Missive comments, but the relationship must be preserved within the correct conversation thread or context is permanently lost. |
| Custom Fields | medium | Kustomer supports custom attributes on any object including Customers, Conversations, Companies, and KObjects, while Missive only supports custom info fields on contacts, requiring significant field-mapping decisions before transformation begins. |
| Companies | medium | Kustomer Company objects map to Missive Contact Organizations, but the linkage to individual contacts must be explicitly re-established during the transformation step as there is no automatic relationship inference. |
| Tags and Labels | low | Kustomer conversation tags map reasonably to Missive shared labels, though customer-level tags have no direct equivalent and must be evaluated for whether they map to contact groups or are dropped. |
| Workflows and Rules | medium | Kustomer's visual workflow builder supports complex branching and multi-step logic, while Missive's rules are limited to simple condition/action pairs with no branching, meaning complex automation must be manually rebuilt and simplified. |
The hard parts
What makes this specific migration difficult, beyond the mechanics.
No Native Migration Path
There is no import wizard, built-in connector, or one-click transfer between Kustomer and Missive, requiring a fully custom API-based extraction and loading pipeline for any meaningful data transfer.
KObject Layer Has No Equivalent
Kustomer's extensible custom object layer (KObjects with Klasses supporting up to ~500 attributes per Klass) has no counterpart in Missive, so all custom object data must be flattened into contact custom fields, exported to an external system, or discarded before migration begins.
Customer-to-Conversation Model Inversion
Kustomer's Customer → Conversation → Message → Note hierarchy must be restructured into Missive's Conversation → Message → Comment model, and any broken relationship in the chain causes permanent loss of thread context.
Missive API Rate-Limit Bottleneck
Missive's sustained API rate limit of approximately 300 requests per minute means importing 50,000 conversations with an average of five messages each requires roughly 70 hours of continuous API calls before accounting for retries.
CSV Export Data Truncation
Kustomer's CSV and reporting exports contain only message previews rather than full message bodies, and are capped at 50,000 rows and 30-day windows, making them unsuitable for full conversation history migration.
Idempotency and Resume Logic Required
Resuming a failed migration mid-run without duplicating already-loaded records requires external state tracking via checkpoint files or a database, external_id deduplication, and the ability to query Missive for existing records.
Tools used in this playbook
All free, all run entirely in your browser — nothing is uploaded.
FAQ
Can I migrate conversation history from Kustomer to Missive via CSV?
No. Kustomer's CSV exports only include message previews, not full message bodies. You must extract conversations through Kustomer's REST API and load them into Missive using the custom channel Messages API. Missive's native CSV import only supports contacts, not conversation history.
What happens to Kustomer KObjects when migrating to Missive?
Missive has no custom object model equivalent to KObjects. Your options are: flatten key KObject fields into Missive contact custom fields (infos with kind: custom), store KObject data in contact notes as structured text, keep the data in an external system and surface it via Missive's iFrame integrations, or archive to a separate database.
How long does a Kustomer to Missive migration take?
It depends on data volume. Missive's API sustains roughly 1 request per second (300 per minute, 900 per 15 minutes). A migration of 10K conversations with 5 messages each takes approximately 14 hours of continuous API calls. Datasets of 50K+ conversations can take multiple days of 24/7 execution. Add 1–2 weeks for planning, testing, and validation.
What Missive limit breaks long Kustomer conversation threads?
Missive caps conversations at 400 messages and automatically starts a new thread after that limit. Long Kustomer conversations should be segmented during load using deterministic thread references (e.g., kustomer-conv-123-part-1) with a safety buffer below the 400-message cap for future replies.
How do I migrate Kustomer conversations older than two years?
Use Kustomer's Archive Search plus API extraction. The standard Search endpoint only returns records updated within the past two years and caps queries at 100 pages. Archive Search is required for older historical data.