Migrate from Deskpro to Jira Service Management with precision & ease

A seamless, customizable migration solution for moving your Deskpro data with perfect fidelity and minimal disruption.

Book free consultation
Deskpro
Jira Service Management
MIGRATION OVERVIEW

Why teams migrate from Deskpro to Jira Service Management

There is no native migration path from Deskpro to Jira Service Management; every approach requires extracting data from Deskpro and transforming it to fit JSM's fundamentally different data model. The core challenge lies in converting Deskpro's HTML-threaded ticket messages into Atlassian Document Format (ADF) for JSM's REST API v3, and resolving Deskpro's email-based People records to Jira accountIds. CSV export captures only flat ticket metadata—stripping conversation threads, attachments, and customer–organization relationships—so API-based migration is required for any production environment that needs full data fidelity.
KEY CHALLENGES

What makes this migration complex

These are the architectural mismatches and technical hurdles specific to a Deskpro to Jira Service Management migration.

Most Critical

HTML to ADF Conversion

Deskpro stores ticket messages as HTML content, which must be programmatically converted to Atlassian Document Format (ADF) required by JSM's v3 REST API, a non-trivial transformation that can silently drop formatting or inline content.

User Identity Resolution

Deskpro identifies users via email-based People records, while JSM requires Atlassian accountIds, necessitating a lookup and mapping layer to correctly attribute tickets, comments, and customer relationships.

Conversation Thread Model Mismatch

Deskpro models conversations as multi-message threads with distinct reply types (agent_reply, user reply, note), whereas JSM uses a flat comments model with only public and internal visibility flags, requiring careful type mapping.

Custom Field Scope Differences

Deskpro supports custom fields at the ticket, person, and organization levels independently, while JSM scopes custom fields per issue type within a project, requiring schema redesign and potential data consolidation.

Archived and Inactive Ticket Extraction

Deskpro's API returns only active tickets by default, so resolved and archived tickets must be explicitly requested with status filters to avoid silently omitting historical data during extraction.

Knowledge Base Platform Separation

Deskpro includes a built-in knowledge base, but JSM relies on Confluence as a separate product for KB content, requiring an additional migration workstream with its own content transformation and permission mapping.

COMPLETE COVERAGE

Intelligent Human-Verified Data Mapping

Our migration engineer precisely maps every data point from Deskpro to Jira Service Management, ensuring perfect continuity for your customer support operations.

Deskpro
Jira Service Management
Tickets
Requests (Issues)
Ticket Messages
Request Comments
Ticket Attachments
Request Attachments
Ticket Custom Fields
Custom Fields
People (Users)
Customers
Agents
Users (Agents)
Organizations
Organizations
Agent Groups
Groups
Departments
Service Desks (Projects)
Knowledge Base Articles
Knowledge Base Articles
Knowledge Base Categories
Not Available
Ticket Labels
Components
Ticket SLAs
Not Available
Snippets (Macros)
Not Available
People Custom Fields
Custom Fields

Looking for more entity mappings?

Contact our team
MIGRATION RISK ASSESSMENT

Every migration risk, already solved

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

Migration Challenge ClonePartner Status
High Complexity —
Solved
Conversation Threads
Deskpro's threaded message model with HTML bodies must be converted to ADF-formatted JSM comments, with CSV import offering no thread preservation and making all comments public.
Solved
Attachments
Each attachment requires individual API calls for both download from Deskpro and upload to JSM, with no bulk transfer mechanism and significant impact on migration runtime and rate limits.
Solved
Contacts (People)
Deskpro People records with rich custom fields must be resolved to Atlassian accountIds, and JSM's customer entity supports far fewer custom profile fields than Deskpro's person model.
Solved
Custom Fields
Deskpro's per-ticket, per-person, and per-organization custom fields must be restructured into JSM's project-scoped, issue-type-scoped field model, with Deskpro's CSV export capping at approximately 55 fields.
Solved
Knowledge Base Articles
Deskpro's built-in KB content must be migrated to Confluence as a separate workstream, requiring HTML-to-Confluence-storage-format conversion and permission model redesign.
Solved
Custom Engineering —
Handled
Tickets
Core ticket metadata maps reasonably well to JSM issues, but preserving original timestamps, status history, and multi-department assignments requires workarounds and careful API usage.
Handled
Organizations
Both platforms support organizations, but the customer-to-organization relationship model differs, and sites created after October 2025 may route organization features through Customer Service Management rather than JSM alone.
Handled
Internal Notes
Deskpro agent notes map to JSM internal comments, but CSV import makes all comments public, so only API-based migration can preserve the internal/public distinction.
Handled
SLA Policies
Deskpro's per-department and per-organization SLA rules must be manually recreated as JSM SLA policies scoped to projects, with no automated migration path for SLA configurations.
Handled
Departments and Agent Groups
Deskpro departments map to JSM projects and queues but the mapping is not one-to-one, requiring decisions about project structure and potentially fanning out departments across multiple service projects.
Handled
5 high-complexity solved
5 custom-engineered
CUSTOM MIGRATION

Fully customizable engineer-led migration

Tailor your migration from Deskpro to Jira Service Management exactly to your needs with our flexible customization options. Our experts will configure the perfect migration plan for your business.

Migration Filters

Conversation Type

Filter by chat, email, or social media conversations

Tag-Based Selection

Migrate tickets with specific tags only

User Selection

Migrate tickets for specific users or agents

Time Range

Migrate tickets from a specific time period

Data Types

Tickets & Conversations

Full conversation history with all metadata

Automations & Macros

Workflows, templates, and automation rules

Knowledge Base

Articles, categories, and help center content

Customer Profiles

Customer information and interaction history

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 Deskpro to Jira Service Management 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

1

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.

2

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.

3

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.

4

Full Migration

2 days · ClonePartner

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

5

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.

Timeline is an estimate. Actual duration depends on API rate limits, data complexity, and your team's availability.

Get an exact timeline

Complete Technical Guide

Deskpro to Jira Service Management Migration: Technical Guide

Deskpro to JSM migration requires API-based extraction to preserve ticket threads, attachments, and internal notes. CSV flattens everything. Plan for HTML-to-ADF conversion and per-issue limits.

27 min read

Read the guide

Pros and cons of different migration options

Choosing the right approach is key because migrating from Deskpro to Jira Service Management 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:

  1. Speed of automation for bulk record migration
  2. Precision of engineers verifying integrity and business logic
  3. Pilot migrations and sandbox testing to catch issues early
  4. 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 Deskpro and Jira Service Management 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:

  1. Field mapping and transformation
  2. Pagination, rate-limit handling, and throttling
  3. Preserving conversation threads, attachments, and internal notes
  4. 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:

  1. 100% record-count parity between your Deskpro data and Jira Service Management
  2. Zero downtime during staged cutovers
  3. 99.9% attachment integrity (verified via checksum)
  4. 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 Deskpro or Jira Service Management 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:

  1. Custom fields, ticket forms, and workflows
  2. Multi-brand or multi-language setups
  3. Historical imports and partial (date-based) migrations
  4. 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 Deskpro to Jira Service Management. Can't find what you're looking for? Talk to our team.

Can I migrate Deskpro to Jira Service Management using CSV export?
Only partially. Deskpro's CSV export captures ticket metadata but does not include full conversation threads, attachments, or customer–organization relationships. Deskpro reports also have a ~55-field limit. JSM CSV imports make all comments public, so you lose internal/private note distinctions. For anything beyond basic ticket data, you need an API-based migration.
What are the API rate limits for Deskpro and JSM during migration?
Deskpro Cloud has a default global rate limit configurable per API key; contact support@deskpro.com to raise it before a migration. JSM Cloud enforces burst rate limits per-tenant per-API — exceeding them returns a 429 error with a Retry-After header. API token-based traffic uses burst limits, not the newer points-based system introduced in March 2026.
How long does a Deskpro to JSM migration take?
Timelines depend on volume. Under 10K tickets with minimal attachments: 3–5 business days. 10K–100K tickets with attachments: 1–3 weeks. Over 100K tickets: 3–6 weeks. These estimates include test runs, validation, and cutover.
Does Jira Service Management have per-issue limits that affect migration?
Yes. Jira Cloud enforces per-issue limits: 5,000 comments, 2,000 attachments, 2,000 issue links, and 2,000 remote links per issue. Deskpro tickets with very long conversation threads exceeding 5,000 messages may need to be split across multiple linked JSM issues.
How do I prevent JSM from sending emails to customers during the migration?
Disable outgoing email notifications in your Jira Service Management project settings before running the migration script. Otherwise, customers will receive notification emails for every historical ticket being recreated. Re-enable notifications only after migration and validation are complete.
How long does the Deskpro to Jira Service Management 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 Deskpro 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 Deskpro to Jira Service Management?
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 Deskpro→Jira Service Management migration.

Contact our team

Ready to start your
Jira Service Management 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.