TL;DR
A new Atlassian implementation in 2026 means Atlassian Cloud: Data Center is no longer sold to new customers. Choose a plan and, often, a Collection that bundles the apps you need. Design a small set of standard templates, workflows and fields before anyone configures anything, because uncontrolled customisation is what makes Jira hard to live with. Set up identity, data residency and integrations early, roll out Rovo AI with clear governance, then go live team by team with role-based training and a light process for future changes.
Atlassian's tools are easy to start with, and that's both their strength and their risk. A team can be up and running in Jira in an afternoon. Ten teams doing that independently produce ten sets of workflows, hundreds of custom fields and reports nobody can compare. A good implementation keeps the speed and avoids the mess.
1. Start with the work, not the tools
Before choosing anything, agree what you're trying to improve and for whom. Typical goals:
- One place to plan and track work across software and business teams.
- A single source of truth for documentation and decisions.
- A service desk for IT, HR or customers.
- Portfolio visibility for leaders, connecting strategy to delivery.
For each, name the teams involved, how they work today and what "better" would look like in measurable terms. That shapes every decision that follows. Atlassian frames this as a System of Work: aligning goals, planning and tracking, and knowledge across teams.
2. Choose your plan and Collections
Atlassian stopped selling Data Center to new customers on 30 March 2026, and Data Center reaches end of life on 28 March 2029, so new implementations are on Cloud. The choices are the plan and the bundle:
- Plans: Free (up to 10 users), Standard, Premium (adds cross-team planning, sandboxes and a 99.9% uptime SLA) and Enterprise (adds multiple sites, a 99.95% uptime SLA, and single sign-on without a separate Atlassian Guard subscription).
- Collections bundle apps for a purpose: Teamwork (Jira, Confluence, Loom), Service (Jira Service Management, Customer Service Management, Assets), Software (Bitbucket, Pipelines, DX), Strategy (Focus, Talent, Jira Align) and Product (Jira Product Discovery and Feedback). The Teamwork and Service Collections include Rovo with larger AI credit allowances than the individual apps.
Atlassian raised Cloud list prices on 13 October 2026. Our Atlassian licensing guide covers buying in Australia, and we can model the options for you.
3. Design before you configure
This is the step that separates implementations people like from ones they tolerate:
- Standard space templates. A small number of agreed templates, for example one for software teams, one for business projects and one for request intake, rather than a bespoke setup per team.
- Shared workflows. As few as possible, with status names that mean the same thing everywhere, so reporting works across teams.
- A controlled set of custom fields. Reuse fields across spaces. Every new field slows Jira down a little and makes reporting harder.
- Confluence structure. Decide which spaces exist (team, project, company knowledge), who owns them and how pages are archived.
- Permissions. Open by default where you can, restricted where you must, using groups rather than individuals.
Validate the design with real teams before rollout. On a global launch-management implementation, we built three proof-of-concept designs in a sandbox and tested them against agreed success criteria before choosing one. More than 50 global teams now run on the result.
4. Set up identity, security and data residency
- Single sign-on and provisioning from your identity provider, such as Microsoft Entra ID, so joiners get access automatically and leavers lose it. Included on Enterprise, and available with Atlassian Guard on other plans.
- Data residency: on Standard, Premium and Enterprise, you can pin product data to Australia (Sydney). Set it up before content builds up.
- Admin roles: a small number of organisation admins, with day-to-day space administration delegated to trained team leads.
Our guide to moving work management to the cloud covers data residency and IRAP in more detail.
5. Plan integrations from the start
Atlassian rarely stands alone. Plan the connections to Slack or Microsoft Teams, your CRM, identity and HR systems, monitoring tools and development tools as part of the design, not as an afterthought. When choosing Marketplace apps, prefer apps built on Forge: Atlassian's older Connect framework reaches end of support on 31 January 2027. Our guide to integrating Atlassian with your tech stack covers the options.
6. Roll out Rovo AI with governance
Rovo is included in paid Cloud plans. It searches across Atlassian and connected tools, answers questions, summarises work and runs agents. A safe rollout:
- Fix oversharing first. Rovo respects permissions, so it will surface anything a user can technically access, including old Confluence pages that were never meant to be widely read. Review permissions on sensitive spaces before switching it on.
- Decide which connectors to enable, such as Google Drive, SharePoint or Teams, and who approves new ones.
- Understand the credits. Jira and Confluence include 25 credits per user per month on Standard, 70 on Premium and 150 on Enterprise, pooled across the organisation; the Teamwork and Service Collections include more. Search and summaries don't use credits. Extra usage is billed from 3 December 2026.
- Start with search and summaries, which everyone benefits from, then introduce agents for specific, well-understood tasks.
7. Pilot, train and roll out in waves
- Pilot with one or two teams that are keen and representative. Fix what they find.
- Migrate existing work and documents where it's worth it. Archive the rest rather than moving clutter.
- Train by role: team members on daily tasks, team leads on boards and reporting, space admins on configuration within the agreed standards.
- Roll out in waves, with champions in each team and office hours for the first few weeks.
Adoption is a change management task as much as a technical one. Our article on why change stalls and the CEO's role covers the people side.
8. Keep it healthy
- A light change process for new fields, workflows and apps, so requests are checked against the standards and existing options.
- Quarterly clean-up: archive inactive spaces, remove unused fields and apps, review licences.
- An owner for the platform, with a roadmap, a budget and the authority to say no.
- Measures that tie back to your original goals, reviewed with the business, not just IT.
Common mistakes
- Letting every team configure its own workflows and fields from day one.
- Copying old processes into Jira exactly, instead of simplifying them.
- Treating Confluence as a file share, with no structure or ownership.
- Switching on AI before reviewing who can see what.
- No owner after go-live, so the platform drifts.
How Great Minds helps
Great Minds is an Atlassian Silver Solution Partner. We design and implement Jira, Confluence, Jira Service Management and the Collections, set up identity and data residency, connect Atlassian to your other systems, and roll out Rovo with the right governance. See our Atlassian implementation service.
Frequently asked questions
Can we still implement Atlassian Data Center?
Not as a new customer. Atlassian stopped selling Data Center to new customers on 30 March 2026, and it reaches end of life on 28 March 2029. New implementations are on Atlassian Cloud.
Should we buy individual apps or a Collection?
If you need most of the apps in a Collection, it's usually better value, and the Teamwork and Service Collections include larger Rovo AI allowances. If you only need Jira, buying it alone can be cheaper. Model both.
How long does an Atlassian implementation take?
It depends on the number of teams, how much you migrate and how many integrations you need. Starting with a pilot of one or two teams gets value early, before rolling out more widely.
Is Rovo safe to switch on?
Rovo only shows users content they already have permission to see, and Atlassian says prompts and responses aren't used to train models. The main risk is existing oversharing, so review permissions on sensitive spaces first.
Where to start
Write down the three outcomes you want from Atlassian and the teams involved in each. If you already have Jira or Confluence, count your workflows and custom fields; the number usually tells you whether you need a fresh design or a clean-up. We're happy to help with either.