Rhythms migration: export the CSV, keep the hierarchy, move your OKRs
Facts checked October 27, 2026
Rhythms is an AI operating system for leadership teams, with OKRs, check-ins, documents and playbooks in one workspace. Getting goals out is easier than its marketing site suggests. The Rhythms help center documents a CSV export with the whole hierarchy, a REST API for check-in history, and Word or PowerPoint exports for the record. This guide walks through each, then shows where every column lands.
Still choosing a destination? Our Rhythms alternatives page compares seven tools. Steps 1 and 2 suit any destination. Steps 3 to 5 cover OKIAR.
Before you start: three things about Rhythms data
- Visibility shapes the file. The export includes only what you can see. Where a parent is hidden from you, the Aligned to column shows ‹Not visible to you›. Ask a Rhythms Admin to run it if you need the full tree.
- One goal can have several parents. Rhythms puts each parent on its own line inside the Aligned to and Aligned to ID cells. Keep that in mind when you open the file in Excel.
- Status labels may be renamed. Admins can relabel the nine statuses, Draft, Pending Approval, Not Started, In Progress, On Track, Behind, At Risk, Closed and Postponed, per the status label article. Your file may say "Green" where another company's says On Track.
Step 1: Choose your Rhythms export
| Export | Where | Format | Holds | Use it for |
|---|---|---|---|---|
| Export to Excel, all child items | View menu (⋯) | CSV | Every objective, key result and initiative under the view, with 26 columns | The import file |
| Export to Excel, top-level items | View menu (⋯) | CSV | Only the items at the top of the view | A quick look at company goals |
| Word or PowerPoint | Templates or chat | DOCX or PPTX | A formatted report | Your archive |
| REST API v2 | api.rhythms.ai, with a token from support | JSON | Objectives, key results, initiatives, check-ins, labels, teams, users | Full check-in history |
| Rhythms MCP | Claude or Codex | Answers in chat | What your permissions allow | Spot checks |
The CSV, step by step
The export article puts it on any OKR view:
- Open a view that covers the goals you want, for example this quarter's company tree.
- Open the ⋯ menu and pick Export to Excel.
- Choose Export all child items to get the whole hierarchy below the view.
- Download the file from the Exports panel in the sidebar.
Columns include ID, Short ID, Title, Type, Owners, Team, OKR Status, Progress, Last Check-In Note, Aligned to ID, Time Period, Start Date, End Date, Contribution Percent, Metric Type, Target, Unit and Current. Dates use YYYY-MM-DD. Reports can't be exported directly, so export the view behind a report instead. Playbooks can schedule exports, which is useful if you want a weekly snapshot during the move.
Check-in history through the API
The CSV holds only the latest check-in and its note. For every past update, use the REST API. Rhythms' API access article says tokens are issued by support, not from a settings page. Ask for an Admin token so it can read the whole workspace. A developer can then page through /rest/v2/checkins and /rest/v2/key_results and save the results. Rhythms publishes no fixed rate limit, but asks callers to back off on a 429.
Word and PowerPoint
The same export article covers Word and PowerPoint output through templates and chat. Keep one deck per quarter as the human-readable record. It won't import cleanly anywhere.
Step 2: Read the CSV before you trust it
Before you plan the move, open the file and check:
- The Type column holds three values: objective, key_result and initiative. Decide now whether initiatives move.
- Every Aligned to ID matches an ID in the file. Rows marked ‹Not visible to you› mean the export was run with too little access.
- Contribution Percent adds up to 100 under each parent. It's the child's weight in its parent's rollup.
- Metric Type: Reach To is a graded number, while Stay Above, Stay Below and Stay Between are pass-or-fail guardrails, per Rhythms' metric types article.
Other destinations
Whatever you choose, test with a sample first. On October 27, 2026, Tability's AI importer took XLSX or CSV up to 10 MB with no set layout, and Perdoo's goal import wanted its own CSV template under 5 MB. The Tability migration guide and Perdoo migration guide cover those tools in more depth.
Step 3: Bring the Rhythms CSV into OKIAR
Upload the CSV as it is. OKIAR's sign-up guide lists spreadsheet, CSV, PDF, Word, text and Markdown files up to 5 MB, and Convert an API export to CSV before upload. It helps map people, teams and parent links for you to review, then shows a draft plan. You approve it once the objectives and key results look right.
- Sign up at no cost, without a card. The beta has no member limit.
- Upload one Time Period's export. A file covering several years can pass 5 MB; filter the view to one period and export again.
- Read every proposed objective and key result before accepting.
- Match the teams to your Rhythms teams, then invite colleagues as Admin, Manager, Contributor or Viewer.
- Check that objectives with two parents ended up under the one you want.
- Set weights on key results from Contribution Percent. OKIAR supports key result weighting.
- Move Stay Above and Stay Below guardrails into KPIs if they're ongoing health metrics.
- Connect Slack and review the plan with each owner.
Where each Rhythms field goes in OKIAR
| Rhythms column | OKIAR | Check |
|---|---|---|
| Title | Objective or key result title | Short ID prefixes you may not want |
| Type: objective, key_result | Objective, key result | Key results with no objective in the file |
| Type: initiative | Key result, or leave in Rhythms docs | Whether you still track them |
| Owners | Objective owners; more than one is optional | Former employees |
| Team | Team | Teams that merged |
| Aligned to ID | Parent link | Goals with several parents |
| Contribution Percent | Key result weight | Totals of 100 per parent |
| Time Period, Start and End Date | Period: quarter, year or custom | Half-year periods |
| Metric Type: Reach To | Key result with start, target and a direction | Decreasing targets |
| Metric Type: Stay Above, Below, Between | KPI, or a key result with a direction | Guardrails that need two bounds |
| Target, Unit, Current | Target, unit (count, percentage, currency, duration) and current value | Swiss franc and pound values |
| OKR Status | Status from pacing | Renamed labels |
| Last Check-In Note | Keep in your archive; new notes go in check-ins | History lives in the API |
| Labels | Description text | Labels used as filters |
All 14 fields shown.
How OKIAR sets status
Status in OKIAR follows pacing, as its objective docs explain: progress so far against progress expected by today. Anyone with rights can override it.
| OKIAR status | When |
|---|---|
| On track | Pacing ratio 0.7 and up |
| Behind | From 0.4 up to 0.69 |
| At risk | Below 0.4 |
| Not started, Closed, Abandoned | Chosen by hand |
Rhythms' Draft, Pending Approval and Postponed have no direct match. Drafts can stay out of the import.
Step 4: Connectors you'll leave behind
Rhythms key results can update themselves through connectors, including Atlassian Jira, Salesforce, Power BI and Tableau. OKIAR has no Jira integration and no connectors of that kind. Owners update numbers in check-ins, or an assistant does it through OKIAR's MCP server, which can create objectives, key results and KPIs, set a key result's current value or file a check-in. It respects each person's role and team.
| Rhythms | OKIAR |
|---|---|
| Slack app | Slack: channel posts and direct messages |
| Microsoft Teams | No Teams app; Telegram is the other chat option |
| Auto-updates from connectors | Check-ins, by voice or text |
| Rhythms MCP for Claude or Codex | OKIAR MCP, 14 tools |
Step 5: Your first OKIAR check-in
Rhythms teams usually have a check-in rhythm already. Keep the day.
- Set the day and template for each team.
- Owners record progress, a 0 to 10 confidence score and blockers, by voice or text.
- Leads read the weekly summary before the meeting.
- After three or four weeks, Insights shows which goals keep slipping.
Our weekly check-in template has five questions to reuse.
Run your next quarter in OKIAR
Free during beta, with no credit card.
Frequently asked questions
Can I export OKRs from Rhythms?
Yes. From any view, the ⋯ menu has Export to Excel, which makes a CSV. Pick Export all child items for the full hierarchy.
Does the export include check-in history?
Only the last check-in, its note and labels. Past check-ins come through the REST API, with a token from Rhythms support.
What happens to Contribution Percent?
It becomes the key result's weight in OKIAR, which supports weighting. Check that weights under each objective still add up after import.
Will Jira auto-updates keep working?
No. OKIAR has no Jira integration, so owners enter progress in check-ins.
Does OKIAR do the migration for us?
No. Migration help is available. You upload the file and review the draft yourself.
What does OKIAR cost?
It's free in beta, without a card and without limits on objectives, key results, KPIs or members. The beta has no fixed end date. Okiar is already live today., and a Pro plan is priced "TBD/seat/month".
Coming from Microsoft? Read the
Viva Goals migration guide.
Rebuild this quarter's OKRs in OKIAR, free during beta
No credit card, no caps on objectives, key results, KPIs or team members. Goal import reads your Rhythms CSV.