Enchant-to-Missive migration requires API-based ETL due to different data models. Plan for tight rate limits on both sides, no KB in Missive, and manual automation rebuilds.
There is no native migration path from Enchant to Missive. Enchant organizes work around tickets with discrete states and inboxes, while Missive uses a conversation-centric model tied to team inboxes and labels — creating fundamental data model incompatibilities. Custom work is required for any full-fidelity migration: API-based extraction from Enchant, schema transformation, and loading via the Missive API, with additional complexity around entities like ticket-level custom fields and CSAT data that have no native Missive equivalent.
Read this first
Pair-specific gotchas that catch teams out. Each one has cost somebody a weekend.
Missive has no native Knowledge Base
If you use Enchant's KB, plan a separate migration path — to a tool like Notion, GitBook, Help Scout Docs, or a dedicated KB platform like Document360.
Run a pilot first
Migrate a single Inbox (100–500 tickets) to validate your mapping, identify edge cases, and estimate total migration time before committing to the full run.
Missive API tokens are personal
There is no organization-level API token. The token inherits the user's access scope — make sure your migration token belongs to an admin with full access to all Team Inboxes and the organization's Contact Book.
Conversation update endpoint
Historically, Missive had no PATCH /v1/conversations/:id. State changes required Posts, Messages, or Drafts endpoints with action parameters. Missive's 11.30.1 changelog indicates a newer endpoint now exists for closing, reopening, assigning, labeling, and moving conversations. Verify the current API reference before coding your loader.
Rate limit math for Missive
At 300 requests per minute (the documented limit), migrating 10,000 conversations with 3 API calls each (contact lookup + post + state change) would take roughly 100 minutes in theory. In practice, factor in retries, error handling, attachment uploads, and conservative pacing — plan for 8–10 hours for a dataset that size. For 50K+ tickets, plan for multi-day migration windows.
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 Enchant
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 Enchant → 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.
Enchant → Missive specifics
- Collaboration model
- Missive's internal chat lives inside each conversation, enabling real-time collaborative drafting and @mentions. Enchant's collaboration is limited to internal notes on tickets — no live co-editing.
- Unified personal + shared inboxes
- Missive combines personal email and team inboxes in one interface. Enchant agents work exclusively in the helpdesk — personal email stays separate.
- Rules engine
- Missive's rules auto-route, label, assign, and trigger webhooks based on content, sender, domain, or keywords. Enchant has triggers and macros, but they're narrower in scope and lack webhook support.
- Multi-channel consolidation
- Missive natively supports email, SMS, WhatsApp, Instagram, and custom channels as first-class conversation types. Enchant supports similar channels but with a more traditional ticket model where each channel creates a discrete ticket.
- API and integration depth
- Missive's API supports posts, drafts, contacts, conversations, and UI/iFrame integrations for embedding external app data in the sidebar. Enchant's API is more limited — focused on tickets, messages, customers, and attachments with no iFrame or sidebar integration support.
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 Enchant 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 Enchant 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 Enchant 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
Enchant → Missive specifics
- Customers
- Total count. Check for duplicates (multiple customer records with the same email).
- Users/Agents
- Active vs. inactive. Inactive Enchant agents should map to a "Legacy User" in Missive to preserve history without paying for unnecessary seats.
- Attachments
- Estimate total size. Large attachment volumes significantly slow migration. Note: Enchant attachment URLs may become inaccessible after account cancellation — download all attachments before deprecating your Enchant account.
- Knowledge Base
- Decide the target platform — Missive has no KB.
- Canned Responses / Macros / Triggers
- Document everything — these must be manually rebuilt in Missive as Rules and Response Templates.
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 Enchant → 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 Enchant → 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.
Enchant → Missive specifics
- Custom Fields
- Document all ticket-level custom fields. Decide whether to map them to Contact custom fields or append as internal comments (Missive has no conversation-level custom fields).
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 Enchant 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 Enchant 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 Enchant 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 Enchant 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 Enchant 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.
Concept Equivalent
| Enchant field | Missive field | Notes |
|---|---|---|
| Ticket | Conversation | 1:1 mapping, but Missive conversations are broader (can include chat, posts) |
| Message (reply/note) | Message / Comment | Replies map to messages; internal notes map to comments within conversations |
| Inbox | Team Inbox | Enchant Inboxes map to Missive Team Inboxes |
| User (agent) | User / Team Member | Users in Enchant map to Missive organization members |
| Customer | Contact | Enchant customers map to Missive contacts |
| Contact (email/phone/twitter) | Contact Info (email/phone) | Missive contacts use an infos array for multiple identifiers |
| Label | Label | Direct mapping — both use labels for categorization |
| Attachment | Attachment | Must be downloaded and re-uploaded per message |
| Ticket Custom Fields | No native conversation equivalent | Missive supports custom fields on Contacts and Organizations only |
| Customer Satisfaction (CSAT) | No native equivalent | Must be stored as metadata in conversation posts or notes |
| Knowledge Base articles | No native equivalent | Missive is not a KB platform; migrate KB content elsewhere |
| Canned Responses | Response Templates | Must be manually recreated |
| Triggers / Macros | Rules | Must be manually rebuilt; Missive Rules are more powerful but structurally different |
Enchant Missive
| Enchant field | Missive field | Notes |
|---|---|---|
| ticket.id | N/A (internal ref) | Store in mapping table; optionally in a label or comment |
| ticket.number | N/A | No equivalent; log for reference |
| ticket.subject | conversation_subject | Direct copy |
| ticket.state | Conversation state + label | Map hold → label; closed → close action; snoozed → snooze |
| ticket.type | Conversation channel | Map where possible; fallback to post for chat/phone |
| ticket.inbox_id | Team Inbox ID | Use pre-built lookup map |
| ticket.label_ids | add_shared_labels | Remap via label ID lookup |
| ticket.user_id | Assignee | Map via user lookup; fallback to Legacy User |
| ticket.created_at | Post timestamp | Preserve original date |
| customer.first_name | contact.first_name | Direct copy |
| customer.last_name | contact.last_name | Direct copy |
| customer.contacts [].value | contact.infos [].value | Map type: email → email, phone → phone |
| customer.summary | contact.notes or custom field | Inject as contact note |
| message.body | Post/message body | Clean and validate HTML; strip Enchant-specific styles |
| message.type | Message or Comment | note → internal comment; reply → message |
| message.direction | Sender context | in = customer; out = agent |
| attachment.name | Attachment filename | Direct copy |
| attachment.data | Attachment upload | Download from Enchant, re-upload to Missive |
Risk matrix
Per-object risk for this pair. Plan extra validation around anything marked high.
| Object | Risk | Notes |
|---|---|---|
| Tickets / Conversations | medium | Tickets map 1:1 to conversations, but the structural model difference requires careful state mapping and threading preservation via API-based migration. |
| Contacts / Customers | low | Enchant customers map directly to Missive contacts with support for multiple identifiers via the infos array, and CSV import is available for basic contact data. |
| Internal Notes | medium | Enchant internal notes must be mapped to Missive comments within conversations, which requires API-based migration as there is no bulk import method. |
| Labels | low | Both platforms support labels for categorization with a direct mapping, though label consolidation and cleanup should be done before migration. |
| Attachments | high | Attachments must be individually downloaded and re-uploaded per message, significantly slowing migration, and Enchant attachment URLs may become permanently inaccessible after account cancellation. |
| Custom Fields | high | Missive has no conversation-level custom fields, so Enchant ticket custom fields must be remapped to contact-level fields or stored as internal comments, resulting in potential data model loss. |
| CSAT Scores | high | Missive has no native customer satisfaction feature, so CSAT data must be stored as metadata in conversation posts or notes with no structured querying capability. |
| Knowledge Base Articles | high | Missive has no knowledge base functionality, requiring a completely separate migration to a third-party KB platform. |
| Canned Responses / Macros | medium | Canned responses and macros must be manually recreated as Missive Response Templates and Rules, with no automated migration path available. |
| Users / Agents | low | Enchant agents map to Missive organization members, though inactive agents should be mapped to a legacy user to preserve history without incurring additional seat costs. |
The hard parts
What makes this specific migration difficult, beyond the mechanics.
No Native Import Path
Missive offers no bulk import tool for conversations, requiring all historical data to be loaded programmatically through its REST API with custom transformation logic.
Ticket-to-Conversation Model Mismatch
Enchant's discrete ticket-based model with states (open, hold, closed, archived) must be mapped to Missive's broader conversation-centric model, which lacks direct state equivalents.
Custom Fields Have No Equivalent
Enchant supports ticket-level custom fields, but Missive only supports custom fields on Contacts and Organizations, requiring data to be relocated or appended as internal comments.
Attachment Re-Upload Required
All attachments must be individually downloaded from Enchant and re-uploaded to Missive per message, and Enchant attachment URLs may become inaccessible after account cancellation.
Workflow and Automation Rebuild
Enchant's triggers, macros, and canned responses cannot be automatically migrated and must be manually reconstructed as Missive Rules and Response Templates, which are structurally different.
Knowledge Base Requires Separate Migration
Missive has no native knowledge base, so Enchant KB articles must be migrated to a separate platform such as Notion, GitBook, or Document360.
Tools used in this playbook
All free, all run entirely in your browser — nothing is uploaded.
FAQ
Can I migrate conversation history from Enchant to Missive using CSV?
No. Enchant's CSV export covers report data only — not full ticket bodies or message threads. Missive's native CSV import only supports contacts. To migrate complete conversation history, internal notes, and attachments, you need to extract tickets via the Enchant REST API and recreate them as conversations in Missive using the Posts or Drafts endpoint.
What are the API rate limits for Enchant and Missive?
Enchant allows 100 API credits per minute (account-wide) with a burst limit of 6 requests per second. Missive allows 5 concurrent requests, 300 per minute, and 900 per 15 minutes. Both return HTTP 429 when limits are exceeded.
Does Missive support Knowledge Base articles like Enchant?
No. Missive is a shared inbox and collaboration platform with no native Knowledge Base feature. If you use Enchant's KB, migrate those articles to a separate tool like Notion, GitBook, or a dedicated KB platform.
How do Enchant custom fields map to Missive?
Missive does not support custom fields on conversations. You must either map Enchant ticket custom fields to Missive Contact custom fields (with the caveat that the last write wins if a contact has multiple tickets), or append the data as an internal comment on the Missive conversation during import.
How long does an Enchant to Missive migration take?
For small teams (<5,000 tickets), an API-based migration can be completed in 1–3 days including validation. Larger datasets (50K+ tickets) may take a week or more due to API rate limits. A managed migration service can typically complete the job in 2–5 business days.