Lattice is brilliant for performance management and OKRs; Notion is ideal for a flexible, all-in-one operating system for teams. If you’re consolidating tools or want tighter alignment between strategy, projects and knowledge, migrating from Lattice to Notion can make sense—provided you export the right data, remodel it well, and recreate key workflows.

What’s improved in this guide

• Clear mapping of Lattice objects (Goals/OKRs, Reviews, 1:1s, Feedback) to scalable Notion databases and templates.

• A step-by-step, low-risk migration plan (CSV/API options, data cleaning, imports, automations).

• Known limits, workarounds, and post-go-live success plan—grounded in current docs.

What changed recently

• Lattice supports CSV exports for Goals and Reviews and a public API for programmatic retrieval (Users, Goals, Feedback, Reviews, etc.).

• Notion imports CSVs (including “Merge with CSV”) and offers an API with ~3 requests/second per integration, plus a revised database/data-source model.

Why organisations move from Lattice to Notion

• Consolidation & context: Bring strategy, projects, docs and reporting into one OS, cutting switching costs.

• Custom workflows: Notion’s databases, relations and templates allow tailored OKR and review processes.

• Visibility: Link OKRs directly to roadmaps, project updates and meeting notes.

Note: Lattice excels at structured performance cycles and people analytics; ensure you won’t lose any compliance or analytics you rely on before deprecating. (Lattice supports centralised performance/engagement data and AI-assists; recreate only what you truly need in Notion.)

What data typically moves (source → target)

Known limits & practical implications

• CSV import scope: Notion supports CSV import and “Merge with CSV,” but some property types (e.g., Relations/People) don’t map directly from CSV—plan for post-import linking or API population.

• API throughput: Notion API averages ~3 requests/second per integration—batch wisely and include retry logic.

• Model changes: Notion’s 2025 API introduces data sources within databases—use current endpoints when automating.

Step-by-step migration plan

1) Discovery & scope (1–2 weeks)

• Inventory what you use in Lattice now (Goals/OKRs, Reviews, Feedback, 1:1s), what must be retained, and any HRIS linkages.

• Decide whether some processes stay in Lattice or move entirely to Notion.

2) Data export from Lattice

• OKRs/Goals: Admins/users can export to CSV; API also available for programmatic pull.

• Reviews: Export review cycle data (CSV) per cycle.

• Directory/People: Export directory if needed (CSV) or draw from HRIS.

3) Transform & clean

• Normalise owners, teams, dates, statuses; convert objectives/key results into a consistent schema (Objective, Key Result, Progress, Confidence, Period).

• Map Lattice fields to Notion properties (Title, Select/Status, Number, Date, Relation).

• Prepare lookup tables for teams/people to enable Relations post-import.

4) Notion architecture (target model)

• Databases:

  • OKRs (Objectives, Key Results, Period, Owner, Alignment)

  • Performance Reviews (Cycle, Reviewee, Manager, Ratings, Outcomes)

  • People (Name, Role, Team)

  • Teams (Name, Lead)

  • 1:1s & Updates (Date, Participants, Agenda, Actions)

• Templates: Review packet template, 1:1 agenda template, Quarterly OKR template.

• Dashboards: Company, Department, Individual views; link OKRs to projects and meeting notes. (Notion offers OKR workflows and examples to build on.)

5) Import into Notion

• Use CSV import (or Merge with CSV) for initial loads.

• For Relations/People or incremental updates, use the Notion API to create pages and set properties, respecting the current database/data-source model and rate limits.

6) Automations & integrations

• Rebuild critical automations (e.g., weekly OKR rollups, review reminders) using the Notion API and your automation stack. Include back-off/retry for rate-limits.

• If your HRIS used to feed Lattice (e.g., BambooHR), decide whether to mirror key fields in Notion via native CSV, third-party connectors, or light custom middleware.

7) Security, privacy & retention

• Confirm what must be retained from performance reviews and feedback; align with internal policies. Decide what needs archiving before switch-off.

8) Pilot, train, iterate

• Pilot with one department. Validate mappings, permissions, and dashboards.

• Train managers on Notion OKR and review flows; provide short videos and templates.

How Generation Digital helps

1. Assessment & design – We run discovery workshops, catalogue Lattice objects and dependencies, and design your Notion information architecture and governance.

2. Data pipeline – We handle Lattice CSV/API extraction, field mapping, and transformations—then import to Notion via CSV/API with auditability.

3. Workflow recreation – We rebuild OKR dashboards, review templates, and 1:1 agendas; we connect OKRs to projects, docs and meetings in Notion.

4. Automations – We re-establish key nudges and reporting using the Notion API in line with current rate limits and API model.

5. Change & enablement – We train managers and admins, write ops playbooks, and run a measured cutover.

6. Support – Post-go-live hypercare, plus quarterly optimisation.

Outcome: a maintainable Notion workspace where strategy, projects, performance and knowledge are tightly connected—without data loss or unpleasant surprises.

FAQs

Can we bring our existing Lattice OKRs into Notion?
Yes. Export Goals from Lattice as CSV or use the API, then import to a Notion OKR database and rebuild relations/dashboards.

What about review data and historical feedback?
Lattice supports review cycle CSV exports; you can store them as Notion pages with properties and attachments for packets, or retain a read-only archive alongside summaries in Notion.

Are there any gotchas with CSV imports to Notion?
CSV works well for first loads, but Relations/People normally need API population or post-import linking; plan for that.

Will the Notion API be fast enough for larger workspaces?
Yes, with batching and retries. The API averages ~3 requests/second per integration, so design jobs accordingly.

Next Steps

Plan your Lattice → Notion migration with Generation Digital.
We’ll assess your current Lattice usage, design a right-sized Notion architecture, run the data move, recreate key workflows and train your teams—end-to-end, UK-based, partner-led.

→ Book a 30-minute migration scoping call.