Viva Goals migration: what's in your export, and how to move your OKRs to OKIAR
Facts checked October 27, 2026
Viva Goals shut down on December 31, 2025, so nothing more can be exported from it. If your team saved a file before then, look for the admin JSON or CSV export first, because it's likely the most complete. This guide shows what each export holds and how to rebuild from it.
Steps 1 and 2 apply whichever tool you choose. Steps 3 to 5 show how to bring your current quarter into OKIAR, which can read your export file.
Before you start: what's still possible after December 31, 2025
Access ended on December 31, 2025, or earlier if your licenses expired first, and Microsoft offered no extension. Microsoft's retirement FAQ doesn't say how long it kept data after that, or how it deleted it.
Start with your own systems. Explorer exports were emailed to the person who ran them, so search mailboxes for the export email. From June 2025, admins could also download JSON or CSV files from an Export tab.
For anything else, ask your Microsoft representative or GoalsDecom@microsoft.com, the two contacts Microsoft named for transition help.
Step 1: Work out which Viva Goals export you have
Viva Goals had five ways to get data out, and each one holds something different.
| Export | Who could run it | Format | What it holds | How it arrived | Best use now |
|---|---|---|---|---|---|
| Explorer → Export → Excel | Any user, from an Explorer view | CSV or XLSX | Only the fields the user picked; first-level key results and initiatives, if ticked | Emailed to the exporter | A checklist for rebuilding |
| Admin Export tab (from June 2025) | Org admins and team admins | JSON or CSV | Goal-related data; one importer reads owners, links, metrics, scores and check-ins from it | Downloaded from Organization or Team settings | Likely the most complete file; Atlassian requires the JSON |
| Microsoft Graph export job (beta) | A signed-in user with a delegated permission | Not documented | One Explorer view per job | Through the API; results expired | Treat it like an Explorer export |
| PowerPoint | Any user, from list or Explorer views | .pptx from a template, as of a chosen date | A snapshot | Downloaded straight away | A visual reference; WorkBoard says it can migrate from PowerPoint |
| Members tab export | Admins | CSV | People information | Downloaded | Rebuilding people and teams |
An Explorer export (CSV or XLSX)
Microsoft's Explorer help says the exporter picked which fields to include, and it never lists the fields available. Export settings were saved for every user, so one person's choices shaped later files. Tags may sit in separate columns.
Key results and initiatives are in the file only if the exporter ticked that option, and then only the first level below each objective. The same page told users to clear the "Show only top-level objectives" checkbox to get key results, so some files may hold objectives only.
An admin data export (JSON or CSV)
From mid-June 2025, org and team admins had an Export tab in Organization settings and Team settings. It produced goal-related data as JSON or CSV, was on by default, and came with no published field list. Microsoft announced it in Message center post MC1092430 (third-party mirror).
Keep an untouched copy before anyone opens or renames it. Atlassian, for one, asks for the JSON version unmodified.
Other files: Graph output, PowerPoint and the Members CSV
Developers could request a Microsoft Graph export job through a beta API, one Explorer view per job. Results expired, and Microsoft didn't document the file format. Check what the developer saved, then treat it like an Explorer export.
PowerPoint exports were editable slides built from a template, as of a date the user chose. They aren't data files, but they show how your goal tree looked.
Admins could also download a CSV of people information from the Members tab. Use it to rebuild your teams.
If you have no file
Without a file, rebuild from your last quarterly review deck and any slides people kept. Starting over? OKIAR's OKR examples cover 16 teams, with templates you can copy.
Step 2: Check what your file contains
Microsoft never published an export schema, and files differ because each exporter chose different fields. The best public list we found is Atlassian's mapping of the admin export, which shows what one importer reads. Compare your file's columns with it.
| Group | Fields Atlassian's importer reads from the admin export |
|---|---|
| Core | Title, Type, Owner, Team, Time period, Start date, End date, Tags, Progress, Status, Metric name, Metric unit, Start and Target, Parent, Child, Score, Check-ins |
| Additional | Creator, Delegated to, Goal type (Aspirational or Committed), Additional owners, Description, Progress configuration, Created at, check-in dates |
| Metric units seen | Number, Percentage, Dollar, Francs, Euros, Pounds, Swiss Franc |
Atlassian also lists what its importer leaves behind. It doesn't migrate alignment, contributions, status configuration, data source, target type, phased targets, risk thresholds, check-in owners or tasks. It skips initiatives and goals with permissions set, and keeps one parent per goal, storing any others in a custom field.
Viva Goals used seven statuses: Not Started, On Track, Behind, At Risk, Closed, Postponed and Reopened. Ask each vendor how it maps them and what its importer leaves out. Write the gaps down before you plan the move.
Moving to a tool other than OKIAR
Send the vendor a sample of your file and ask to see the result before you sign. Atlassian, for example, asks for the unmodified admin JSON export through a Support ticket. Our Viva Goals alternatives page compares eight tools, including what each offers for migration.
Step 3: Rebuild your current quarter in OKIAR
OKIAR's goal import lets you upload your export, up to 5 MB, at sign-up or later. It reads spreadsheets (multi-sheet Excel included), CSV, PDF, Word, text and Markdown, and helps map people, teams and parent links for you to review. JSON isn't on that list, so use the CSV version of an admin export. OKIAR drafts a plan from the file, and you edit it before you accept it. Bring in only the quarter you're in, and keep the original file as your archive.
White glove migration is listed on OKIAR's Enterprise plan, which is coming soon.
- Sign up free, with no credit card. OKIAR's beta plan has no cap on team members, so invite everyone who owns a goal.
- Upload your export with goal import, and review the draft plan before you accept it.
- Check your teams against the Members CSV or the Team column in your file. Check that every owner still works with you.
- Check that each team goal aligns to the right company objective, using the Parent and Child columns.
- Check each key result's start value, target and unit against your file. All three are optional in OKIAR.
- Move metrics you track all the time, such as revenue or uptime, into KPIs instead of key results.
- Connect the Slack integration, so owners get reminders, check in from Slack, and see summaries in their channels.
- Check the result against your PowerPoint export or last review deck, using the objective, team and person views. Fix owners and links that don't match.
Or rebuild with Claude or Codex
OKIAR's MCP connection can create objectives, key results and KPIs. If your file needs reshaping first, connect it to Claude or Codex, share your export, and ask the assistant to create your current quarter. It follows your role and team permissions. Check the result against your file before the first check-in.
Where each Viva Goals field goes in OKIAR
| In your Viva Goals file | In OKIAR | Check before you start |
|---|---|---|
| Title and Type | Company objective, team goal or key result | Which level each item sits at. Individual objectives become person-level objectives |
| Parent and Child | Team goals aligned to company objectives | Multi-parent goals; Explorer files hold first-level children only |
| Owner, Additional owners | A person, with their own view | Owners who have left the company |
| Team | A team, with its own view | Team names match today's org chart |
| Metric name, Metric unit, Start and Target | A measurable key result with an optional start value, target and unit | Units carried over correctly |
| Metrics you track all the time | KPIs | Revenue or uptime belong here, not in key results |
| Progress and Score | Set fresh in the first check-in | Keep old scores in your archive file |
| Status | Confidence, set fresh in the first check-in | See the status table below |
| Check-ins | Stay in your archive file; start fresh check-ins in OKIAR | Copy any blocker still open into the first check-in |
| Tags | Products (projects in OKIAR) or teams, where they match | Tags that were themes, not owners |
| Time period, Start date, End date | The period you're setting up; fiscal-quarter labels such as halves or fiscal years work too | Bring only the current quarter across |
| Description, Goal type, Creator, Created at, Delegated to | Keep in your archive unless you need them | Committed goals you must not drop |
What to do with Viva Goals statuses
We suggest you don't copy old statuses across. Ask each owner to set confidence fresh in their first OKIAR check-in instead.
| Viva Goals status | In your rebuild |
|---|---|
| Not Started | Create the goal; the owner sets confidence at the first check-in |
| On Track | Bring it across |
| Behind or At Risk | Bring it across, and name the blocker in the first check-in |
| Closed | Leave it in the archive |
| Postponed | Decide whether it belongs in this quarter |
| Reopened | Treat it as active |
Step 4: Replace each Viva Goals integration
Every Viva Goals integration stopped on December 31, 2025. Viva Goals had checked them for new data once per hour, and you could also sync by hand. OKIAR offers Slack and MCP connections today, so most old syncs become a weekly update from the owner.
Tell owners before the first check-in that they'll now enter progress themselves.
| Group | Viva Goals integrations | In OKIAR today |
|---|---|---|
| Chat | Slack, Microsoft Teams | Slack integration; no Teams app |
| Work tracking | Azure DevOps, Jira, GitHub, GitLab, Asana, Trello, monday.com, Microsoft Planner, Smartsheet, Favro, Planview Projectplace, Project for the web | The owner updates progress in the weekly check-in |
| BI and data | Power BI, Tableau, Looker, Domo, Mode, Snowflake, BigQuery, Amazon Redshift, Azure Data Explorer, Microsoft SQL Server, MySQL, PostgreSQL | Weekly check-in; long-running metrics become KPIs |
| Spreadsheets | Excel Online, Google Sheets | Weekly check-in |
| CRM and support | Salesforce, HubSpot, Dynamics 365, Zendesk | Weekly check-in |
| Files | Box | Nothing listed |
| AI assistants | None listed | MCP for Claude or Codex, following your role and team permissions |
Viva Goals' integration list named 31 sources, and its admin page added Teams and Project for the web.
Step 5: Run the first check-in
Hold the first check-in in your first week on OKIAR, while the rebuild is fresh.
- Set each team's cadence and check-in template.
- Ask each owner to check in by voice or text, covering progress, confidence and blockers.
- Read the weekly summary together at the next team meeting, since it surfaces what needs attention.
- Once you have several check-ins, open Insights to see pacing, confidence and recurring blockers.
- Use a mid-quarter review to adjust the plan as things change.
Our weekly check-in template gives you five prompts to reuse.
Run your next quarter in OKIAR
Free during beta, with no credit card.
Frequently asked questions
Can I still export Viva Goals to Excel?
No. Viva Goals shut down on December 31, 2025, and Microsoft didn't extend access.
If someone exported before then, the Explorer file is a CSV or XLSX sent to their email. If no one did, ask admins about Export tab downloads, and contact your Microsoft representative or GoalsDecom@microsoft.com.
Which Viva Goals export is the most complete?
Probably the admin data export from the Export tab, available from June 2025. Atlassian's importer reads owners, parent and child links, metrics, scores and check-ins from it. An Explorer export holds only the fields the user picked and first-level children.
Does the Excel export include key results and initiatives?
Only if the exporter ticked the option, and then only the first level under each objective. If the "Show only top-level objectives" box was ticked in Explorer, key results may be missing too. Check your file for key results before you plan the rebuild.
We came to Viva Goals from Ally.io. Is anything different?
No. Microsoft acquired Ally.io on October 7, 2021, and its technology was rebranded as Viva Goals. Your goals lived in Viva Goals after that, so the exports described above apply to you too.
Can OKIAR import my Viva Goals file?
Yes. OKIAR's goal import reads CSV and Excel files up to 5 MB, helps map people, teams and parent links for you to review, and drafts a plan you review before accepting. JSON isn't listed, so use the CSV version of an admin export. See Step 3.
What does OKIAR cost?
OKIAR is free during its beta, with no credit card and no caps on objectives, key results, KPIs or team members. A Pro plan is coming, priced "TBD/seat/month". Okiar is already live today.