Atlassian Goals→OKIARNo shutdown date. Leave when you’re ready.

Migration guide · Atlassian Goals

Atlassian Goals migration: what the CSV holds, and how to rebuild your OKRs in OKIAR

Facts checked October 27, 2026

Before you start: what's in Goals and what isn't in the export

Three facts shape the whole move:

1. The CSV leaves out success measures. In Atlassian Goals, "success measure" is the general term for key results and KPIs, and those values aren't in the published CSV field list.
2. The CSV is flat. Atlassian's own tracker, ATLAS-312, says the export "will only include the data in a flat format, not in a hierarchical structure." Parent goal and Subgoals columns are still there, so you can rebuild the tree.
3. One export holds up to 1,000 goals. Atlassian's limits page says to filter by status, owner or tags and export in batches.

Step 1: Work out which Atlassian Goals export you have

The Goals directory CSV

Open the Goals directory, apply a saved view or any filters, then open the menu at the top of the list and select Export CSV. Atlassian lists these fields: Goal key, Name, Status, Creation date, Target date, Owner, Teams, Parent goal, Subgoals, Contributing projects and Tags. It also says: "Custom fields are currently not available to be exported."

If your organization set up key results as their own goal type, as some OKR setups do, each key result is a goal and appears in the file as its own row. Atlassian allows up to 20 goal types per workspace.

Who can export? If your admins use group permissions, the Views, Export permission controls it. Atlassian says group permissions are in early access and need a Strategy Collection license.

The GraphQL API

The Goals GraphQL API is how you get what the CSV leaves out. Atlassian's search query guide shows a goals_search query sent to your site's GraphQL gateway with an API token. The API overview sets a default limit of 10,000 points per user per minute, so big pulls need pacing. Its search can filter on parent goal, goal type, team and attached metric, so a developer can pull goals level by level with their metrics, then save the result as CSV. The ATLAS-312 ticket suggests the same route for keeping the hierarchy.

Atlassian Analytics data shares

Atlassian added Goals and Projects data to data shares, rolling out through May 2026. If your company already sends Atlassian data to a warehouse, your data team may hold goal history there.

If you have no file

Export the CSV first. It takes a minute, and it's still the cleanest start. If you'd rather not carry anything over, pick a template from the 16 teams in OKIAR's OKR examples.

Step 2: Check what your file contains

Before you plan the move, check four things:

1. Count the rows in each CSV, and run more filtered exports if any file stopped at 1,000 goals.
2. Check the Parent goal column. Every parent named should also have its own row in the file.
3. Look for owners who have left the company.
4. List the success measures and custom fields you need. They aren't in the CSV, so copy them from each goal page or pull them through the API.

Moving to a tool other than OKIAR

Because the CSV is flat and has no success measures, check how a vendor handles it with a test import before signing. As of October 27, 2026:

• Tability's AI importer needs no fixed template for an XLSX or CSV of up to 10 MB, though it won't create users or teams.
• Perdoo's goal import needs the rows moved into its CSV template or pasted as text, within 5 MB and 10,000 rows, and carries current state only.

Our Atlassian Goals alternatives page compares the tools teams move to.

Step 3: Rebuild your current quarter in OKIAR

Upload the Goals CSV to OKIAR. The sign-up guide lists spreadsheets, CSV, PDF, Word, text and Markdown, with a 5 MB limit. Owners, teams and the parent links from the Parent goal column carry over. Run the import at sign-up or later; you'll get a draft plan to edit, including objectives, key results, start values and targets, before you accept.

Rebuild only the quarter you're in. Keep the CSV and any API output as your archive.

1. Sign up for OKIAR's free beta. No card is needed, and team size isn't capped.
2. Filter the Goals directory to the goals due this quarter, export, and upload that CSV. Review every proposed objective before you accept the plan.
3. Compare imported teams with your Atlassian teams before inviting people as Admin, Manager, Contributor or Viewer.
4. Check that company goals and the goals under them nest the way they did in Atlassian.
5. Add the key results. Copy each success measure's start, current and target values from the goal page or your API pull.
6. Set up KPIs for numbers you track continuously, like revenue or churn.
7. Connect Slack.
8. Hold the objective, team and person views up against Atlassian Goals and fix any owner or link that differs.

Where each Atlassian Goals field goes in OKIAR

Statuses in OKIAR

Atlassian's goal statuses don't need to move. OKIAR assigns status from pacing, and its objective guide defines pacing as actual progress weighed against the progress expected at this point in the period. Owners can override it.

Pacing of 0.7 or more gives On track; 0.4 to 0.69 gives Behind; lower than 0.4 gives At risk. Not started, Closed and Abandoned are set by people, not by the ratio.

Every check-in can also record confidence from 0 to 10.

Step 4: Replace your Atlassian Goals connections

Goals sits inside Atlassian's platform, so a lot of its value comes from links: up to 100 Jira work items per goal, projects, Confluence embeds and Slack or Microsoft Teams updates. None of those links comes with the CSV.

Your Jira work stays in Jira, and owners now enter progress themselves, so tell them before the first check-in. An assistant like Claude can help through OKIAR's MCP: 14 tools that can update a current value or file a check-in, though none creates objectives or key results.

Step 5: Run the first check-in

Plan your first check-in for week one.

• Agree on a check-in day and template for each team.
• Owners write or record progress, confidence and blockers.
• Read the weekly summary at the following team meeting.
• Look at Insights after a few weeks for pacing, confidence and blockers that come up again.
• Adjust the plan in the mid-quarter review.

Our weekly check-in template suggests five prompts.