Eriksen Labs Support
  1. Eriksen Labs
  2. Moving from Data Center

Moving from Data Center

Bring your diagrams, templates and repeats to Cloud

Atlassian ends Data Center on 28 March 2029. If your Confluence, Jira or Jira Service Management is moving to Cloud, this page says what our three apps do there, how your Mermaid and PlantUML diagrams, issue templates and recurring requests come across, and what you set up again.

  • Nothing moves by itself: you copy diagrams and set templates and schedules up again. This page says how.
  • All three apps run on Atlassian Forge and send nothing outside Atlassian.
  • All three are listed for Atlassian Isolated Cloud as well as the normal cloud.
Mermaid & PlantUML Diagrams for Confluence Mermaid and PlantUML as text in the page, drawn in the reader’s browser. Issue Templates & Create Defaults for Jira Templates for new work items, opened in Jira’s own Create dialog. Recurring Requests & Templates for Jira Service Management Customers raise a request again, or set it to repeat, from the portal.

Atlassian’s timeline

Three dates to plan around

  1. New customers can no longer buy Data Center subscriptions or Data Center apps.
  2. The last day existing customers can buy new Data Center subscriptions, apps and expansions.
  3. End of life. Data Center subscriptions and their Marketplace apps expire, and become read-only.

Source: Data Center End of Life, Atlassian (read 19 November 2026). Atlassian also offers extended maintenance for some customers by exception; its page says how.

Confluence

Mermaid and PlantUML diagrams: copy the text, paste it in Cloud

Mermaid and PlantUML diagrams are text, and the text is what you bring. In Cloud, Mermaid & PlantUML Diagrams has a macro for each: Mermaid Diagram (/mermaid) and PlantUML Diagram (/plantuml), in one app with one license. Both are drawn in the reader’s browser, inside the page. The app asks for no permissions and sends nothing outside Atlassian.

What we checked

  • A macro from a Data Center app that has no Cloud version shows as an “unknown macro” box after a migration. That is Atlassian’s own description in CONFCLOUD-73039, and its workaround is to deal with those macros before you migrate.
  • Our macros do not pick up another app’s diagrams on their own. Each diagram is added again, with its text.
  • So copy each diagram’s text while Data Center still runs, and keep it with the page’s title.

Mermaid

  1. Copy the diagram’s text from the old macro’s editor.
  2. In Cloud, type /mermaid, choose Mermaid Diagram and paste.
  3. Check the preview and save.

If what you copied carries the page’s storage format, another app’s saved format or a Markdown code fence, the editor takes the diagram out and says what it removed. Moving a diagram from another Mermaid app shows each step, including what to do when the old app will not open.

PlantUML

  1. Copy the diagram’s text, from @startuml to @enduml.
  2. In Cloud, type /plantuml, choose PlantUML Diagram and paste.
  3. Check the preview and save.

Not drawn: Graphviz (@startdot), ditaa, formulas, the AWS and Azure icon libraries, and includes from files or web addresses. The editor says so when a diagram uses one. PlantUML documentation.

Jira and Jira Service Management

Issue templates and recurring requests, set up again in Cloud

Issue Templates & Create Defaults

Each project gets a Templates page. Pick a template and Jira’s own Create dialog opens filled in. A template can also create child work items and sub-tasks in order, and set the assignee, a due date, components and custom fields. Jira Automation rules can create from a template too.

It does not read templates or settings from Data Center apps. Create the templates again, or save a well-filled work item as a template. Between two Cloud sites that both have the app, use Export and Import.

Recurring Requests & Templates

Customers raise a request again, or set it to repeat, from the Jira Service Management portal: daily, weekly, monthly patterns such as the first Monday, or quarterly. Project admins set the limits and the desk’s closed days. Scheduling is off until a project admin turns it on.

It does not read schedules from Data Center apps or from Automation rules. Set each repeat up again, from the request you want repeated.

At a glance

What comes across, and what does not

On Data CenterIn CloudHow it comes acrossWhat does notData
Mermaid diagramsMermaid Diagram macro, in Mermaid & PlantUML DiagramsCopy the text, paste it into the editorThe old macro and its settingsIn the page itself; no app storage, no permissions
PlantUML diagramsPlantUML Diagram macro, in the same appCopy the text, paste it into the editorThe old macro; Graphviz, ditaa, formulas, AWS and Azure icons, includesIn the page itself; no PlantUML server
Issue templatesIssue Templates & Create DefaultsCreate again, or save a work item as a templateOther apps’ templates and settingsForge storage in your site; nothing recorded about the people who use it
Recurring requestsRecurring Requests & TemplatesSet each repeat up again from its requestSchedules from other apps and Automation rulesForge storage in your site; holds account IDs and request answers (trust center)

None of the three uses Atlassian’s migration assistants to bring anything across. Each row is done by hand, as described above.

Checklist

Before you move

  1. Copy each diagram’s textWhile Data Center still runs, copy the Mermaid or PlantUML text of every diagram you want to keep, with the page it belongs to.
  2. Write down your templatesFor each issue template: the work type, the fields it fills and the child work items it creates.
  3. List your repeating requestsFor each one: the request, who raises it, and how often.
  4. Check which cloud you are moving toFor Isolated Cloud or Government Cloud, our regulated clouds page says where each app is listed.
  5. Try the apps on a Cloud test siteEach app has a free trial on the Atlassian Marketplace, so you can rehearse the move first.

Built for your own Data Center

Your own add-ons won’t move. We rebuild them.

Add-ons a company wrote for its own Jira or Confluence Data Center do not move to Cloud with the migration. Anything still needed has to be built again, or replaced by a built-in feature or Automation.

Send us a list of your add-ons and what each one does, and we go through them with you for an hour, free. You get a one-page note: what each would be on Forge, what cannot move, and a rough size.

How the free hour works

FAQ

Questions

Will my Data Center diagrams move to Cloud by themselves?

No. Our apps do not read or convert other vendors’ macros. Copy each Mermaid or PlantUML diagram’s text before you migrate, then add our macro in Cloud and paste it.

Do your apps run on Data Center?

No. All three are built on Atlassian Forge for Cloud. They are not available for Data Center or Server.

Are the apps available in Atlassian Isolated Cloud?

Yes. All three are listed in Atlassian Isolated Cloud since 12 November 2026, with the same features as in the normal cloud. Mermaid & PlantUML Diagrams and Issue Templates are also listed in Atlassian Government Cloud since 20 November 2026, the diagrams app with all three macros (Mermaid, PlantUML and OpenAPI). Recurring Requests is not listed in Government Cloud yet.

Does any data leave Atlassian?

No. All three apps run on Atlassian Forge and declare no outside addresses, so they cannot send anything outside Atlassian, to us or to anyone else.

Can PlantUML diagrams be drawn without a PlantUML server?

Yes. The PlantUML Diagram macro draws PlantUML in the reader’s browser, inside the page. The diagram’s text is sent nowhere and nothing is fetched from the web.

What about add-ons we built ourselves?

They do not move with the migration. We go through your list with you for an hour, free, and say what each would be on Forge.

Planning a move and want to know whether our apps fit your review? Write to [email protected]. You get a first reply within one to three business days, depending on severity (service level agreement).