Atlassian is retiring Align, its enterprise agile-rhythm tool, and the retirement date is now concrete. If your org runs portfolio or strategic roadmap planning in Align, you have until 2027-03-15 to move off. After that, the vendor's stated path is Jira Cloud.[source1]

What's changing

The official end-of-life date for Atlassian Align is 2027-03-15.[source1] From that date the product is no longer supported, and the expectation is that all planning work migrates to Jira Cloud. For teams already deep inside the Jira ecosystem, this is less a technical shock than a planning-model shift: Align's whole selling point was a separate, strategy-level view above team-level Jira boards.[source1]

Atlassian's rationale, as stated in the announcement, is that roadmap and work-management capabilities now live "in Jira" natively — the company is consolidating its planning surface rather than maintaining two overlapping products.[source1] That's a defensible product decision, but it lands as a migration project on your calendar, not a feature toggle.

Where Align's gap leaves you

The practical question is: what did Align do that Jira doesn't do today? The classic Align value was bridging portfolio strategy (OKR-style objectives, quarterly commitments) down to the team-level backlog — including cross-program dependency tracking and rolling planning across many teams.[source1] Jira's native roadmap views cover release and team-level planning well, but if your org runs large-scale program planning — think multi-team dependency matrices or a strategy tree above the backlog — you may find yourself assembling that layer from Jira fields, automation, or third-party apps rather than a dedicated product.[source1]

That's the tradeoff to size honestly before you start migrating. If your Align usage is mostly as a fancy roadmap, Jira's native views will likely absorb it with little friction. If you use Align's cross-team portfolio views heavily, budget time for a real data-model redesign, not a copy-paste migration.

Migration route

The announcement points to Jira Cloud as the destination, not Jira Server or Data Center.[source1] That's consistent with Atlassian's broader push to cloud-first, but it forces the conversation about where your instance lives. If you're already on Jira Cloud, the path is straightforward — export from Align, re-map to Jira projects and issues, and re-cut the dashboards.[source1] The same route is documented in Atlassian's own guidance on moving from Align to Jira.[source1]

One thing to verify before you start: mapping Align's hierarchy to Jira. Align's entities (initiatives, epics, stories) don't map one-to-one to Jira's issue types by default, and the announcement does not document a built-in migration wizard or script.[source1] The absence of an automated tool is notable — a vendor sunsetting a product usually ships a migration path, and the source article does not mention one, so you should plan for a manual re-creation of structure.[source1] If you need to preserve history and relationships, confirm how far back your export goes before you commit.

When to move

You have until 2027-03-15.[source1] That's roughly a year and a half from today, which is plenty if you start now — and not much time if you wait. The risk of waiting isn't just the deadline; it's that Atlassian will likely stop investing in Align well before the end-of-life date, so bugs and edge cases in your current setup may go unfixed.[source1] Plan for a phased migration: map the hierarchy, migrate a pilot project, validate the dependency view, then roll out.

The succession question

If you're already betting on Jira Cloud as the single planning surface, this sunset is a confirmation. If you were waiting to see whether Align would survive, the answer is now on the calendar. The post-mortem verdict to track: whether Jira's native hierarchy truly covers the portfolio-planning slice Align owned.[source1] That's the gap that will decide whether this migration is a clean cutover or a five-year project.

Sources: