Skip to content
Talk to an architect
Data Center to Cloud

The move to cloud is when your model gets decided.

Atlas Bench is an Atlassian Platinum Solution Partner with the Atlassian Cloud Migration specialization, and we move Jira, Jira Service Management, Confluence, Bitbucket, and Bamboo from Data Center to Atlassian Cloud. We assess the estate and its Marketplace apps, set up identity on the cloud side before data moves, rehearse with Atlassian's Jira and Confluence Cloud Migration Assistants, and run the cutover and hypercare. Atlassian Data Center products reach end of life on March 28, 2029, when subscriptions expire and the products become read-only.

We move Jira, Jira Service Management, Confluence, Bitbucket, and Bamboo from Data Center to Atlassian Cloud, and we consolidate cloud sites and bring other tools into Atlassian. Identity, apps, and governance are decided before any data moves, so you land on a platform someone owns instead of the same estate at a new address.

before after one platform separate instances, separate permission models L1 L2 L3 L4

The problem

Atlassian has set the date. Jira, Jira Service Management, Confluence, Bamboo, and Crowd Data Center reach end of life on March 28, 2029, so the move is coming whether or not anyone plans it. It is also the one moment when someone is funded to look at everything: every user, every group, every integration, every automation that has run unattended since the person who built it left.

Most migrations waste that moment. The plan is to move what exists and fix it later, and later never gets funded. Permissions arrive in cloud exactly as broken as they were on Data Center, now in a platform where they are harder to unpick. The move is when the model gets decided, so we decide identity, apps, and ownership first and move data second.

What the work is

Estate inventory and sequencing

Every instance, app, integration, automation, and custom field in scope, with the ones nobody owns identified. Then which instances merge, which move as they are, and in what order, with cutover windows set against your business calendar and Atlassian's Data Center dates.

Identity before data

Access is decided before anything is copied. Atlassian Cloud identifies people by email address, and LDAP or Crowd cannot connect to it directly, so you need a cloud identity provider and, in most cases, Atlassian Guard Standard. We set up SSO, groups, and provisioning on the target so users land where they belong.

App and integration rationalization

Marketplace apps go through the app assessment in Atlassian's migration assistants, which shows whether each app has a cloud version and an automated migration path. Each app is then marked needed, not needed, or replaced by an alternative, based on actual usage, so cost does not migrate along with the data.

Jira, Jira Service Management, and Confluence data

The move runs on the Jira Cloud Migration Assistant and the Confluence Cloud Migration Assistant, with their pre-migration checks cleared first. Every run is rehearsed on a test site, reconciled on both sides, and tracked in a defect log rather than spot-checked.

Bitbucket and Bamboo

Bamboo Data Center reaches end of life and Bitbucket Data Center does not, so build plans need a new home either way. We move build plans and deployment projects to Bitbucket Pipelines with Atlassian's Bitbucket Pipelines Importer, and repositories with the Bitbucket Cloud Migration Assistant, because Pipelines needs the code in Bitbucket Cloud.

Governance on the far side

Permission, workflow, and field schemes configured on the target so a small administration team can maintain the estate, with named owners for who creates spaces, fields, and schemes.

Cutover and hypercare

A cutover plan, communications, go-live in sequence, and a hypercare window before the platform transitions to your team.

How it runs

  1. Assessment

    3 to 4 weeks

    Discovery across every instance in scope: inventory, app assessment, identity design, a risk register, and a recommended sequence. This is the deliverable that makes the rest estimable.

  2. Design and build

    6 to 10 weeks

    Target configuration built on a test site: identity, permission schemes, workflows, apps, and the migration runbooks. Nothing touches production.

  3. Test and remediate

    3 to 4 weeks

    Test migrations with the migration assistants, structured user acceptance testing, and defect triage with configuration fixes across everything in scope.

  4. Cutover and hypercare

    3 to 4 weeks

    Go-live in the agreed sequence, post-cutover validation, then hypercare with the team who built it before handover.

What you get

  • An inventory of instances, apps, integrations, automations, and custom configuration in scope, with an owner for each
  • A migration approach with sequencing, cutover windows set against Atlassian's Data Center dates, and a named risk register
  • Target identity configuration, with SSO and group provisioning live before data moves
  • An app decision log from the migration assistants' app assessment: needed in cloud, not needed, or replaced by an alternative
  • A test-site build of the target estate, used for test migrations before any production change
  • Reconciliation on both sides of the move, with a tracked defect log
  • Permission, workflow, and field schemes configured so the estate is maintainable after handover
  • A cutover plan, communications, and a hypercare period before transition to your team
  • As-built documentation and administrator training
Start here

Four layers. One accountable system of work.

The layer everyone wants sits on the layer everyone ignores. Every engagement starts at one of these four, and whichever door you come through, the other three are still load bearing.

L4

Agents and Automation

Rovo, Agents in Jira, Forge, MCP with Claude and Copilot, agent lifecycle, usage and cost governance.

2 services

Atlassian Anthropic
L3

Governance and Change

Permission architecture, audit and compliance, ITSM and change control, change management, strategic reporting and budgets.

6 services

Atlassian Guard Jira Service Management Strategy Collection Jira Align
L2

Platform and Migration

Migration of every kind, tool consolidation, licensing, standardization, the system of work.

5 services

Atlassian Miro AWS Azure
L1

Identity and Access

Human and non-human identity, SSO, SCIM, least privilege, access reviews, Guard cleanup, Agent SSO readiness.

4 services

Atlassian Guard Okta

load-bearing, bottom to top

Proof

Cloud Migration

Atlassian Cloud Migration specialization, held alongside the Service Management specialization.

Atlassian Partner Directory, 2026.

Questions we get

When does Atlassian Data Center reach end of life?
March 28, 2029 at 23:59 PST. On that date Data Center subscriptions and their Marketplace apps expire, and the products become read-only. Sales to new customers ended on March 30, 2026, and existing customers can buy new subscriptions, apps, and expansions until March 30, 2028. Technical support and fixes for critical security vulnerabilities continue until end of life; extended maintenance after it is offered only by exception, at additional cost. The end of life covers Jira, Jira Service Management, Confluence, Bamboo, and Crowd. Bitbucket Data Center and Align (formerly Jira Align) Data Center are not included.
Why use a Platinum partner instead of migrating ourselves?
You can migrate yourselves. Atlassian's migration assistants move the data, but they don't decide which instances merge, which apps to replace, how identity works in cloud, or who owns the permission model afterwards. Atlassian recommends a Solution Partner if you suspect your migration is complex in any way, and it vets its Cloud Migration specialized partners on competency, capability, and customer satisfaction. We are an Atlassian Platinum Solution Partner with that specialization, and we make those decisions with you before any data moves.
Can you migrate without consolidating?
Yes, and sometimes that is the right call. But a like-for-like move carries the permission model with it. If the estate is already hard to administer, moving it makes that permanent rather than better.
What happens to our Marketplace apps?
The migration assistants list every installed app, whether a cloud version exists, and whether its vendor has built an automated migration path. We check each one against actual usage and mark it needed, not needed, or replaced by an alternative. App data is moved by each vendor's own migration path, so you agree to their terms first. Migrating an app nobody opens is a cost you carry for years.
How long does it take?
It depends on the number of instances and the state of the configuration, not on the volume of data. The assessment exists to produce a defensible answer to exactly this question. Start early: Atlassian gives Data Center customers a free cloud trial for the rest of their subscription, which is where test migrations can run.
Do you migrate history?
Usually, but decide it deliberately. Sometimes it is faster, and the result is better, to start clean in templated spaces and keep the old data for reference. Plan where that reference copy lives: Atlassian advises against leaving a read-only Data Center instance connected to the internet after end of life, because security fixes stop.
Who runs it afterwards?
Your team, with documentation and administrator training as deliverables. If you would rather not, the run layer is a service in its own right.

Training

Learn it in a class.

Live classes on the official curriculum, taught by the architects who run these platforms, each with a hands-on sandbox of your own.

Every course and learning path

featured guide

Most teams ask for a phased migration because it feels safer, but when spaces share links, roll-ups, scripts, and global apps, phasing splits one connected system into two broken ones. For instances like that, a single well-rehearsed cutover carries less risk, less coordination, and fewer surprises than moving in batches.

Read the guide

Recent resources

Find out what you are actually running.

Fixed scope. The assessment reads the estate as it is: instances, schemes, licensing, and the decisions a migration would force you to make anyway. You get the findings, the ownership gaps, and the order to close them in.

Talk to an architect

By sending this you agree to our privacy policy.

Not ready? Talk to an architect