Still figuring out what to compare? Start with How to choose an HR system.
How long a rollout takes
The fast version: you create the company, upload your people, switch on one module and you're live within hours. It makes sense when there's nothing to migrate, or when you want the basics working and the rest tuned as you go.
The staged version: you break it into a few waves, let each one settle, and only then switch on the next. It stretches into weeks or months, but at every point you know what's changing and for whom.
Neither one is better. It comes down to what your operation can absorb and how much change your people can take at once. What matters is that the vendor doesn't push you into one of them — a system that can only go live as a whole is handing you its risk.
What drives the timeline
The timeline isn't set by the vendor. It's set by seven things on your side. The two that move it most are where you're coming from and what state your data is in. The rest are decisions — how many modules you switch on at the start, whether you build your own document templates, and how many people have to say yes.
| Factor | Shortens it | Stretches it |
|---|---|---|
| Your previous system | You don't have one — nothing to migrate, no habits to unlearn | Migrating from another system, or from a pile of spreadsheets |
| Modules at launch | One, the rest later | Everything at once |
| Attendance | One working schedule for everyone | Shifts, multiple operations, several locations |
| Legislation | One country | Two or more, each with its own rules |
| Data quality | One file, one consistent format | Files on a drive, a server and SharePoint, each one different |
| Document templates | You take the defaults | You build your own from scratch |
| Decision-making | One person with a mandate | Sign-off circulating through three departments |
The five phases of a rollout
1. Preparing the data. Export your employee list and fill in what's missing. This is the one phase nobody can do for you, and it usually takes the longest. Don't try to tidy up everything — what the first module needs is enough.
2. Basic setup. The company, the org structure, roles and permissions. This is where you decide who sees what, and it's worth sitting in on, dull as it is.
3. A pilot with a small group. One team, one module, two weeks. The point isn't to test the software but to find out what people are going to ask.
4. Going live for everyone. A short email to employees saying what's changing and where to log in. No hour-and-a-half training session — a system that needs one is a system you picked badly.
5. Switching on the rest. One module at a time, with a gap in between. Each one goes faster than the last, because the data and the habits are already in place.
Why to switch modules on one at a time
Switching everything on at once means every problem shows up in the same week and every employee hits the change at the same moment. When something doesn't work, you don't know what. Going one at a time is duller and it works.
An order that holds up for a company coming off spreadsheets:
- People and document records — the foundation everything else runs on
- Attendance and absence — the fastest visible relief, and mistakes show up immediately at payroll
- Onboarding — once the data and attendance have settled
- Documents and signatures — once you have templates everyone agrees on
- Performance, training, assets — whichever is pressing hardest
A system that makes you switch everything on at once is handing you its risk.
How to run a trial that tells you something
A thirty-day trial is the cheapest dress rehearsal for a rollout you'll get — but only if you put your own data into it. A trial full of sample employees tells you exactly as much as a demo.
| Week | What to do |
|---|---|
| 1 | Load the real employee list, set up the company and the roles |
| 2 | Run one real process end to end — ideally a new hire, or a month of attendance |
| 3 | Bring in two or three employees and let them use it without instructions |
| 4 | Take stock: what happened by itself, what you had to finish by hand, what people asked about |
If the trial needs a card, assume part of what's being tested is whether you remember to cancel it.
Who needs to be on the team
At a smaller company, two people will do: someone who sets the system up and has the mandate to decide, and someone who will work in it every day. The second one matters more. A system chosen and rolled out without them ends with the old spreadsheet still running next to it.
Management only needs to be there for two moments: the decision on scope at the start, and the decision to go live for everyone.
Five signs a rollout won't land
Nobody has the rollout in their job description. “We'll do it when there's time” means it won't get done.
Everyone is waiting for perfect data. The data will never be clean. Clean up what the first module needs and the rest sorts itself out in use.
The old spreadsheet is still running. Once Excel is being kept “just in case” on the side, six months later Excel is the only thing still being kept.
Employees find out on go-live day. One email in advance saves dozens of questions.
Nobody said when it's finished. Without a definition of “done”, a rollout doesn't end. It just dissolves.
Data migration: what to have ready
You already have most of what a migration needs — it just isn't in one place. The list below is what the first module you switch on will want; the rest can follow when its turn comes. Worry about the format once you know what the data is going into, not before.
- An employee list with personal and employment details, ideally in a single file
- Employment contracts and amendments in electronic form
- Vacation entitlements and balances as of the switchover date
- The org structure — who reports to whom
- Asset records, if you're going to keep them
- The dates you track: probation periods, medical checkups, training, expirations
Most of this already exists at your company, just in five different places. Tracking it down is ninety percent of the work.
FAQ
The five questions that come up most often around rollouts — how long it takes, whether all the data has to move at once, what stays on your side, whether employees need training, and how you know it worked.
Speybl is an HR application for all of HR — eight modules from hiring to offboarding in one system: people, recruitment and onboarding, attendance and shifts, performance, data and insight, documents and signatures, assets, training. AI agents take the routine steps off your hands and pass the result back for approval. It connects to Pohoda, Pamica, Money S3, Helios, Abra Flexi, Giriton, Microsoft 365, Google Workspace, Slack, DigiSign and Signi. Your data stays in the EU and support is available in English.
30 days free no credit card up and running in hours to days