Tability→OKIAR

Migration guide · Tability

Tability migration: how to export your plans and rebuild your OKRs somewhere else

Facts checked October 27, 2026

Before you start: list your plans and who owns the workspace

Tability organizes work as plans, which hold objectives, outcomes (its name for key results) and initiatives. Plans can have sub-plans, so a company plan may sit above several team plans.

Do three things this week:

1. List every plan and sub-plan you want to keep, with its owner. Each one needs its own export.
2. Find your workspace owner. Tability's guide to deleting a workspace says only the owner can do it, so they should be part of the move.
3. Decide whether you need check-in history. If you do, plan for the API route below, which needs a Premium workspace.

We couldn't find a public statement of how long Tability keeps data after a workspace is deleted, so export everything first.

Step 1: Work out which Tability export you have

Tability's pricing page lists CSV and PDF export, PowerPoint and Google Slides export, and a public API among its features. Each route holds something different.

Export plan (CSV or slides)

Open the plan, click the three dots and choose Export plan. You'll get "the option to export your data to a CSV or to generate slides with the most recent update for each key result," in the setup guide's words. Take the CSV for the rebuild, and the slides if you want a picture of where things stood. Repeat for every plan on your list.

Filter views

Tability's filters guide says each filter view has options to save a segment, share the view or export results. A filter view can pull outcomes from many plans at once, which helps you check that no plan was missed.

AI Mode review spreadsheet

If your workspace uses AI Mode, Tability's guide to a team review spreadsheet shows how to ask for a downloadable CSV with the columns you name. Its example asks for one row per key result with plan, owner, current value, target, unit, latest check-in date and confidence. Check the rows against the plan, since an AI built the file.

The API

The API setup guide says you need a Premium workspace. API access is off by default and is turned on per user under Workspace settings, then Users. Each user then copies their personal API token from their account page, and the authentication guide says the token has the same access as that user. The API reference includes plans, objectives, outcomes, initiatives and the check-ins for each outcome.

If you have no file

Then the record is whatever people kept: slides from the last quarterly review, or screenshots of a plan. Teams that want a clean slate can borrow from OKIAR's OKR examples, written for 16 kinds of team.

Step 2: Check what your file contains

Tability doesn't publish a column list for the plan CSV. What its guides do say:

• The export covers one plan. Sub-plans need their own exports.
• The slides show only the most recent update for each key result.
• Outcomes come in several types, such as From X to Y, Stay above X, Stay below X, Milestone and Non-measurable.

Before you plan the move, check four things:

1. Count the objectives and outcomes in each CSV, and compare the totals with the plan in Tability.
2. Check that you can tell which plan each file came from, and which plan sits above it. Name each file after its plan.
3. Look for owners who have left the company.
4. Look for check-in history. The guides don't say the plan CSV includes past check-ins, so assume it doesn't until you see them.

Moving to a tool other than OKIAR

Test before you commit: give each vendor one of your Tability CSVs and look at what their import produces. On October 27, 2026 the options were:

• Perdoo's goal import names Tability CSV as a supported source, with limits of 5 MB and 10,000 rows. Updates, comments and check-ins stay behind.
• Teamflect's bulk upload needs an admin to copy your goals into Teamflect's Excel template, and it can only add new goals.
• Atlassian Goals: there's an open request for bulk upload, but no importer yet.

Eight tools, with their import options, are compared on our Tability alternatives page.

Step 3: Rebuild your current quarter in OKIAR

OKIAR's goal import takes the CSVs directly. Per the sign-up guide, any file up to 5 MB works, from a spreadsheet to a PDF, and a multi-sheet Excel file is read sheet by sheet. Owners, teams and parent links are kept. You can import while signing up or come back to it, and nothing is final until you've edited the draft and accepted it.

Leave closed plans in Tability's CSVs; rebuild just the plans running now.

1. Open a free account. The beta asks for no card and puts no cap on team members.
2. Put each current plan's CSV on its own sheet of one Excel file, kept under 5 MB. A CSV without a team column needs one added, filled with that plan's team. Read through the proposed objectives and key results before you accept.
3. Hold the new teams up against your org chart. Then invite everyone as an Admin, Manager, Contributor or Viewer.
4. See that the company plan's objectives sit above the team ones, as your plans and sub-plans did.
5. Go through the numbers on each key result: start, current, target and unit.
6. Anything you track every quarter, like revenue or churn, becomes a KPI.
7. Turn on Slack.
8. With the CSVs open, walk the objective, team and person views and repair any owner or link that's wrong.

Where each Tability field goes in OKIAR

Statuses in OKIAR

Tability's statuses don't need to come along. OKIAR sets its own from pacing, which its objective guide explains as real progress next to the progress you'd expect by this date in the quarter. Owners can still set a status by hand.

A key result pacing at 0.7 or better shows as On track. Between 0.4 and 0.69 it reads Behind, and below 0.4 it turns At risk. Not started, Closed and Abandoned skip the math; someone sets them.

Each check-in can also carry a confidence score, from 0 to 10.

Step 4: Replace your Tability integrations

Tability's pricing page lists integrations with Slack, Microsoft Teams, Jira, Linear, Asana and ClickUp, plus a data connector, webhooks and a check-ins API. Its MCP server lets AI assistants read OKRs and create check-ins. None of those connections come with your file.

OKIAR has no data connector yet. Its MCP server exposes 14 tools, so Claude or another assistant can log a check-in or move a key result's current value, though it can't add objectives or key results. Before the first check-in, make sure owners know the numbers are now theirs to update.

Step 5: Run the first check-in

Plan the first OKIAR check-in for week one.

• Choose which day each team checks in, and which template it uses.
• Each owner covers progress, confidence and blockers, by voice or in writing.
• Bring the weekly summary to the next team meeting.
• After a few weeks, Insights shows pacing, confidence and repeat blockers.
• Make plan changes at the mid-quarter review.

For the questions themselves, use the five prompts in our weekly check-in template.