Jira Data Center to Cloud Migration 2026: What JCMA Misses for JSM
Jira Data Center to Cloud migration for JSM: what JCMA moves, what it skips, comment and SLA risks, Cloud prices and limits, and a checklist. Plan it.
Published Updated 13 min read

On this page
- Why move from Jira Data Center to Cloud in 2026?
- What moves, what gets rebuilt and what's at risk in a JSM Data Center to Cloud migration
- Field mapping for a JSM Data Center to Cloud migration
- Should you use JCMA, CSV or the API for a JSM Data Center to Cloud migration?
- The Jira Data Center to Cloud migration plan in phases
- Where does a JSM Data Center to Cloud migration fail?
- Jira Data Center to Cloud migration checklist
- Jira Data Center to Cloud migration FAQ
A Jira Data Center to Cloud migration for Jira Service Management (JSM) runs mostly through the Jira Cloud Migration Assistant (JCMA), Atlassian's free tool. It moves service projects, customers, request types, queues, SLAs and, on Premium or Enterprise, Assets. It does not move canned responses, mail handlers, issue collectors or linked knowledge base articles, and migrated automation arrives switched off (Atlassian JCMA docs, as of 27 Oct 2026).
If you own a JSM Data Center service desk, this guide shows what JCMA carries, what you rebuild, and where SLA and comment history can break.
Why move from Jira Data Center to Cloud in 2026?
The deadline is fixed: JSM Data Center reaches end of life on 28 Mar 2029 and turns read-only (Atlassian end of life page, as of 27 Oct 2026). Our Jira Data Center end of life guide covers the full timeline and non-Cloud options; this table keeps only the dates that change the migration plan.
| Date | What happens | What it changes in your plan |
|---|---|---|
| 13 Oct 2026 | New Cloud list prices for purchases, renewals and upgrades | Budget at today's prices; older quotes hold only until they expire |
| 1 Dec 2026 | Confluence Cloud XML site and space export reaches end of life | Back up the knowledge base from Cloud as CSV |
| 3 Dec 2026 | Usage billing starts for most meters, including automation steps and Assets objects | Re-enabled automation has a metered cost |
| 5 Apr 2027 | Opsgenie end of support; data not moved is deleted | Move alerting and on-call into JSM in the same program |
| June 2027 | Cloud Enterprise bought by then "may be eligible for a 10-20% discount" in year one | Decide on Enterprise before then |
| 28 Mar 2029 | Data Center end of life; read-only | Cutover and hypercare must be finished |
Sources: Atlassian end of life, list-price FAQ, usage, Confluence KB (updated 6 Aug 2026) and Opsgenie pages, as of 27 Oct 2026.
The new prices are current, not upcoming: a 100-agent Standard annual subscription now lists at $21,000, up from $19,700 (Atlassian pricing tables, as of 27 Oct 2026). The pricing page does not clearly say whether its headline figures are monthly or annual, so confirm on your quote. Our Jira Service Management pricing guide covers each plan and fee.
What moves, what gets rebuilt and what's at risk in a JSM Data Center to Cloud migration
JCMA moves your JSM records and most configuration, but not the behavior around them: email intake, canned responses, knowledge base links and live automation are rebuilt in Cloud.
| JSM item | Moves with JCMA | Rebuilt or at risk in Cloud |
|---|---|---|
| Service projects, request types, queues, portal settings | Yes | Per-project priorities are "not available in Cloud" |
| Customers and organizations | Yes, one new cloud account per customer | Licensed users with a cloud customer account end up with two accounts |
| Agents and groups | Yes, matched by email | Re-migrated groups keep their first membership |
| SLAs, calendars, approvals | Configuration moves | Values recalculate when an SLA is edited |
| Comments | Yes | Visibility has flipped in past JCMA versions |
| Attachments | Yes, skipped on later runs once moved | Files over 2 GB exceed the Cloud maximum |
| Assets schemas, objects, history | Yes, on Premium or Enterprise per the JCMA doc | Archived objects arrive active |
| Automation flows | Yes, disabled | Webhook, Send Web Request, Teams and Twilio actions recreated |
| Canned responses, mail handlers, issue collectors, linked KB articles | No | Recreated, reconnected or re-linked |
| App and locked custom fields | Only if the app is in Cloud | Locked fields recreated and values mapped |
Sources: Atlassian migration docs and differences page, as of 27 Oct 2026.
Running SLA timers, workflow post functions, automation logic and integrations are rebuilt in Cloud, not migrated. New to JSM Cloud? Start with our explainer on what Jira Service Management is.
Field mapping for a JSM Data Center to Cloud migration
Field mapping decides whether users, priorities, comments, SLAs, Assets and knowledge base links still work in Cloud, and each needs its own decision.
Users, agents and customers
Cloud identifies accounts by unique email, disabled users arrive active without app access, and JCMA sends no invitations (Atlassian users and groups doc, as of 27 Oct 2026). A re-migrated group keeps its first membership, which "can result in permission escalation," so change Cloud groups by hand.
Request types, priorities and the Customer Request Type field
Atlassian's differences page says per-project priorities are "not available in Cloud," and the guardrails page lists 100 priorities per space in its September 2026 rollout (both as of 27 Oct 2026). Retest the priority matrix.
Atlassian's tracker says the locked Customer Request Type field is not migrated; its values go into Request Type, so JQL naming the old field "may return unexpected results" (MIG-1794, open, as of 27 Oct 2026). With no automated workaround, edit every affected filter, queue and dashboard.
Internal and public comments
Comment visibility has broken in both directions. MIG-2305 (internal comments migrated as public) was closed as fixed, last updated 23 Sep 2025; MIG-2517 (public comments migrated as internal when visibility was unset, for example by a sync automation) was fixed on 8 May 2026 (Atlassian tracker, as of 27 Oct 2026). The workaround sets sd.public.comment to {"internal": false} through the Cloud REST API.
Keep JCMA updated and sample comments from every project after each test run. Do not fill gaps with CSV, which makes all JSM comments public (Jira Cloud CSV import doc, as of 27 Oct 2026).
SLAs and SLA history
Any SLA configuration change in JSM Cloud recalculates all open issues, and a destructive recalculation "destroys all existing SLA data" (Atlassian KB, updated 25 Jun 2026). Cloud cannot copy SLA configuration between projects (Atlassian differences page, as of 27 Oct 2026). Freeze SLA edits until you capture the reporting baseline. A "We couldn't import Time Metric" error means work items point to a project outside the plan; remove or re-create that SLA first (Atlassian KB, updated 26 Sep 2025).
Attachments, Assets and CIs
Jira Cloud allows 1 GB per file by default and 2 GB at most (Atlassian attachment settings, as of 27 Oct 2026). JCMA moves Assets schemas, objects, attachments and history, but archived objects arrive as non-archived. Cloud caps one custom field at 20 objects per work item, allows 2 unique constraints per object type, and limits Name and Description to 255 characters (Atlassian Assets migration doc, as of 27 Oct 2026). Migrate schemas first: if projects go first, "linking will not happen."
Knowledge base, canned responses and email
Re-link Confluence spaces to each service project after they move. Canned responses exist in JSM Cloud (JSDCLOUD-631, resolved 15 Jun 2023), but JCMA does not carry them and only project admins can create shared ones. Incoming email uses POP/IMAP or a connected Google, Microsoft or custom address (Atlassian differences page, as of 27 Oct 2026). Cloud allows 700 fields and 150 work types per space (Atlassian guardrails page, as of 27 Oct 2026).
Should you use JCMA, CSV or the API for a JSM Data Center to Cloud migration?
Use JCMA for the main move, CSV only for small gap-fills, and the REST API for targeted fixes.
| Method | What Atlassian says | Limits for JSM | Use it for |
|---|---|---|---|
| Jira Cloud Migration Assistant | Recommended and free; needs a supported Data Center version; will not overwrite Cloud data | Automation disabled; Assets on Premium or Enterprise per the JCMA doc | The main move |
| Jira Cloud CSV import | "isn't a recommended migration method due to its limitations" | About 1,500 work items per file; statuses must exist; comments become public | Small gap-fills |
| Data Center filter export | 1,000 issues per export by default | Raising the cap risks memory errors | Reconciliation counts |
| Jira Cloud REST API | Points-based rate limits | 65,000 points an hour for apps; HTTP 429 | Comment and field fixes |
Sources: Atlassian migration, CSV, filter export and rate limiting docs, as of 27 Oct 2026.
Jira Cloud rate limits for fix scripts
Forge, Connect and OAuth 2.0 apps share 65,000 points per hour, reset each UTC hour; API token traffic stays on burst limits (Atlassian developer docs, last updated 23 Oct 2026). One work item takes at most 20 writes per 2 seconds and 100 per 30 seconds, so spread fixes across work items and honor Retry-After.
Automation after go-live is metered
Standard, Premium and Enterprise include 3,000, 6,500 or 9,500 automation steps per user per month, and extra steps bill at $0.50 per 1,000 from 3 Dec 2026. A trigger that finds no match still counts as one step (Atlassian pricing page and usage doc, as of 27 Oct 2026), so narrow broad triggers before enabling them.
Atlassian's pages disagree on the default: the usage page says "Extra usage is enabled by default," the list-price FAQ says "Extra usage billing requires opt-in." With extra usage off at 100%, flows stop until usage resets, routing and SLA rules included.
The Jira Data Center to Cloud migration plan in phases
Plan six phases, and let the test migration in a cloud migration trial site set your cutover date.
- Discover. Inventory projects, SLAs, queues, automation, apps, Assets, knowledge base spaces, mail handlers and canned responses. Activate JSM on the cloud site and run the JCMA pre-checks. With 1,000 or more seats, you can apply for FastShift, which Atlassian says cuts 12 to 16 months to 2 to 6 months (as of 27 Oct 2026).
- Map. Decide on duplicate emails, groups, priorities, SLA goals and app replacements. Fix SLAs that would fail with "Time Metric" errors.
- Test migration. A cloud migration trial matches your user tier and remaining Data Center subscription, up to 12 months and 20,000 users. Trial data is not backed up, is deleted 15 days after the trial, and trials send at most 100 outbound emails a day (Atlassian trials doc, as of 27 Oct 2026). Our test migration checklist lists what a trial run should prove.
- Cutover with a freeze. Pre-migrate users, groups and attachments while agents work, then Assets schemas. Freeze Data Center with a Browse-only permission scheme. Atlassian documents no issue-level delta sync, so run each project's final issue migration once, inside the freeze.
- Reconcile. Compare counts, SLA states, customers, Assets and sampled comments. Connect email, re-link the knowledge base, rebuild canned responses, then enable tested automation.
- Hypercare. Watch SLA breaches, email intake and automation usage daily.
Atlassian recommends at least 16 CPUs per node above 500 users and pausing antivirus, XML backups and full reindexing during the run (Atlassian speed doc, as of 27 Oct 2026).
Where does a JSM Data Center to Cloud migration fail?
Most JSM cutover failures come from items JCMA never touched.
- Email requests go nowhere until the email channel replaces the mail handlers.
- Portal article suggestions vanish until knowledge base spaces are re-linked.
- Routing and SLA automation stays off until someone enables it.
- Comment visibility flips where visibility properties were unset (MIG-2517).
- Filters break silently if JQL still names Customer Request Type (MIG-1794).
- Opsgenie is left behind: data not moved by 5 Apr 2027 is deleted.
If Cloud no longer fits, our Jira to ServiceNow migration guide covers another route.
Jira Data Center to Cloud migration checklist
Run these eleven checks before and during a Jira Service Management Data Center to Cloud migration.
- Confirm in writing which plan your Assets migration needs, and check the extra-usage setting.
- Update JCMA, Automation for Jira (7.2.6 or later) and Data Center to supported versions.
- Activate JSM on the cloud site and run the JCMA pre-checks.
- Fix SLAs that reference projects outside the migration plan.
- Resolve duplicate emails between agents and customers.
- List attachments over 2 GB; count fields and work types against 700 and 150.
- Search filters, queues and dashboards for Customer Request Type.
- Pre-migrate users, groups and attachments, then Assets schemas.
- Run a test migration; sample comments, SLAs, priorities and portal search.
- Freeze Data Center, run the final migration, connect email, rebuild canned responses and re-link the knowledge base.
- Reconcile, then enable tested automation before agents return.
Facts checked October 27, 2026 from Jira Cloud Migration Assistant docs, Atlassian Data Center end of life, Atlassian Service Collection pricing, Atlassian cloud pricing tables, Atlassian usage-based pricing and Atlassian public bug tracker. No vendor paid for this article. How we research
Jira Data Center to Cloud migration FAQ
How long does a Jira Data Center to Cloud migration take?
There is no neutral public benchmark. Atlassian says it "can't provide an exact estimation of downtime" and recommends a test migration to estimate it (as of 27 Oct 2026). For 1,000 or more seats, Atlassian claims FastShift takes 2 to 6 months. Duration depends on volume, attachments, Assets, apps and automation to rebuild.
Does the Jira Cloud Migration Assistant migrate JSM SLAs?
Yes, JCMA migrates SLA configuration, calendars and approvals. Values can still change: any SLA edit in Cloud recalculates open issues, and a destructive recalculation replaces historic results (Atlassian KB, updated 25 Jun 2026). SLAs referencing projects outside the plan fail with a "Time Metric" error. Capture an SLA baseline and freeze SLA edits until reconciliation is signed off.
Are automation rules migrated to Jira Cloud?
Yes, but "All migrated automation flows are disabled on the cloud by default post migration" (Atlassian, as of 27 Oct 2026). Global flows move only with the all-flows option, and webhook, Send Web Request, Microsoft Teams and Twilio actions are recreated. From 3 Dec 2026, steps beyond your allowance bill at $0.50 per 1,000.
Can I migrate Assets on the JSM Standard plan?
Atlassian's sources conflict. The JCMA Assets doc says "You need to have a Jira Service Management Premium or Enterprise plan to migrate Assets to your cloud instance," while the Service Collection pricing page lists 5,000 Assets objects on Standard (both as of 27 Oct 2026). Get written confirmation before you sign the Cloud order.
What happens to the Confluence knowledge base linked to JSM?
JCMA does not migrate knowledge base articles linked to service projects. The Confluence spaces move separately; re-link them to each service project so portal suggestions work again. Confluence Cloud XML site and space export reaches end of life on 1 Dec 2026, with CSV export as the supported alternative (Atlassian KB, updated 6 Aug 2026).
Written by
Ayush BothraFounding Member, MigrateX
Ayush writes about ITSM platforms, pricing and what it takes to move a service desk to a new platform without losing its history.


