Moving a rollup app from Jira Data Center to Cloud
Checked against Atlassian’s documentation on 12 October 2026.
Your site runs Jira Data Center with an app that adds estimates up to the epic, and the move to Cloud is on the calendar. This page gives Atlassian’s dates, what the migration assistant does with your apps, what Jira Cloud adds up by itself and what it does not, then what Sumline does.
Atlassian’s dates
From Atlassian’s Data Center end of life page; the dates were set out for app vendors on 8 September 2025 (Atlassian):
- 30 March 2026: new customers can no longer buy Data Center subscriptions or new Data Center apps from the Marketplace.
- 30 March 2028: the last day for existing customers to buy new Data Center subscriptions, expansions, upgrades and Marketplace apps.
- 28 March 2029: end of life. Data Center subscriptions and the Marketplace apps that go with them expire, and the products and apps become read-only.
Jira Software, Jira Service Management and Confluence Data Center are included; Bitbucket and Bamboo Data Center are not.
What happens to your rollup app
The Jira Cloud Migration Assistant lists every Marketplace app on your site in its Assess your apps step (Atlassian):
- Cloud availability: whether the app has a Cloud version.
- Migration path: whether its data can move, from Automated through Install-only, View path, Upgrade app and Contact vendor to No.
- Your decision for each app: Needed in cloud, Not needed in cloud (for example when Cloud has native functionality that replaces it), or Choose alternative, to pick a different app in Cloud later in the flow.
For apps whose vendors do not plan a Cloud version, Atlassian keeps a list of Cloud alternatives, some of them other vendors’ apps and some Jira’s own features.
Three things to check for a rollup app before you decide:
- Where its totals live. An app that adds up when you look has no totals to move. One that writes them into custom fields does, and its Migration path column says whether they move.
- What reads those totals. Filters, dashboards, board cards and Automation rules that use the app’s fields need those fields in Cloud too.
- What a Cloud licence costs. A Cloud app is licensed for every user on the site, as on Data Center, and billed by Atlassian monthly or yearly.
What Jira Cloud adds up by itself
- Time tracking’s Σ figures, one level: a story includes its subtasks’ time, an epic its stories’ own time, and nothing from the subtasks reaches the epic (JRACLOUD-70150).
- No sum of story points. Atlassian’s request for it is “Not Being Considered” (JRACLOUD-90636).
- Automation, included in every Cloud plan, writes sums into fields with rules; the guides for story points, logged time and % complete give them step by step.
- Formula fields calculate within one work item only (Atlassian).
One difference to plan for: on Data Center, Advanced Roadmaps is part of Jira Software Data Center (Atlassian). In Cloud the same tool, Plans, comes with Premium and Enterprise only (pricing). A site that moves to Standard loses the roll-ups it had in its plans; see Jira roll-ups without Premium.
Cloud also has team-managed spaces, whose story points live in a field of their own, “Story point estimate”, beside company-managed spaces’ “Story Points” (Atlassian). A rule or report written for one field reads nothing in the other.
With Sumline
Sumline is our app. It is built for Jira Cloud only: it has no Data Center version, so it is not your Data Center app’s Cloud version in the migration assistant, and you install it from the Marketplace once your site is in Cloud. It adds estimates up with nothing to migrate:
- Every level, from subtask to story, epic and initiative (initiatives need Jira Premium): story points, original estimate, time spent and remaining, children in other spaces included.
- Both story-points fields, found automatically, so company-managed spaces from your migration and new team-managed spaces add up in one tree.
- Computed when you look, from the issues as they are, so there are no totals to backfill after the move.
- On the issue, in a table per space or across spaces, and on a dashboard, with Excel and CSV downloads.
- Built on Forge and read-only: your data stays on your Atlassian site.
What it does not do: Sumline only reads, so its totals are not Jira fields. If your reports search the Data Center app’s total fields with JQL, keep an Automation rule for those, or plan that change with your team. How Sumline counts is in How the numbers are calculated.
