Desk365 to Enchant Migration

MIGRATION OVERVIEW

Why teams migrate from Desk365 to Enchant

The core problem

Migrating from Desk365 to Enchant requires a fully custom API-driven migration with no native import path that preserves editable ticket history. Desk365 is a highly relational helpdesk with companies, groups, SLA policies, custom fields, ticket types, and contacts enforced as structured objects, while Enchant is an inbox-centric shared inbox with a deliberately flat data model built around tickets, customers, labels, and messages. The directional mismatch means that critical Desk365 constructs — including custom fields, company objects, SLA policies, ticket types, and priority fields — have no direct Enchant equivalents and must be flattened into labels, appended to message bodies, stored in customer summary fields, or discarded entirely. Additionally, Enchant's API does not expose writable timestamp fields, meaning original creation and modification dates cannot be preserved, and agent users must be created manually before any migration code runs.

Why this matters for your migration

KEY CHALLENGES

What makes this migration complex

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

Most Critical

No Native Custom Fields

Enchant has no custom field objects on tickets, so all Desk365 `cf_*` fields must be flattened into the first message body, stored in the customer `summary` field, or permanently discarded before migration begins.

Blocks all downstream imports if mapped wrong

Company Object Elimination

Desk365's company object has no equivalent in Enchant, requiring teams to either flatten company identity into the customer `summary` field or represent company membership via labels, both of which reduce queryability.

Ticket Type vs. Channel Collision

Desk365 uses `type` as a business classification (Incident, Problem, Request) while Enchant uses `type` as the transport channel (email, chat, phone), meaning values cannot be copied directly and must be remapped to Enchant labels.

Timestamp Immutability in Enchant

Enchant's API does not expose writable `created_at` or `updated_at` fields, so all migrated tickets and messages will reflect their import timestamp rather than their original Desk365 creation dates.

Attachment Pre-Upload Requirement

Every attachment must be individually base64-encoded and uploaded via `POST /api/v1/attachments` before it can be linked to a message by `attachment_ids`, creating a sequential dependency that significantly increases migration complexity and runtime.

Agent and Inbox Pre-Provisioning Required

Enchant does not expose a public API endpoint for user creation, and inboxes must be configured manually, meaning all agents and inbox-to-group mappings must be established before any API migration code can execute.

MIGRATION RISK ASSESSMENT

Every migration risk, already solved

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

High complexity

Companies

Enchant has no company object, so all company associations are permanently lost as structured data and must be manually flattened into customer summary fields or represented as labels before migration.

Solved
Custom Fields

All Desk365 `cf_*` custom fields are completely unsupported in Enchant as structured, filterable fields and must be either appended to message body text or discarded, resulting in permanent loss of field-level queryability.

Solved
SLA Policies

Enchant has no SLA management functionality whatsoever, so all Desk365 SLA policies, breach data, and associated reporting are permanently non-migratable and require a full process redesign.

Solved
Watchers and Share To

Neither Desk365 Watchers nor Share To have direct equivalents in Enchant, and both require full workflow redesign rather than data migration, representing a potential operational gap at cutover.

Solved

Custom engineering

Tickets

Tickets can be recreated via API but are restricted to `type: email` regardless of their original Desk365 channel, and all tickets will lose their original creation timestamps due to Enchant's immutable `created_at` field.

Handled
Contacts / Customers

Enchant splits identity into a Customer object and a Contact channel object, requiring careful mapping logic to avoid duplicate customer records during the deduplication process on ticket creation.

Handled
Attachments

Attachments are migratable but require individual base64 encoding and sequential pre-upload via the Enchant attachments endpoint before linking, making them the highest-effort per-record operation in the pipeline.

Handled
Groups / Inboxes

Desk365 groups do not map 1:1 to Enchant inboxes because Enchant inboxes also carry channel configuration, permissions, and language settings, requiring manual provisioning and scoping decisions before migration begins.

Handled

Clean transfer

Replies and Notes

Desk365 replies and internal notes map cleanly to Enchant message types (`reply` with `direction: in/out` and `note`), with the primary risk being loss of original timestamps rather than structural data loss.

Clean
Categories and Labels

Desk365 categories, sub-categories, ticket types, and priorities all map to Enchant labels, but labels must be created manually in Enchant and a complete ID mapping table must be built before ticket creation begins.

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 Desk365 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 Desk365 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 Desk365 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 Desk365 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 Desk365 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 30 days of engineer-assigned support post go-live.

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

No two teams configure Desk365 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 Desk365 to Enchant. Can't find what you're looking for? Talk to our team.

Can I migrate Desk365 tickets to Enchant using CSV export?

Only partially. Desk365's CSV export includes ticket metadata but not conversation threads, replies, notes, or attachments. For a full migration with conversation history, you must use the Desk365 API v3 for extraction and the Enchant REST API for loading.

What happens to Desk365 custom fields when migrating to Enchant?

Enchant does not support custom fields. You can append custom field values to the ticket's first message body as formatted text, store customer-level data in Enchant's customer summary field, convert boolean or dropdown values to labels, or discard the data. The structured, filterable nature of the fields is lost regardless.

Does Enchant preserve original ticket timestamps during API migration?

Enchant's published API docs do not document writable created_at fields on tickets or messages. Migrated records may carry the timestamp of when they were created during migration. Confirm with Enchant support if this is a hard requirement, or append original dates to message bodies as annotations.

Does Desk365 Type map to Enchant type?

No. Desk365 Type is a business classification (Question, Incident, Problem, Request). Enchant type is the channel (email, chat, phone, WhatsApp). Copying values straight across will corrupt your data. Use Enchant labels for the business classification instead.

What are the API rate limits for Desk365 and Enchant during migration?

Desk365 Standard plan allows 100 API calls per hour; Plus and Premium plans allow 50 calls per minute. Enchant allows 100 credits per minute with a burst limit of 6 requests per second. Extract Desk365 data to local staging first, then load into Enchant as a separate phase to decouple the two rate limiters.

How long does the Desk365 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 Desk365 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 Desk365 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 Desk365→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 Desk365 to Enchant with precision & ease

Why teams migrate from Desk365 to Enchant