A 120-person company rarely decides to replace spreadsheets because one file is untidy. The decision usually follows a more revealing moment: a manager approves leave from an outdated balance, payroll receives three different headcount figures, or an employee asks who can see their personal data. This HRIS migration from spreadsheets example shows what a controlled move looks like when a small HR team needs better records without creating a six-month IT project.
The example is based on a growing European services business with offices in Belgium, the Netherlands and Germany. Its two-person HR team used separate spreadsheets for employee records, annual leave, onboarding tasks, training and performance review dates. Payroll was managed elsewhere. The spreadsheets worked when the company had 35 people. At 120, every change created a chain of emails, duplicate updates and uncertainty over which version was correct.
The starting point: useful spreadsheets, growing risk
The company had not been careless. Its spreadsheets contained years of useful information and had been adapted carefully as needs changed. But the process depended too heavily on individual knowledge. One HR manager knew which tab held contract end dates. Finance maintained a different list of cost centres. Team leads kept local absence trackers because they did not trust the central leave balance.
The immediate objective was not to digitise every HR process at once. It was to create one reliable employee record, give employees and managers appropriate self-service access, and make leave and onboarding visible without chasing updates. That narrower scope mattered. A migration succeeds when the organisation solves its most costly problems first, then builds from a stable foundation.
Before selecting fields or importing files, the HR lead agreed three principles with finance and operations. The HRIS would become the source of truth for people data. Every data field would have a named owner. Historical information would move only where there was a defined business, legal or employee-service reason to keep it active.
An HRIS migration from spreadsheets example, step by step
1. Map the data before moving it
The team started with an inventory of every people-related spreadsheet, not just the main employee register. They found 14 files across shared drives and personal folders. Some contained the same data under different column names. Others held information that should never have been copied into a general HR file, such as sensitive notes from employee relations cases.
They grouped each field into one of four decisions:
- migrate as an active HRIS field, such as legal name, work location, manager and start date
- migrate as a document or controlled record, such as signed contracts and right-to-work evidence
- retain outside the HRIS with restricted access, such as formal case files
- archive or delete under the organisation’s retention rules
This stage exposed the usual issues: inconsistent job titles, old managers still assigned to employees, missing emergency contact details and dates entered in multiple formats. None of these are technical migration problems. They are data governance problems that a new system makes visible.
For an SME, this work is often more valuable than the import itself. It establishes who is responsible when a manager changes, an employee transfers country or a contract is renewed. Without that ownership, an HRIS can become a more polished version of the spreadsheet problem.
2. Create a practical minimum data set
The HR team resisted the urge to make every field mandatory on day one. They defined a minimum data set needed to run core HR processes: personal and work contact details, employing entity, location, department, manager, job title, start date, employment type, working pattern, leave policy and key compliance documents.
They also agreed standard values for departments, locations and employment types. This sounds administrative, but it prevents reporting from becoming unreliable. If one employee belongs to “Sales”, another to “Commercial” and a third to “Sales Team”, headcount reporting will require manual repair every month.
Where employees worked across borders, the team checked that country-specific fields and leave rules were configured appropriately. A shared approach is useful, but not every policy should be forced into a single template. Local public holidays, working-time practices and document requirements may differ.
3. Clean, validate and assign owners
Next, HR exported the source files into a controlled migration workbook. Each field was mapped to its destination in the HRIS, with an owner responsible for checking it. HR verified employment information, finance checked entities and cost centres, and line managers confirmed reporting lines and working patterns.
The team did not ask managers to validate everything. That would have slowed the project and produced uneven results. Instead, managers received a short, focused request covering the information they were best placed to know: team structure, job titles and any upcoming changes.
Employees then reviewed their own contact details and emergency contacts during the launch process. Self-service is not just a convenience feature here. It improves data quality by placing routine updates with the person closest to the information.
4. Test with a small group before launch
Rather than importing all records and announcing the platform immediately, the company ran a pilot with HR, finance, three managers and ten employees from different countries. They tested the processes people would actually use: requesting leave, approving an absence, updating a home address, completing onboarding tasks and locating a policy.
The pilot revealed two problems. First, leave balances had been imported correctly but were presented in a way that confused part-time employees. Second, manager permissions were too broad for a regional structure. Both were corrected before launch, when the impact was manageable.
Testing should include permissions as well as workflows. HR data is personal data, and access should follow roles, not curiosity or convenience. For European SMEs, it is sensible to confirm where data is hosted, how environments are separated and how access is audited. These questions are part of implementation, not an afterthought for procurement.
5. Launch around real moments of work
The company launched the HRIS at the start of a leave cycle, after payroll had completed its monthly cut-off. This gave HR a clear point from which new leave requests had to be submitted in the system. They did not run the spreadsheet and the HRIS indefinitely in parallel. For two weeks, HR checked exceptions daily, then retired the old leave tracker as the operational record.
Communication was concise and specific. Employees were told what they needed to do, why it mattered and where to get help. Managers received a short session on approvals, team records and their responsibilities for accurate data. The HR team prepared answers to predictable questions, including how to correct a leave balance and who could view personal information.
Adoption improved because the system replaced work rather than adding another task. Employees could request leave in one place. Managers could see their teams’ absences before approving. HR stopped rekeying changes across several trackers.
What changed after 90 days
After three months, the company had a clearer headcount view, fewer requests for basic employee information and a more reliable onboarding process. HR was not spending Mondays reconciling absence records. Finance received a consistent employee-change report before payroll cut-off. Managers could see essential team information without being given unrestricted access to HR records.
There were trade-offs. The first migration did not include every historic appraisal note or every training record. The team chose to archive much of that material and bring forward only current objectives, required certifications and active development plans. That was the right choice because it reduced clutter and avoided transferring records with unclear purpose or inconsistent quality.
A different organisation might decide otherwise. If historic qualifications are needed for regulated work, or past review data informs compensation decisions, a fuller migration may be justified. The point is to make that decision deliberately, not to import everything simply because it exists.
Where growing teams commonly lose momentum
The most common mistake is treating migration as a data-upload exercise. Software configuration matters, but the difficult work is agreeing how the organisation will operate after launch. Who updates a manager change? When does an onboarding workflow begin? Which system owns a leave balance? What happens when a local policy changes?
Another mistake is trying to replace every disconnected tool in a single release. A consolidated platform can reduce fragmentation, but a phased approach is often safer. Start with the employee directory, documents, leave and onboarding. Add performance, learning, expenses or recruiting once the underlying data and habits are reliable.
For teams evaluating a platform such as Cognitis.cloud, the practical question is not whether every feature can be switched on immediately. It is whether the platform can give HR one dependable foundation while allowing processes to grow at a sensible pace, with EU-gegevensresidentie and access controls that fit the organisation’s obligations.
The spreadsheet is not the enemy. It was a reasonable tool at an earlier stage. The signal to move on is when maintaining it takes more effort than managing the people information it was meant to organise. Start with a clear source of truth, involve the people who own the data and make the first launch useful enough that nobody wants to return to the old tracker.
