Migration guide

You export the data. We do the rest.

Moving from Lattice, Quantive, or a spreadsheet mess? The whole migration is designed so you do one thing well — export — and we handle the rest. Map, import, validate, launch. Most teams are running in OKRs Tool within two weeks.

Talk to us about your migration See your migration path
Parallel run while you migrate No mid-cycle disruption 60% adoption guarantee
The effort split

You do the export. We do everything else.

Your side
Export the data
  • Export from your current tool (CSV or native export)
  • Send us the file
  • Confirm the mapping we propose
  • Invite your team when we're ready to launch
Our side
Everything else
  • Map your fields to the OKRs Tool structure
  • Import your OKRs, KRs, owners, and history
  • Set up your cycles, permissions, and integrations
  • Validate the data with you before go-live
  • Handle the parallel run during transition
  • Run the training on your real (migrated) OKRs
Choose your starting point

Three migration paths. Same effort split.

The details of what maps and what doesn't change with each source tool. Pick your current setup for the specifics.

Migrating from · Lattice

Leaving Lattice? The OKRs come with you.

Lattice's CSV export gives us everything we need to rebuild your OKR structure on OKRs Tool — without losing history, ownership, or check-in data. Performance review data stays in Lattice (we don't compete with that); everything OKR-related moves cleanly.

Typical timeline
5–10 days
From export to live

What maps directly

  • Objectives & Key Results — full structure preserved
  • Owners — both objective and KR owners
  • Cycles — current + historical cycles
  • Progress values — current KR scores and status
  • Check-in history — comment threads and updates
  • Team structure — org hierarchy and reporting lines

What doesn't transfer

  • Performance reviews (stay in Lattice)
  • Compensation data (never in scope)
  • Career growth ladders
  • Custom fields specific to Lattice's data model
  • Lattice's custom emojis and reactions
Read the full comparison: OKRs Tool vs Lattice — how the models differ, and why teams switch.
See comparison →
Migrating from · Quantive / Workboard / Betterworks

Leaving enterprise OKR software? You'll ship faster.

Enterprise OKR platforms have deep data models — but that also means richer exports. We've migrated teams from Quantive, Workboard, and Betterworks; the OKR core maps cleanly. What doesn't transfer is usually the stuff people wanted to leave behind anyway — custom scoring formulas, governance workflows, and dashboard cruft.

Typical timeline
7–14 days
From export to live

What maps directly

  • Objectives & Key Results — hierarchy preserved
  • Alignment & cascade — parent/child relationships
  • Owners — single accountable owner per KR
  • Cycles — current cycle + historical archive
  • Initiatives — if you use them as sub-work
  • Progress values — latest scores per KR

What doesn't transfer

  • Custom scoring formulas (we use a simpler standard)
  • Multi-step approval workflows
  • Custom dashboard configurations
  • SAP or Workday deep integrations
  • Custom fields beyond OKR structure
Enterprise buyers usually find the setup phase is 3–5x faster than their previous rollout.
Book migration call →
Migrating from · Google Sheets / Excel / Notion

Outgrown the spreadsheet? The fastest migration path.

Most teams graduate to real OKR software when the spreadsheet stops scaling — usually around 20–30 people. The good news: your data is already in a portable format. Share the sheet, we clean it up, map it into OKRs Tool, and you're live. Same idea for Notion databases and Airtable bases.

Typical timeline
2–5 days
From share to live

What maps directly

  • Objectives & Key Results — whatever columns you have
  • Owners — auto-matched to invited users
  • Current status — on-track / at-risk / behind
  • Progress percentages — if tracked
  • Team assignments — department/team columns
  • Common formats: Google Sheets, Excel, Notion, Airtable

What we clean up

  • Duplicate rows, inconsistent naming
  • Missing owners (we'll flag them)
  • Vague KRs (we'll suggest tightening)
  • Free-text status like "kinda on track" (normalized)
  • Multi-owner KRs (we require one accountable)
Most spreadsheet migrations are done in an afternoon. Big ones take a few days.
Start free →
The migration process

Five steps. You're in step 1 only.

Everything after the initial export is on our side, with your team involved only at review checkpoints.

Day 0
Export
You export from your current tool. CSV, JSON, or native export. Send it to us.
Days 1–3
Map & import
We map your fields to OKRs Tool's structure and run the import into a staging workspace.
Day 3–5
Review
You review the staging workspace with us. Nothing goes live yet. We fix anything odd.
Day 5–10
Parallel run
Optionally run both tools in parallel for a cycle. Full confidence before you switch.
Launch
Go live
Structured launch. Training runs on your real, migrated OKRs — not dummy data.
The parallel run

Migrate without losing the cycle.

The biggest fear with migration is losing continuity mid-cycle. Our answer: run both tools in parallel for as long as you need — usually a week or two — and only cut over when your team is confident. No forced deadline, no bridge to demolish.

Most teams switch fully within 14 days. Enterprise migrations sometimes extend the parallel period through the end of a cycle for extra confidence.

  • Keep your current tool active
    Don't cancel your Lattice, Quantive, or Betterworks contract until you're running clean in OKRs Tool.
  • Copy in whatever's missing
    If new OKRs get added to the old tool mid-migration, we'll sync them into OKRs Tool for you.
  • Cut over when ready
    You decide when the parallel run ends. We recommend cutting over at a natural cycle boundary.
FAQ

The questions every migration starts with.

How long does a migration take, really?
Most teams are live in 1–2 weeks. Spreadsheet migrations can be done in a day. Enterprise migrations with heavy custom data models take up to 3 weeks. The parallel run can extend as long as you want it to, so there's no hard deadline for cutting over.
Do we lose our OKR history?
No. We import completed cycles, historical scores, and check-in history alongside your current OKRs. You keep the record of what you did in the last quarter or year — not just what you're doing now.
What if our old tool has data we can't export?
Rare, but it happens. In practice, every major tool has a CSV or API export. If yours doesn't, tell us what you're on and we'll find a path — sometimes that means scraping a report, sometimes it means rebuilding the current cycle manually with your team. Migration is included in concierge implementation on Expand.
Can we migrate mid-cycle?
Yes, though we usually recommend starting your parallel run mid-cycle and cutting over at the next cycle boundary. That way your team gets used to OKRs Tool without the mental overhead of switching sources mid-review.
What if we're on Lattice for performance reviews too?
Keep it. Lattice does performance review well — we don't compete with that part of the tool. Many customers run OKRs on OKRs Tool and continue with Lattice for reviews, then decide over time whether they want to consolidate. See our Performance section if you're considering moving reviews too.
Do you charge for migration?
Migration is included on the Expand plan as part of concierge implementation. Scale customers can migrate spreadsheets themselves with our guides, or request migration help for a one-time fee — scoped case by case.
What if the migration doesn't work out?
Every paid plan includes the 60% adoption guarantee. If your team doesn't reach 60% adoption in the first 30 days after go-live, we refund what you've paid. Migration doesn't create risk — it removes it.
Ready to switch?

Export the data. We'll do the rest.

Book a migration call and we'll walk through your current setup, map what transfers, and give you a timeline. No sales pitch, no slide deck — just a working session.

Book a migration call