# Leaving Lattice: the 30-day plan

Leaving Lattice, read 8 Nov 2026

**The plan in short.** Leaving Lattice means leaving a talent platform and, for a few US companies, an HRIS in limited beta: single and bulk exports cover reviews, goals and engagement, the API and the MCP server reach the data, contracts are annual with a $4,000 minimum, and the notice period is not published. Export every review cycle before the term ends.

Week 1 export / Week 2 map and cleanse / Week 3 import and parallel / Week 4 cut over

## Week one: export everything, in this order

- **Export formats, as published:** single and bulk exports (optimised or standard); CSV bulk tools
- **API access:** Lattice API and MCP
- **Notice to give:** not published (checked 2026-11-08)
- **Documents and e-signed files:** not stated in the export formats read on 8 Nov 2026; ask for a bulk document export in writing

Week one: bulk export reviews, goals, 1:1 notes, feedback and engagement results cycle by cycle; the optimised and standard exports differ, so take both. For the HRIS beta, export the people data by CSV and ask Lattice in writing for the retention terms, which the trust centre does not state.

## Week two: map the data model and cleanse

- Fields: person, entity, manager, job, contract type, location, start date, salary band, custom fields by name.
- Entities and policies: one row per legal entity, one row per time-off and working-time policy, who approves each.
- Documents: contracts, right-to-work evidence, signed policies, with the signing date and the signer.
- Reporting lines at the leaving date for every leaver in the last two years, so attrition by manager survives the move.

The mapping is a performance history into a destination module or an archive: calibration, succession and talent reviews rarely have a one-to-one home, and the plan archives them as PDFs and CSVs rather than forcing them into fields.

## Week three: import, then run both systems for a week

- **Destination import:** build your directory from a spreadsheet or with an agent; bulk import; run any integration sync now
- **Payroll and ATS:** Re-point the payroll export and the ATS hire webhook on the Monday; run one payroll cycle from both systems if payroll moves.
- **Checks:** Headcount by entity, next payroll run, every open time-off request, every document awaiting signature.

There is no payroll to run in parallel; the parallel week is the first review cycle planned in the destination while the last one closes in Lattice. The cutover is the annual term end, which is the only date that matters.

## Week four: the people-facing change and the first-week checks

- Tell employees the date, the sign-in route and what to check in their own record.
- Managers: their team list, their open approvals, their onboarding tasks.
- Day one: the audit log for anything an import wrote; day five: the first report the CEO asks for.
- Cancel the old system in writing within its notice period: not published (checked 2026-11-08).

## What this move costs at 150 people, on the calculator's assumptions

- **People time:** 64 hours, £2,869
- **Overlap on the old term:** £4,563 (Foundations package at $13, 3 months)
- **Destination implementation fee:** not published (No fee published; Plus includes guided implementation; 'Most teams are up and running in days, not weeks' (vendor claim).)
- **Calendar:** 5 weeks: export 1, cleanse 1, import 1, parallel run 1, cutover 1

**Where Shapes is weak.** Shapes is not the destination for a company that wants payroll run inside the HRIS.

## Sources

- Lattice: export: https://lattice.com/blog/march-2026-product-updates (read 8 Nov 2026)
- Lattice: API: https://lattice.com/platform/mcp (read 8 Nov 2026)
- Lattice: retention: https://trustcenter.lattice.com/ (read 8 Nov 2026)
- Lattice: notice period: https://lattice.com/pricing (read 8 Nov 2026)
- Lattice: minimum term: https://lattice.com/pricing (read 8 Nov 2026)
- Shapes: export: https://shapes.co/releases/export-all-employee-files-at-once (read 8 Nov 2026)
- Shapes: API: https://shapes.co/pricing (read 8 Nov 2026)
- Shapes: retention: https://shapes.co/legal/dpa (read 8 Nov 2026)
- Shapes: notice period: https://shapes.co/legal/terms (read 8 Nov 2026)
- Shapes: minimum term: https://help.shapes.co/en/articles/9569350-shapes-pricing (read 8 Nov 2026)

Last reviewed 10 Nov 2026. Canonical: https://hrisalternatives.com/switch-guides/leaving-lattice/
