0:00 / ~0:00

Atlassian Cloud Migration

Cloud migration is not an export-import project.

Server has been unsupported since February 15, 2024. Affected Data Center products have a clear end-of-life path through March 28, 2029. I help you prepare data, apps, users, security and processes so the move does not become real only on cutover day.

Back to Atlassian
Migration readinessCloud cutover
Inventory84%
Apps31
Users412
Test run2/3
  • Projects & workflows checked
  • App compatibility assessed
  • Accounts & security prepared
  • Cutover plan with fallback option
Feb. 15, 2024 PT

Server support ended

Server installations are out of official support. Continuing to run them means increasing risk.

March 30, 2026

New Data Center purchases blocked

New Data Center subscriptions for affected products are no longer generally purchasable.

March 30, 2028

Expansions end

Existing customers can expand users and apps only until this date.

March 28, 2029 PST

Data Center EOL

Affected Data Center products reach the announced end of their lifecycle.

Migration in stages

From three weeks to several months, depending on legacy baggage.

Project size does not depend only on user count. The key factors are grown workflows, apps, permissions, integrations, data quality and how much change the teams can absorb.

  1. 1

    Assessment

    Capture products, projects, fields, workflows, users, groups, permissions and apps.

  2. 2

    Clean up

    Reduce old projects, duplicate fields, unnecessary apps and unclear permissions before the move.

  3. 3

    Cloud target model

    Define plans, licensing model, security, accounts, domains, SSO and app replacements cleanly.

  4. 4

    Test migration

    Check Migration Assistant, app data, permissions and critical workflows in test runs.

  5. 5

    Cutover

    Plan communication, freeze, final export, links, handover and first support windows.

  6. 6

    Stabilize

    After go-live, catch errors, training needs, automations, permissions and user questions.

Why experience matters

The fair-weather scenario is not what decides.

You want someone in the project who has already seen app data migrate differently than expected, accounts collide, old permissions suddenly become visible or a seemingly small workflow detail block go-live.

App not cloud-ready Duplicate user accounts Unclear project permissions Fields and workflows grown over time External users and portal access Links, mail handlers and integrations

Prepare data

Review projects, spaces, attachments, fields, workflows and historical baggage deliberately.

Assess apps

Clarify cloud compatibility, replacements, licensing costs and app data before the test run.

Map accounts

Map users, groups, domains, managed accounts, portal access and external accounts cleanly.

Plan security

Define permissions, SSO preparation, admin roles, approvals and post-migration checks.

Start migration

Tell me what is running today and when the cloud must be ready.

We clarify whether your migration is a compact three-week project or a multi-month move with several test runs.

Discuss migration