Desk365 to LiveChat Migration

MIGRATION OVERVIEW

Why teams migrate from Desk365 to LiveChat

The core problem

Migrating from Desk365 to LiveChat involves an architectural shift rather than a simple data transfer, as no native migration path exists between the two platforms. Desk365 is a ticket-centric helpdesk deeply integrated with the Microsoft 365 ecosystem using Azure AD identities, while LiveChat is a real-time chat platform whose legacy ticketing was fully sunset in January 2025 and replaced by HelpDesk, a separate product. The migration requires a split-target architecture: historical ticket data and conversation threads must be extracted via the Desk365 REST API v3, transformed from a replies-and-notes model into HelpDesk event payloads, and loaded via the HelpDesk import API (POST /v1/importedTickets), while LiveChat itself requires fresh configuration rather than data migration. Automation rules, SLA policies, knowledge base articles, and asset management data have no import path and must be rebuilt manually, requiring an estimated 2–5 weeks for a mid-size migration.

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 LiveChat migration.

Most Critical

No Native Migration Path

There is no built-in export or import tool connecting Desk365 and HelpDesk, requiring a fully custom extraction, transformation, and load pipeline built against two separate REST APIs.

Blocks all downstream imports if mapped wrong

Conversation Data Model Mismatch

Desk365 structures conversations as replies and notes on tickets, while HelpDesk organizes them as typed event payloads, meaning each reply, note, and agent message must be individually transformed into the correct event schema before import.

Azure AD Identity Resolution

Desk365 identifies agents and contacts using Azure Active Directory Object IDs and User Principal Names, which must be resolved and mapped to standard email addresses before tickets can be assigned in HelpDesk.

API Rate Limit Constraints

The Desk365 API v3 enforces a ceiling of 10,000 tickets per hour, and real-world throughput with 429 backoffs and per-ticket conversation requests typically runs at 30–50% of that limit, significantly extending extraction time for large datasets.

Split-Target Architecture Required

Ticket data must be routed to HelpDesk while LiveChat requires independent configuration, forcing teams to execute and coordinate two parallel workstreams rather than a single platform-to-platform migration.

Manual Rebuild of Configuration Objects

SLA policies, automation rules, approval workflows, and knowledge base content have no import API in HelpDesk and must be fully recreated by hand, adding significant post-migration configuration effort.

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 LiveChat and built proven solutions for each one.

High complexity

Conversation Threads

Full conversation threads require combining two separate Desk365 API calls per ticket and transforming each reply, note, and message into a typed HelpDesk event payload; a direct field copy will produce malformed or incomplete records.

Solved
Attachments

Attachments are referenced within conversation threads and must be individually fetched and re-uploaded during transformation, making them one of the most fragile and time-consuming elements of the migration.

Solved
SLA Policies

SLA policies have no import path into HelpDesk and must be fully rebuilt manually, with no automated way to retroactively apply SLA breach status to historical imported tickets.

Solved
Automation Rules

All automation rules, triggers, and workflow logic are configuration objects with no import API and must be recreated from scratch in HelpDesk, requiring thorough documentation of existing rules before cutover.

Solved
Knowledge Base Articles

Desk365 provides an API endpoint to retrieve knowledge base articles, but HelpDesk has no corresponding import API, requiring all articles to be manually recreated or migrated to a separate standalone knowledge base tool.

Solved

Custom engineering

Tickets

Ticket metadata migrates via the HelpDesk import API, but the original ticket description is excluded from the Desk365 API response by default and must be explicitly requested with the description=1 parameter to avoid data loss.

Handled
Custom Fields

Custom fields using the Desk365 cf_ prefix must be manually pre-created in HelpDesk before import begins, as any ticket referencing a non-existent custom field will fail or lose that field's data.

Handled
Categories and Subcategories

Desk365's native category and subcategory hierarchy has no direct equivalent in HelpDesk and must be flattened into tags or custom fields, potentially losing structural context used in reporting or routing.

Handled
Time Entries

Time entries are available via a separate Desk365 API surface but have no corresponding field in the HelpDesk import payload, meaning this data must be preserved in external reporting exports or summarized into custom fields to avoid permanent loss.

Handled

Clean transfer

Contacts and Companies

HelpDesk auto-creates contact records from requester email addresses on import, reducing manual effort, though the identity mapping from Desk365 Azure AD identifiers to email addresses must be completed accurately beforehand.

Clean

What Our Customers Say

Real migration stories

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.”

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.”

See all customer stories →

CUSTOM MIGRATION

Fully customizable engineer-led migration

Tailor your migration from Desk365 to LiveChat 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 LiveChat 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 LiveChat, 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 LiveChat 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 LiveChat 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 LiveChat
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 LiveChat 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 LiveChat. Can't find what you're looking for? Talk to our team.

Can I migrate Desk365 tickets directly to LiveChat?

No. LiveChat's legacy ticketing was sunset by January 31, 2025. Ticket data must go to HelpDesk (helpdesk.com), a separate product by LiveChat's parent company Text. LiveChat itself only handles real-time chat conversations.

Does Desk365 CSV export include conversation history?

No. Desk365 CSV exports contain only ticket metadata (subject, status, priority, custom fields). Full conversation threads — including replies, notes, and attachments — require extraction via the Desk365 REST API v3. You also need to export both All Tickets and Archived Tickets separately for complete coverage.

What are Desk365 API rate limits for migration?

Desk365 API v3 allows 30, 50, or 100 tickets per call via the ticket_count parameter, with a maximum of 10,000 tickets per hour. Real-world throughput with backoffs and conversation-detail requests runs at 30–50% of theoretical max.

How long does a Desk365 to LiveChat migration take?

A small migration (under 5,000 tickets) takes 1–2 weeks. Medium (5K–30K) takes 2–4 weeks. Large (30K–100K) takes 4–6 weeks. These estimates include scripting, dry runs, and validation — not just data transfer.

What Desk365 features don't exist in LiveChat or HelpDesk?

SLA policies, approval workflows, asset management, knowledge base import, Microsoft Teams bot integration, dedicated PHI/PII fields, time entries, and category/subcategory hierarchies have no direct equivalent. These must be rebuilt manually or replaced with alternative tools.

How long does the Desk365 to LiveChat 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 LiveChat?

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→LiveChat migration.

Contact our team

Ready to start your
LiveChat 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 LiveChat with precision & ease

Why teams migrate from Desk365 to LiveChat