Migrate your Enchant data
Omnichannel helpdesk platform unifying email, phone, SMS, and social messaging into shared inboxes with built-in knowledge base and workflow automation.
In its favor
Why people choose Enchant
The signal that keeps Enchant on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Single-price simplicity removes decision fatigue — one plan at $20/user/mo includes all core features rather than gating functionality behind multiple tiers
G2 reviewers consistently highlight the intuitive interface and ease of setup, particularly for small to mid-sized support teams transitioning from fragmented tools
Omnichannel consolidation brings email, phone, SMS, and social messaging into one shared inbox view, eliminating the context-switching that frustrates agents
Built-in knowledge base reduces repeated agent effort by surfacing self-service articles alongside conversations without requiring a separate CMS
Mobile app experience lags behind desktop functionality, frustrating agents who handle support on-the-go or work remotely via phone
Workflow and automation capabilities are less mature than competitors — power users report needing workarounds for complex routing or conditional logic
No public API documentation or mature developer portal makes custom integrations and automated data exports difficult to build and maintain
Limited enterprise-grade features such as granular role permissions, audit logging, and advanced SLA tooling push scaling companies toward Zendesk or Freshdesk
Reasons to switch
Why people leave Enchant
The recurring reasons buyers give for replacing Enchant. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where Enchant fits
Grades across six dimensions, plus a SWOT-style view of where the platform shines and where it falls short.
SWOT — strengths, weaknesses, and use-case fit
Strengths
Weaknesses
Where it works
Where it struggles
Pricing tiers
Enchant pricing overview
Enchant uses a single flat-rate base plan of $20 per user per month covering all core features, with optional add-ons for security (SSO, IP restrictions) at $5/user/mo and AI capabilities charged per 500 customers helped. There are no tiered feature gates within the base plan.
Base Plan
Tier 1 of 4
$20/user/mo
What's included
Need help selecting your Helpdesk?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on Enchant's schedule — see our quote-based pricing →
What gets migrated
Enchant object support
Object-by-object support for Enchant migrations. Per-pair details surface during scoping.
Conversations
Fully supportedConversations are the core object in Enchant, representing threaded message exchanges within an inbox. We migrate full conversation history including internal notes, shared drafts, and message timestamps. Status transitions (open, pending, resolved, spam) are mapped to the destination ticket status model.
Customers
Fully supportedEnchant maintains customer profiles linked to conversation history. We migrate name, email, phone, company, custom properties, and tags. Customer activity timelines are preserved as linked conversation history in the destination.
Channels
Mapping requiredChannels represent communication sources (email, phone, SMS, WhatsApp, Facebook, Instagram). We map each channel to an equivalent in the destination. Phone channels require special handling as they may include call recordings not accessible via standard export.
Inboxes
Mapping requiredInboxes group conversations by team or function. We preserve inbox structure and map agents to destination teams. Inboxes with complex routing rules require manual review during scoping to ensure correct assignment logic in the destination.
Knowledge Base Articles
Fully supportedEnchant's knowledge base contains public articles and internal snippets. We migrate article content, categories, and publication status. Attachments embedded in articles are downloaded and reattached. Article URLs change post-migration and will need redirect handling.
Agents / Team Members
Mapping requiredAgent profiles include name, email, role, and availability settings. We map agents to destination users, preserving admin versus agent status. Enchant's granular permission model may require simplified role mapping depending on destination platform capabilities.
Tags
Fully supportedConversations and customers can be tagged in Enchant. We migrate all tags and apply them to the corresponding records in the destination, handling multi-tag associations per record.
Satisfaction Ratings
Fully supportedCSAT ratings attached to resolved conversations are migrated as standalone metrics linked to their originating conversations. Historical rating distributions are preserved for reporting continuity.
Workflows / Automations
Not in this platformEnchant's workflow automation rules (triggers, conditions, actions) are not exported via available methods. We document existing automations during scoping so they can be rebuilt in the destination platform.
Attachments
Mapping requiredFile attachments in conversations are downloadable. We extract and re-upload them to the destination, preserving original filenames. Attachments stored in third-party integrations (e.g., Google Drive links) require re-authentication post-migration.
| Object | Support | Notes |
|---|---|---|
| Conversations | Fully supported | Conversations are the core object in Enchant, representing threaded message exchanges within an inbox. We migrate full conversation history including internal notes, shared drafts, and message timestamps. Status transitions (open, pending, resolved, spam) are mapped to the destination ticket status model. |
| Customers | Fully supported | Enchant maintains customer profiles linked to conversation history. We migrate name, email, phone, company, custom properties, and tags. Customer activity timelines are preserved as linked conversation history in the destination. |
| Channels | Mapping required | Channels represent communication sources (email, phone, SMS, WhatsApp, Facebook, Instagram). We map each channel to an equivalent in the destination. Phone channels require special handling as they may include call recordings not accessible via standard export. |
| Inboxes | Mapping required | Inboxes group conversations by team or function. We preserve inbox structure and map agents to destination teams. Inboxes with complex routing rules require manual review during scoping to ensure correct assignment logic in the destination. |
| Knowledge Base Articles | Fully supported | Enchant's knowledge base contains public articles and internal snippets. We migrate article content, categories, and publication status. Attachments embedded in articles are downloaded and reattached. Article URLs change post-migration and will need redirect handling. |
| Agents / Team Members | Mapping required | Agent profiles include name, email, role, and availability settings. We map agents to destination users, preserving admin versus agent status. Enchant's granular permission model may require simplified role mapping depending on destination platform capabilities. |
| Tags | Fully supported | Conversations and customers can be tagged in Enchant. We migrate all tags and apply them to the corresponding records in the destination, handling multi-tag associations per record. |
| Satisfaction Ratings | Fully supported | CSAT ratings attached to resolved conversations are migrated as standalone metrics linked to their originating conversations. Historical rating distributions are preserved for reporting continuity. |
| Workflows / Automations | Not in this platform | Enchant's workflow automation rules (triggers, conditions, actions) are not exported via available methods. We document existing automations during scoping so they can be rebuilt in the destination platform. |
| Attachments | Mapping required | File attachments in conversations are downloadable. We extract and re-upload them to the destination, preserving original filenames. Attachments stored in third-party integrations (e.g., Google Drive links) require re-authentication post-migration. |
Gotchas
What to watch for in Enchant migrations
Issues we've hit on past Enchant migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
No documented public API constrains migration extraction
Phone channel attachments require separate handling
Workflows and automation rules do not migrate
Knowledge base article URLs change post-migration
| Severity | Issue |
|---|---|
| High | No documented public API constrains migration extraction |
| Medium | Phone channel attachments require separate handling |
| Medium | Workflows and automation rules do not migrate |
| Low | Knowledge base article URLs change post-migration |
Leaving Enchant?
Where Enchant customers move next
7 destinations Enchant can migrate to.
How a Enchant migration works
Four steps, Enchant-specific
Connect
Not publicly documented into Enchant. Scopes limited to read-only on the data we move.
Map
We translate Enchant-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate Enchant quirks before production.
Migrate
Full migration with Enchant rate-limit handling. Rollback available throughout.
FAQ
Enchant migration FAQ
Answers to the questions buyers ask most during Enchant migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your Enchant migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationOther helpdesks we support
Ready when you are
Migrate Enchant.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your Enchant setup and destination — written quote back within a business day.