# How to clean people data before an import

Guide, 8 Nov 2026, read 8 Nov 2026

**The short answer.** Cleanse before the import, never after: one spelling per manager, one date format, one entity per row, one contract type from a short list, a start date for everyone, a leaving date and reporting line for every leaver, a salary band instead of a salary, and no duplicate people. The calculator gives it twelve hours per hundred.

## Why the import is the wrong place

Every destination on this site imports what it is given. Shapes generates a directory proposal from the upload and an agent refines it before approval, which catches a manager who does not exist but not a manager spelled two ways; BambooHR's trial loads the file as it is; an implementation team at HiBob, Rippling or ADP loads what the customer sends. A dirty file becomes a dirty system with a new logo, and the first report the CEO asks for is wrong in a new way.

## The nine checks

- Managers: one spelling, one email, and every manager is also a row. A manager who left is replaced by the person who holds the team now, with the old reporting line kept in the leaver export.
- Dates: one format, no text. Start dates for everyone; probation end dates where the policy has them.
- Entities: one legal entity per row, named as the destination will name it. A location is not an entity.
- Contract types: a short list (permanent, fixed term, contractor, intern, EOR) and nothing else.
- Leavers: kept, not deleted, with the leaving date, the reason from a short list and the reporting line at the time; attrition by manager is impossible without it.
- Pay: a band, a currency and an effective date; the salary itself goes in last, into the field the destination marks sensitive, by the person who may see it.
- Locations and policies: each location maps to a time-off policy, a working-time policy and a payroll provider.
- Duplicates: the same person in two rows (a rehire, a transfer) becomes one row with history.
- Custom fields: each has an owner, a type and a reason; a column nobody can explain is archived, not imported.

## What to keep outside the system

The cleansed file is the import; the original file and the leaver export are the archive, read-only, with the date. The destination's audit log starts at the import, so the archive is the only record of what the old system held before. Shapes's audit log and field change reports, BambooHR's Audit Trail and Humaans's audit log all begin on day one of the new system and not before.

## Sources

- Shapes: build your directory with an agent: https://shapes.co/releases/build-your-directory-with-an-agent (read 8 Nov 2026)
- Shapes field-level permissions: https://shapes.co/releases/sensitive-fields (read 8 Nov 2026)
- BambooHR Audit Trail: https://www.bamboohr.com/product-updates/bamboo-ai (read 8 Nov 2026)

Last reviewed 8 Nov 2026. Canonical: https://hrisalternatives.com/guides/clean-people-data-before-an-import/
