Atlas→OKIAR

Migration guide · Atlassian Atlas

Atlassian Atlas migration: saving projects and weekly updates after the rebrand

Facts checked October 27, 2026

Before you start: find your old Atlas data in Atlassian Home

Sign in at home.atlassian.com. Your former Atlas projects sit in the Projects directory and your goals in the Goals directory. Atlassian's support pages still say "Atlas workspace" in places, which is a leftover of the rename, not a separate product.

Three things changed in the move that affect your exit:

• You need Jira or Confluence. The announcement says the apps require a version of one of them, free plans included.
• Followers need Atlassian accounts. Followers don't use a seat, but they must be Atlassian users. One customer replying to the announcement said he could no longer add outside people as email-only followers.
• Admins now control access. Atlassian's availability page says Goals and Projects were due to reach every customer in Q2 2026, and users see them only after an admin grants access.

Make sure the person doing the export has access to every project and goal, including private ones.

Step 1: Pull Atlas projects, goals and updates

Projects directory CSV

Atlassian's directory export page works the same for both lists. Apply a saved view or filters, open the menu at the top, and choose Export CSV. The project file holds Project key, Name, Status, Start date, Target date, Owner, Team, Contributors, Related goals, Related links and Tags.

Related goals is the column that matters. It's the only link in the file between the work you did and the outcomes it was for.

Goals directory CSV

The goal file holds Goal key, Name, Status, Creation date, Target date, Owner, Teams, Parent goal, Subgoals, Contributing projects and Tags. Each CSV is capped at 1,000 goals, and custom fields aren't exported. For batching, the hierarchy and the API, follow the Atlassian Goals migration guide instead of repeating it here.

Weekly updates

This is the gap that hurts Atlas teams most. Asked in the community thread on exporting updates, an Atlassian staff member replied that there is export for goals and projects "but not for updates specifically." The workarounds offered were following the goals, so the Monday digest lands in your inbox, or pasting updates into a Confluence page.

For an exit, that means:

• Decide which projects' update history anyone will ask about later. Usually it's a handful.
• Copy those updates into a Confluence page or a document now, newest first, with the date and author.
• Follow the active goals and projects for your last few weeks, so the digests become a record by email.

Activity history

Atlassian's activity page says goal activity only covers changes made after April 2026. It tracks owner, target date, name, status or score, and followers, but not description or tag changes. Don't count on it for anything from the Atlas years.

Starting from nothing

If the directories are empty or locked, rebuild from the last digest emails or from our OKR examples, which cover 16 teams.

Step 2: Check the two Atlas files

Atlas mixed two kinds of thing: projects (work) and goals (outcomes). OKR tools mostly care about the second. Read both files side by side before you plan the move, and confirm these points:

1. Every active goal appears in the goal file, and any file with exactly 1,000 rows gets split and run again.
2. Each live project points to at least one related goal. Projects with none may not belong in an OKR tool.
3. Owners and team names still match people and teams you have.
4. The updates you copied by hand line up with the right project keys.

A quick way to sort projects: put the project CSV in a sheet, filter on Related goals, and mark each row "keep linked," "archive" or "finished." Only the first group needs a home in an OKR tool.

Atlas goals often had no numbers at all, just a name, a target date and a status. Those need rewriting into measurable key results, which is the real work of this migration.

Picking a destination? The Atlassian Atlas alternatives page compares tools by price, Jira links and import.

Step 3: Turn Atlas goals and projects into OKRs in OKIAR

OKIAR's goal import (see the sign-up docs) can read both CSVs, plus JSON, Excel workbooks with several sheets, PDF, Word, text and Markdown, up to 5 MB per file. It helps map people, teams and parent links for you to review and hands you a draft to edit before saving. Use it at sign-up or later.

An order that suits Atlas data:

1. Make a free OKIAR account at okiar.app/signup.
2. Put the goal CSV and project CSV into one workbook as two sheets and upload it.
3. Keep top goals as objectives and use the Parent goal column for nesting.
4. Write two to four key results per objective. Where an Atlas goal had subgoals that were really measures, turn them into key results.
5. Attach projects to objectives using OKIAR's optional project field, or leave them in Jira.
6. Weight key results unequally if one matters more. OKIAR supports weighting.
7. Invite teams with roles: Admin, Manager, Contributor or Viewer. Followers who only read become Viewers.

Where each Atlassian Atlas field goes in OKIAR

How OKIAR sets status

Atlas let owners choose a status each week. OKIAR's objective docs describe a pacing ratio instead, actual progress divided by the progress expected by today. The result is On track at 0.7 or higher, Behind from 0.4 to 0.69, and At risk under 0.4. Not started, Closed and Abandoned stay manual, and owners add a confidence score from 0 to 10.

Step 4: Replace Atlas digests and chat posts

Atlassian Home has a Slack app that posts each update to linked channels and sends reminders and digests to owners and followers. A Microsoft Teams connection exists too.

Step 5: Swap the weekly update for a weekly check-in

Atlas teams already write something every week, so keep the habit and change the form. An OKIAR check-in asks for the numbers, confidence and blockers instead of a free-text paragraph. Our weekly check-in template shows a format. Run the first one before you remove anyone's access in Atlassian Home, and keep your copied updates and both CSVs in a shared folder for later questions.