Desk365 to Intercom Migration

MIGRATION OVERVIEW

Why teams migrate from Desk365 to Intercom

The core problem

Migrating from Desk365 to Intercom requires translating a ticket-centric, Microsoft 365-integrated helpdesk into a contact-centric, messenger-first platform — no native migration path exists between the two systems. The fundamental data model difference is significant: Desk365 organizes work around tickets linked to Microsoft Azure AD identities, while Intercom requires all tickets and conversations to be anchored to pre-existing Contact records identified by email or external ID. Custom migration scripting is required to extract threaded conversations from Desk365's separate reply and notes endpoints, sanitize Microsoft Teams and HTML-formatted content, flatten multi-level custom fields into Intercom's flat attribute schema, and handle file attachments via intermediary storage. Several Desk365 objects — including Time Entries, Asset Management records, Approval workflows, Change Management items, and SLA policies — have no Intercom equivalent and must be archived externally.

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

Most Critical

Threaded Conversation Extraction

Desk365 stores ticket replies and internal notes at separate API endpoints from the ticket metadata, requiring a multi-step extraction script that stitches the initial description, replies, and notes into a single chronological record per ticket before import.

Blocks all downstream imports if mapped wrong

Azure AD Identity Detachment

Desk365 uses Microsoft 365 and Azure Active Directory for agent and user identity, meaning User Principal Names (UPNs) must be explicitly mapped to Intercom email-based or external_id contact profiles before any ticket association can be established.

Multi-Level Custom Field Flattening

Desk365 supports dynamically populated multi-level fields where child options depend on parent selections, but Intercom only supports flat custom attributes (string, integer, float, boolean, datetime, list), requiring hierarchical field logic to be decomposed or collapsed before import.

Teams Formatting Sanitization

Desk365 captures Microsoft Teams chat logs and rich HTML emails containing nested tables, adaptive cards, and Microsoft Word-style inline CSS that must be sanitized before import because Intercom only supports a specific subset of HTML in conversation parts.

Conversation Part Volume Limits

Intercom enforces a hard limit of 500 parts per ticket, so Desk365 tickets with large reply and internal note counts must be identified and handled — through truncation, summarization, or splitting — before attempting import.

Contact-First Import Sequencing

Intercom requires all Contact records to exist before tickets can be created, meaning the migration must be strictly sequenced — contacts and companies first, agent mappings second, and tickets last — with deduplication applied to Desk365 contacts before any import begins.

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

High complexity

Tickets

Tickets require a pre-migration decision on whether to map to Intercom Tickets or Conversations, must be extracted across multiple endpoints, and are subject to the 500 conversation parts per ticket limit — making them the highest-complexity entity in the migration.

Solved
Custom Fields

Desk365's multi-level custom fields have no equivalent in Intercom's flat attribute schema, requiring custom transformation logic to decompose or collapse hierarchical field structures before import.

Solved
Ticket Replies and Internal Notes

Replies and notes are stored at separate Desk365 API endpoints from ticket metadata and must be individually fetched per ticket ID, stitched chronologically, and sanitized of unsupported HTML before being posted as Ticket Parts in Intercom.

Solved
Attachments

Desk365's CSV export contains only attachment references rather than files, and binary files must be routed through intermediary storage before being re-uploaded to Intercom, adding pipeline complexity and potential for data loss.

Solved
SLA Policies

Desk365 SLA policies have no API import path in Intercom and must be manually rebuilt in the Intercom admin UI, with no automated migration option available.

Solved
Time Entries / Asset Records

Desk365 Time Entries, Asset Management records, Approval workflows, and Change Management items have no equivalent objects in Intercom and must be archived externally as CSV or JSON, resulting in permanent functional data loss within the platform.

Solved

Custom engineering

Contacts

Contacts require deduplication before import, carry a billing risk if large volumes of inactive historical contacts trigger a plan tier upgrade, and must be created before any ticket association can be established.

Handled
Knowledge Base Articles

Article HTML bodies are generally portable via the Intercom Articles API, but category and folder hierarchy must be mapped to Intercom Collections, which support only up to three levels of nesting.

Handled

Clean transfer

Companies

Companies map cleanly to Intercom's Company object via company_id or name and can be created via standard API calls with minimal transformation required.

Clean
Tags

Tags are supported natively in Intercom and can be applied post-creation via API, making them a low-risk entity provided the tagging step is sequenced after ticket and contact creation.

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 Intercom 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 Intercom 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 Intercom, 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 Intercom 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 Intercom 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 Intercom
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 Desk365 or Intercom 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 Intercom. Can't find what you're looking for? Talk to our team.

Can I export all my data from Desk365?

Desk365 offers CSV exports from the UI for ticket metadata and API v3 for full programmatic access including ticket descriptions in HTML and plain text. The CSV export does not include individual replies, attachments, or internal notes — use the API for complete data extraction.

How long does a Desk365 to Intercom migration take?

For teams with under 5,000 tickets and simple fields, expect 3–5 days. Mid-size migrations (5K–20K tickets) take 1–2 weeks. Larger datasets with attachments and complex custom fields can take 2–6 weeks depending on scope.

Does Intercom have a built-in import tool for Desk365?

No. Intercom does not offer a native Desk365 import. You need to extract data via Desk365's API or CSV export, transform it to match Intercom's data model, and import using Intercom's REST API (Contacts, Tickets, Articles endpoints).

What Desk365 data cannot be migrated to Intercom?

Time entries, asset management records, approval/change management workflows, and SLA policies have no Intercom equivalent. These should be exported as CSV or JSON archives. Automation rules and Microsoft Teams bot configurations must be manually rebuilt.

How do I keep historical timestamps when importing into Intercom?

If you import Desk365 tickets as Intercom Tickets, the reply endpoint supports a created_at parameter for preserving original dates. If you use Conversations instead, the creation timestamp cannot be backdated — store the original date in a custom attribute and prepend it to the message body.

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

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

Contact our team

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

Why teams migrate from Desk365 to Intercom