Crisp to Enchant Migration

MIGRATION OVERVIEW

Why teams migrate from Crisp to Enchant

The core problem

Migrating from Crisp to Enchant requires a fully custom API-led integration, as no native one-click migration path exists between the two platforms. Crisp is built around a conversation-centric model anchored on session_id within Website workspaces, while Enchant organizes work around Tickets belonging to Inboxes — a fundamentally different structural paradigm. The profile model diverges equally: Crisp People profiles support arbitrary key-value data and segments, whereas Enchant Customers are flatter entities with a limited contact type set. Custom engineering is required to extract data from Crisp's REST API, transform it to Enchant's schema, handle attachment re-upload, manage timestamp loss, and replay messages with correct directionality.

Why this matters for your migration

KEY CHALLENGES

What makes this migration complex

These are the architectural mismatches and technical hurdles specific to a Crisp to Enchant migration.

Most Critical

No Native Migration Path

There is no one-click or built-in export/import tool connecting Crisp and Enchant; all data transfer requires custom API-to-API engineering or use of Enchant's managed import service, which produces read-only archive tickets unsuitable for active work.

Blocks all downstream imports if mapped wrong

Ticket Type API Constraint

Enchant's public API only supports creating tickets of type email, meaning all Crisp conversations — regardless of whether they originated as live chat, bot sessions, or messaging — must be migrated as email-type tickets.

Historical Timestamps Not Preserved

Enchant's API does not accept custom created_at values on ticket or message creation, so all migrated records receive the current system time rather than their original Crisp timestamps.

Attachment Re-Upload Complexity

Files shared within Crisp conversations cannot be transferred by reference; each attachment must be individually downloaded from Crisp and re-uploaded to Enchant as a base64-encoded payload during migration.

Profile and Segment Data Model Mismatch

Crisp People profiles support arbitrary key-value custom data and workspace-wide segments, while Enchant Customers offer only a flat summary text field and per-inbox Labels, requiring significant data flattening or external storage for richer profile data.

Rate Limit Complexity on Both APIs

Crisp enforces a daily request quota per plugin token that can halt large exports until the following day, while Enchant enforces both a 100-credits-per-minute account-wide limit and a hard burst cap of 6 requests per second, requiring a carefully throttled request queue.

MIGRATION RISK ASSESSMENT

Every migration risk, already solved

Migration between platforms is full of edge cases. Our engineers have identified every risk from Crisp to Enchant and built proven solutions for each one.

High complexity

Conversations / Tickets

Every Crisp conversation must be individually extracted via paginated API calls, transformed to Enchant's email-type ticket schema, and written through the API — with no timestamp preservation and no guarantee of state fidelity across the two platforms' differing state models.

Solved
Messages / Replies

Crisp supports a wide variety of message types including text, note, file, animation, audio, picker, field, carousel, and event, but only text and note types map cleanly to Enchant replies and notes — all other types require custom handling or will be lost.

Solved
Attachments / Files

Each file attachment must be downloaded from Crisp's storage and re-uploaded to Enchant as a base64-encoded payload, introducing significant transfer time, potential data loss if source URLs expire, and payload size constraints.

Solved

Custom engineering

Customers / People Profiles

Crisp People profiles carry arbitrary key-value custom data, notepad content, and company details that cannot be fully represented in Enchant's flat Customer model, requiring decisions about what to flatten into the summary field and what to archive externally.

Handled
Contacts

Enchant Contacts are limited to email, Twitter, and phone types, so any Crisp People identifiers outside these categories — such as custom social handles or platform-specific IDs — cannot be migrated without data loss.

Handled
Segments / Labels

Crisp segments are workspace-wide constructs, while Enchant labels are scoped per inbox and must be pre-created before ticket import, meaning segment-to-label mapping requires upfront structural decisions and manual setup before any data load begins.

Handled
Operators / Users

Enchant does not expose a user creation endpoint in its public API, so all agents must be manually invited through the admin interface before migration begins, and operator identity in Crisp messages requires a pre-built lookup table to preserve message attribution.

Handled
Conversation Custom Data

Crisp conversation-level custom key-value metadata has no dedicated field in Enchant and must be flattened into the Customer summary text field or stored in an external system, resulting in loss of structured queryability.

Handled

Clean transfer

Bot and Anonymous Conversations

Conversations that were handled entirely by Crisp's chatbot or that captured no email address cannot be meaningfully linked to an Enchant customer, and industry estimates suggest 20–70% of chat sessions may fall into this category depending on chatbot usage — these are best left archived in Crisp.

Clean
Campaign Messages / Bot Events

Crisp marketing campaigns, visitor browsing events, geolocation data, and real-time widget events have no equivalent in Enchant's data model and cannot be migrated, making them candidates for external archival only.

Clean

What Our Customers Say

Real migration stories

Direct Review

“One of the easiest migrations I've ever been through. The team took care of everything — all our data, customer interactions and macros. The process was clear, straightforward and we felt supported all the way. An absolutely seamless experience for our support team and our customers.”

Direct Review

“Fantastic at both guiding us through the process and helping us fix things as they come up and dial them in.”

Reviewed on G2

“The ease of the process and that ClonePartner was informing me what was going on at every step. If you're on the fence, do it. ClonePartner are great!”

Direct Review

“They were SO helpful. We had a few hiccups because our migration was in the middle of the process, but they were really flexible and did multiple delta migrations for us. We were able to map a lot of our old ticket data so it's usable for comparisons in the future.”

Direct Review

“Overall a great experience. We had to go back a few times to get everything just right, which was totally expected. The transition was smooth, and there was no data loss.”

See all customer stories →

CUSTOM MIGRATION

Fully customizable engineer-led migration

Tailor your migration from Crisp to Enchant exactly to your needs with our flexible customization options. Our experts will configure the perfect migration plan for your business.

Migration Filters

Data Types

ZERO DOWNTIME

Your timeline. Our engineers.

A dedicated engineer runs your migration, planned around your schedule and your data.

No babysitting a wizard. Avoid debugging errors yourself.

Looking for a more detailed migration timeline?

Contact our team

Speed

The migration timeline depends on both our turnaround time and yours.

We can complete a migration in under a day when the accounts are connected and the sample migration is approved promptly.

Background Sync

We also support migrating the newest records first, so you can go live faster while the rest of the data is synced in the background.

Data Volume Impact

Larger data volumes may require longer migration windows.

Continuous Operation

Weekend migrations minimize disruption to your customer service operations.

MIGRATION TIMELINE

Your Crisp to Enchant migration, step by step

See how long your migration will take from start to finish. Drag the slider to estimate based on your data volume.

How many records are you migrating?

<10K 50K 100K 250K 500K 1M 2M 5M 10M+

Checklist ~3 days

Sample 1 day

Review ~2 days

Full 2 days

Delta 1 day

Your team ClonePartner

Estimated total

~9 business days

Migration Checklist

1 day · ClonePartner ~2 days · Your team

We prepare the optimal data mapping as a shareable spreadsheet. Your team reviews, approves, and adds any customizations.

Sample Migration

1 day · ClonePartner

We run a test migration with a representative sample of your data to verify mapping accuracy and identify any potential issues before the full run.

Review & Approve

~2 days · Your team

Your team reviews the sample migration results, confirms data accuracy and mapping, and gives the go-ahead for the full migration.

Full Migration

2 days · ClonePartner

We execute the complete migration of all your data to your new Enchant, with real-time progress tracking and comprehensive logging.

Delta Migration

1 day · ClonePartner

We capture and transfer any new data that was added or updated during the main migration to ensure no data is lost. This final sync keeps everything current.

Pros and cons of different migration options

Choosing the right approach is key because migrating from Crisp to Enchant isn't just about moving data – it's about protecting customer relationships.

Feature / Criteria	ClonePartner	Automated Tools	CSV Import	In-house migration
Custom Scripting for complex data	✓ Engineers build & maintain	✗ No	⚠ Manual	✓ Yes – but costly
Sandbox & Pilot Migrations	✓ Full sandbox + pilot plans	⚠ Limited	✗ No	⚠ Often Informal
Manual validation & reconciliation	✓ Automated + manual QA	✗ No	✓ Yes (Manual)	✓ Heavy manual effort
Backup & rollback plan	✓ Robust procedures	✗ No	✗ No	⚠ Often incomplete
Handles automation and integrations	✓ Full support	⚠ Partial	✗ No	⚠ Possible but fragmented
Post-migration engineer support	✓ Dedicated engineers	✗ No	✗ No	⚠ Limited SLA
Adaptable to API changes	✓ Proactive adaptation	✗ No	⚠ Manual fixes	⚠ Slower response
Turnaround / SLA predictability	✓ Predictable SLAs	⚠ Fast but brittle	⚠ Slow and manual	⚠ Often slower
Data Security & Compliance	✓ High – enterprise grade	⚠ Medium (depends)	⚠ Low (manual)	⚠ Hidden gaps common
Pricing predictability	✓ Transparent & fixed	⚠ Low (per-job)	⚠ Low (manual hours)	⚠ High/variable OPEX
End-to-end project management	✓ Full E2E delivery & PM	✗ No	✗ No	⚠ Often partial
Business impact & opportunity cost	✓ No diversion of staff	✗ No	✗ No	⚠ Diverts engineering

What does an Engineer-led migration mean anyway?

Speed & Accuracy: Our Blended Method

We blend automation (smart scripts, bulk APIs) with human expertise for speed without risk. Our engineers manually check every mapping, validation, and exception.

You get:

Speed of automation for bulk record migration
Precision of engineers verifying integrity and business logic
Pilot migrations and sandbox testing to catch issues early
Real-time validation reports and rollback readiness

Result: 50x faster migrations than manual imports — with near-zero error rates.

Handling the Tricky Tech and API Details

The Crisp and Enchant APIs each behave differently, which is where our engineers shine. We build custom logic to handle the data quirks where generic tools typically break.

We handcraft API logic for:

Field mapping and transformation
Pagination, rate-limit handling, and throttling
Preserving conversation threads, attachments, and internal notes
Syncing custom fields, SLAs, and macros without breaking structure

Our scripts: Natively retry failed calls, re-queue large attachments, and ensure data parity.

No Guesswork

We don't just promise smooth migrations—we measure and prove them. Every client receives a Migration Validation Report with all metrics.

Typical results across projects:

100% record-count parity between your Crisp data and Enchant
Zero downtime during staged cutovers
99.9% attachment integrity (verified via checksum)
Full automation and preservation of all business rules

Our standard: Includes full SLA preservation and 48 hours of engineer-assigned support post go-live.

We Adapt to Your Setup (Not the Other Way Around)

No two teams configure Crisp or Enchant exactly the same way—with unique automations and data. We customize every migration script to fit your exact workflow, tags, and triggers.

Our engineers adapt for:

Custom fields, ticket forms, and workflows
Multi-brand or multi-language setups
Historical imports and partial (date-based) migrations
Integration re-mapping for CRMs, chat, or feedback tools

The promise: If your data doesn't fit a standard template, we build one just for you.

Enterprise-Grade Security & Compliance

Your customer data is precious. Our migration process maintains the highest standards of security and regulatory compliance.

SOC 2 Type II

Independently audited compliance with rigorous security standards

ISO 27001

Certified information security management system

GDPR

Full compliance with EU data protection regulations

HIPAA

Certified for handling protected health information

AES-256 Encryption

Bank-grade encryption for all stored credentials

Latest TLS

Secure transfer protocol for all data in transit

Role-Based Access

We follow role-based access control for every migration project

Scheduled Deletion

Automatic data purging after migration completion

FAQ

Frequently Asked Questions

Everything you need to know about migrating from Crisp to Enchant. Can't find what you're looking for? Talk to our team.

Can I migrate Crisp conversations to Enchant as normal working tickets?

There is no native one-click migration. You need to extract data from Crisp's REST API, transform it to match Enchant's ticket/customer model, and write it via Enchant's REST API. Enchant's managed import is an alternative, but imported tickets are read-only and cannot be assigned, replied to, or included in reports.

Does Enchant support importing non-email conversations from Crisp?

No. Enchant's API only allows creating tickets of type 'email'. Chat, WhatsApp, SMS, and social conversations from Crisp will all be imported as email-type tickets. Use labels like 'migrated-from-chat' to preserve the original channel context.

Can I preserve original timestamps when migrating to Enchant?

The Enchant API does not accept custom created_at timestamps — tickets and messages receive the current system time. To preserve historical context, include original dates in ticket subjects and internal notes. Enchant's managed import may support historical timestamps, but those tickets become read-only.

What are Enchant's API rate limits for migration?

Enchant allows 100 credits per minute across the entire account with a burst limit of 6 requests per second. A 10,000-conversation migration with 5 messages each requires roughly 75,000 API calls, taking approximately 15–16 hours at a sustainable pace.

How do Crisp segments map to Enchant?

Crisp segments map to Enchant labels. Segments are free-form, case-sensitive strings; labels are structured objects scoped per inbox. Pre-create labels in Enchant before migration, normalize segment names to avoid duplicates, and build a lookup map from segment strings to label IDs.

How long does the Crisp to Enchant migration take?

Most migrations complete within 1–5 business days, depending on data volume and complexity. We provide a detailed timeline after the initial assessment and can often complete small migrations in under 24 hours.

Will my team lose access to Crisp during the migration?

No. Your source system remains fully operational throughout the entire migration. We run the migration in the background with zero downtime to your current operations.

Will there be downtime when migrating from Crisp to Enchant?

No. Our migration process is designed for zero downtime. We use a staged approach with background sync and a fast cutover, ensuring no disruption to your live business operations.

How do I validate that everything migrated correctly?

Every client receives a Migration Validation Report with comprehensive metrics including record-count parity, attachment integrity verification via checksum, and full audit logs. We also offer unlimited sample migrations so you can verify before committing.

Do I need professional help for this migration?

While simple migrations can sometimes be handled in-house, professional help ensures zero data loss, proper field mapping, and preservation of relationships between records. Our engineer-led approach catches edge cases that automated tools miss.

Does ClonePartner provide guidance before committing?

Yes. We provide a free consultation and assessment. We'll review your data structure, discuss your requirements, and provide a detailed migration plan and fixed-price quote before you commit to anything.

Still have questions?

Book a free 30-minute consultation with our migration engineers. We'll walk you through the exact approach for your Crisp→Enchant migration.

Contact our team

Ready to start your
Enchant Migration?

Join hundreds of businesses who have successfully migrated with ClonePartner. Let's discuss your migration needs and build a plan that works for you.

Book free consultation

Attention to Detail

We meticulously handle every aspect of your migration, ensuring no data is lost during transfer and mapping every field correctly between platforms.

Custom Solutions

Every business is unique. We tailor your migration strategy to match your specific requirements, workflows, and data structures.

Security & Compliance

Your customer data is handled with enterprise-grade security protocols, ensuring compliance with GDPR, HIPAA, and industry standards.

Migrate from Crisp to Enchant with precision & ease

Why teams migrate from Crisp to Enchant