Home/Insights/Moving HR data safely
Moving your HR data safely: clean-up, switching systems and POPIA
By Zené Olivier / Alexandra Wagener · Zanani People Solutions, Cape Town
7 min read

If people do not trust the data going in, they will not trust the system coming out.
To move HR data safely, clean it before you move it, decide who owns each type of data, set access levels in the new system and test the move more than once. Under POPIA, your organisation stays responsible for employee data even when a provider processes it, so check your contract, tell employees what is happening and take extra care with special information like biometrics.
This article is general guidance, not legal advice. For your own situation, speak to your specialist who handles privacy or legal matters in your organisation.
Why data is the hard part
In a South African Workday rollout, the implementation partner said the biggest pitfalls, and the most stressful phases, usually come during data migration and cut-over. The client team said they overcomplicated cut-over, validation and data migration, and spent a lot of overtime capturing and recapturing data (CHRO South Africa, Mastering Workday implementation).
Their advice: cut-over is not the time to optimise. Start simply. Add complexity later.
Clean your data before you move it
Do not move a mess into a new system. Clean it first.
- Find every source. Spreadsheets, the old system, payroll, email folders.
- Pick one source of truth for each field, such as job title or bank details.
- Fix duplicates and gaps. Same person, two records? Missing tax numbers?
- Check South African fields. ID numbers, tax reference numbers and Employment Equity fields often do not match across sources.
- Remove what you do not need. POPIA says do not keep personal information longer than needed.
- Standardise naming conventions as far as possible for accurate reporting and utilisation of data for decision making
- Get sign-off. Ask payroll and HR or other relevant departments and their systems, if it is extended integrations, to check a sample before the move.
AIHR recommends one trusted home for people data, with other systems pulling from it, and a data governance policy. That policy says who owns each type of data, who maintains it and who may view, edit or delete it (AIHR, 7 HR digital transformation challenges). We support this view in the work we do. Single source of truth for People data.
Switching systems: what to look out for
- Data. Can you get all your data out of the old system, in a usable format? Including history?
- Workflows. Map approvals for leave, overtime and onboarding before you rebuild them. Do not just copy old steps.
- Access levels. Decide who can see what. A line manager should not see the whole company's salaries.
- Timing. Avoid switching payroll at a busy time, such as tax year-end or other statutory reporting in the HR Calendar.
- Testing. Move a test batch first. Check it. Then move the rest.Test, test, and test again! The importance of testing can not be overemphasized.
- The old system. Keep read-only access for a while. Agree when to switch it off and what happens to the old data.
"Systems don't change organisations. People do." Zanani People Solutions
What employers must know about POPIA and employee data
Bowmans sets out the POPIA points that matter most when HR systems process employee data (Bowmans, AI in the workplace part 2: POPIA). The article focuses on AI, but most points apply to any HR system:
- You stay responsible. The employer is the "responsible party". A provider that processes data for you is an "operator". You remain accountable, so your contract with the provider must include POPIA duties.
- Tell people. When you collect personal information, employees must know what is collected, why, who receives it and whether it will go outside South Africa.
- Only what you need. Information must be relevant and not excessive for the purpose.
- Use it for its purpose. Data collected for one reason should not be used for an unrelated one.
- Keep it safe. Take reasonable technical and organisational steps to protect it, including when it sits in the cloud.
- Do not keep it forever. Keep it only as long as needed.
CHRO South Africa adds practical questions for any HR system provider: where is employee data stored, how is it processed, who can access it and what does your agreement cover (CHRO South Africa, Your HRMS should adapt to your business).
Biometric clocking and POPIA
Fingerprint or face scanners for clocking process biometric information. Under POPIA, biometric information is "special personal information". Bowmans notes that processing it is prohibited unless a specific exemption applies, such as consent or where it is necessary for employment law purposes.
SEESA, a South African labour law service, warns that relying on consent at work can be risky, because of the power imbalance between employer and employee (SEESA, When may you legally use biometric info under POPIA?). It suggests a Personal Information Impact Assessment first, and looking at less intrusive options.
In practice, before you roll out biometric clocking:
- Write down why you need it, and whether a less intrusive option would work.
- Do an impact assessment.
- Tell employees clearly what is collected and why.
- Check your provider's security and contract.
- Get legal advice for your situation.
An example
Picture a payroll officer at a security company moving to a new system. The old system had 1 200 employee records. The test move showed 90 duplicates and dozens of missing tax numbers.
Because the team tested early, they fixed the records before go-live. The first payroll run in the new system proceeded successfully without a single query about missing employees.
Try this on Monday
Pull 20 employee records at random. Check each one for ID number, tax number, bank details, EE fields and job title. Count the errors. That number tells you how much clean-up to plan before any move.
How Zanani helps
Zanani is an HR technology adoption partner and HR advisory. We help you get your people data ready, so the new system starts on a base people trust. Here is what that looks like for you:
- Data you can trust. Employee records are clean before they move.
- Clear ownership. Everyone knows who owns, edits and views each type of data.
- Privacy built in. POPIA questions are asked early, not after go-live.
- Employees who understand. People know what data is used, and why.
We work directly with organisations, and we also work with HR technology providers. Every organisation is different, so let's talk about how we do it.
FAQ
What should we look out for when switching HR systems?
Getting all your data out, mapping workflows before you rebuild them, setting access levels, timing the switch away from busy periods and testing a batch first.
How do you handle data clean-up before an HR system migration?
Find every source, pick one source of truth, fix duplicates and gaps, check ID, tax and EE fields as a few examples, remove what you do not need and get sign-off on a few sample sets of the data.
What must employers know about POPIA and employee data?
You stay responsible even when a provider processes the data. Tell employees what you collect and why, collect only what you need, keep it safe and do not keep it longer than needed.
When may we use biometric clocking under POPIA?
Biometric data is special personal information. It may only be processed if an exemption applies. Do an impact assessment, consider less intrusive options and get legal advice.
Who is responsible if our HR system provider has a data breach?
Under POPIA, the employer remains accountable as the responsible party. That is why your contract with the provider must include POPIA duties.
Getting your HR data ready to move? Email info@zanani.co.za or see what we do. We would love to talk.
FAQ: How do we support your digital journey?
