Workpath→OKIAR

Migration guide · Workpath

Workpath migration: Explorer files, the Connect API and what private goals miss

Facts checked October 27, 2026

Before you start: list what your Workpath account holds

Workpath accounts can switch modules off and rename things. The Connect API overview notes that your screens might say Objectives or Outcomes where the API says Goals. Write down the names your company uses so the export makes sense to everyone.

Also note:

• Which modules are on. KPIs, Goals, Initiatives and Strategic Elements each export differently.
• Your cycles. Goals are planned in cycles, usually quarters, and you'll pick the cycle when filtering.
• Private goals. Ask owners to make any private goal they want moved visible, or list them by hand. The API never returns private goals, KPIs, initiatives or notes.
• Archived teams. Their goals are also left out of the API.
• A super admin. Only admins can create API clients.

Step 1: Get your data out of Workpath

Explorer export

Workpath's export article is short. Open Goals, click Explorer in the upper right, filter and sort until the list shows what you want, then hit Export and choose "CSV/Excel File or Word File." Exports run in the background and you receive a download link.

Filter by cycle, not by team, so a single file holds the whole company for the quarter you're moving. Then do a second export for the previous cycle if you want history for comparison.

Connect API v3

The overview spells out what an API client sees. A super admin creates the client in Settings; the developer docs put it under Integrations, API clients, while Workpath's Connect API help article points to an API Clients tab in Organization Settings. Either way, choose read access. The help article says older clients were all set to full access, so create a fresh read-only client for the migration and delete it afterwards. Lists return 20 items per page by default, and you can raise that to 100.

The Goals reference adds detail you'll want:

• Every goal has exactly one owning user plus the team, business unit or organization it belongs to.
• Progress and confidence are calculated by Workpath and read-only. Progress rolls up from key results, from supporting goals, or both.
• Key results carry start, current and target values, a confidence level, labels and owners.
• Goals and key results are linked to what they support through "supports" and "supported_by."

KPIs come back as dated actuals, targets and forecasts. If anyone still has v2 scripts, the overview says v2 is frozen and its goal and key result responses include a v3 ID for mapping.

Workpath MCP

The overview also mentions an MCP server set up under Settings, Integrations, Connections. It's handy for asking questions about your data, but use the API or Explorer for the actual move.

Without access

If your contract has ended or your login no longer works, email support@workpath.com and ask what can still be sent. Otherwise rebuild your top goals from leadership decks, or start with our OKR examples.

Step 2: Check the Workpath export

Workpath doesn't document the Explorer file's columns, so treat your first export as a test. Before you plan the move, compare it with the screen:

1. Count goals and key results per team for the cycle and match the Explorer totals.
2. Confirm each row names its team or business unit and its owner.
3. Look for links between levels. If the file doesn't show what each goal supports, pull that from the API's supports fields.
4. Find missing private goals and goals from archived teams, and decide whether they matter.

A sample API pull

A developer's script for a migration usually needs only a few calls, all read-only:

• Cycles, to find the ID of the quarter you're moving.
• Teams, business units and users, which come back in full for admins.
• Goals for that cycle, with their key results, owners and supports links.
• Goal updates, if you want the written history.
• KPIs, if that module is on.

Save the raw JSON before you transform anything. If a later step goes wrong, you can rerun it without calling Workpath again, which matters if the contract has ended by then.

Initiatives and KPIs are separate from goals. If they matter to you, export them through the API, or at least record the current KPI values by hand.

Still deciding where to go? The Workpath alternatives page compares prices, contracts and Slack support.

Step 3: Set up the same quarter in OKIAR

OKIAR's import understands both of Workpath's outputs. The sign-up docs say goal import reads CSV, Excel (including several sheets), Word, PDF, text, Markdown, up to 5 MB per file. It helps map people, teams and parent links for you to review and gives you a draft to fix before anything is final, either during sign-up or later.

How we'd sequence it:

1. Start a free OKIAR account at okiar.app/signup.
2. Upload the Explorer CSV or Excel file for the current cycle. For JSON from the API, trim to the current cycle and stay under 5 MB.
3. Rebuild the hierarchy from organization goals down through business units to teams, using the supports links.
4. Enter KPIs as OKIAR KPIs. From here on OKIAR records their history; past Workpath values stay in your export.
5. Set a period that matches your Workpath cycle. Custom periods are available.
6. Add people with the right role: Admin, Manager, Contributor or Viewer.
7. Weight key results where some count for more. OKIAR supports it.

Where each Workpath field goes in OKIAR

Status in OKIAR

OKIAR's status is driven by pacing, as the objective docs explain: actual progress over expected progress for the date. At 0.7 or above you're On track, from 0.4 to 0.69 you're Behind, and below 0.4 you're At risk. Not started, Closed and Abandoned are chosen directly.

Step 4: Replace Workpath integrations

Workpath leans on Microsoft: Teams, Power BI, Excel Online, Planner, Azure DevOps and Entra ID appear on its pricing page. Here's the honest mapping:

Step 5: Run the first cycle and wind Workpath down

Pick a weekly check-in day and announce it. Owners record their numbers, their confidence and any blocker, so the confidence that Workpath used to calculate now comes from the person closest to the work. At mid-cycle, compare a few top goals between the two tools. Before the Workpath contract ends, make sure every Explorer file, API dump and KPI history you want is saved in your own storage.