Most HRIS implementations take somewhere between three weeks and nine months. A 30-person company moving off spreadsheets onto a lightweight platform can be live inside a month. A 2,000-employee business replacing a legacy system, with payroll and integrations in scope, should plan for six to nine months. The size of that gap is the whole point: headcount matters less than how many systems you are connecting and how clean your data is.
Below is what the timeline actually looks like at each size band, what a 2,000-person rollout involves, how long integrations take to build, and where projects usually lose weeks.
A realistic HRIS implementation timeline by company size
Vendors quote the best case. The figures below are closer to what teams report once discovery, procurement and internal sign-off are counted, which is where most of the hidden time sits.
| Company size | Realistic time to go-live | What drives the timeline |
|---|---|---|
| 1 to 50 employees | 2 to 4 weeks | Usually a single admin, one data source, no integrations. The bottleneck is whoever has to tidy the employee spreadsheet. |
| 50 to 250 employees | 6 to 12 weeks | Leave policies get complicated, managers need approval workflows, and payroll export has to be tested against a real pay run. |
| 250 to 1,000 employees | 3 to 6 months | Multiple entities or sites, shift patterns, an existing HR system to migrate from, and a formal UAT phase. |
| 1,000 to 3,000 employees | 6 to 9 months | Parallel payroll runs, integrations with finance and ATS, works council or union consultation, phased rollout by division. |
| 3,000+ employees, multi-country | 9 to 18 months | Country-by-country payroll, localisation, data residency, and an implementation partner running the programme. |
The jump between the third and fourth row is the one that surprises people. It is not the extra 1,000 employee records. It is that above roughly 1,000 people you almost always have a payroll parallel run, a second or third system to integrate, and enough stakeholders that decisions need scheduling rather than a quick call.
How long does an HRIS implementation take for a 2,000-employee company?
Plan for six to nine months from signed contract to full go-live if you are in one country with one payroll provider. Add three to six months for each additional payroll jurisdiction.
That number assumes a dedicated internal project lead. Without one, the most common outcome is not failure, it is drift: the project quietly stretches to twelve or fourteen months because nobody owns the decisions between vendor calls.
| Phase | Duration | What actually happens at 2,000 employees |
|---|---|---|
| Discovery and requirements | 3 to 5 weeks | Process mapping across HR, payroll, finance and IT. Every business unit surfaces a policy exception nobody documented. |
| Data audit and cleansing | 4 to 8 weeks | Reconciling employee records across the old HRIS, payroll and any local spreadsheets. This runs in parallel and always takes longer than scoped. |
| Core configuration | 6 to 10 weeks | Org structure, job catalogue, leave entitlements, approval hierarchies, permissions by role. |
| Integrations | 4 to 12 weeks | Payroll, finance, ATS, identity provider. Runs alongside configuration but gated by vendor sandbox access. |
| Data migration and reconciliation | 3 to 6 weeks | Two or three test loads before the production load. Balances have to tie back exactly. |
| UAT and parallel payroll | 6 to 8 weeks | Two full pay cycles run in both systems and compared line by line. Non-negotiable at this size. |
| Training and change comms | 4 to 6 weeks | Admins first, then roughly 150 to 250 line managers, then all employees. Manager training is the piece most often underfunded. |
| Go-live and hypercare | 4 to 6 weeks | Cutover at the start of a pay period, then daily triage for the first two cycles. |
Those phases overlap heavily, which is why the total lands around seven months rather than the eleven you get by adding them up. Two scheduling rules are worth holding to. Do not cut over in December or at the end of your tax year, and do not go live in the same month as a pay review, because you will not be able to tell a configuration bug from an expected change.
How long does it typically take to build an HRIS integration?
This is a separate question from implementation, and the answer depends almost entirely on which route you take. A prebuilt connector is an afternoon. A custom build against Workday is a quarter.
| Integration approach | Build time | Worth knowing |
|---|---|---|
| Native prebuilt connector | A few hours to 3 days | Authenticate, map fields, test. Only works if both vendors already support each other. |
| Scheduled CSV or SFTP file transfer | 1 to 2 weeks | Still the workhorse for payroll. Unglamorous, reliable, and easy to debug when a pay run looks wrong. |
| Unified API provider | 2 to 4 weeks for the first, days for each after | Services like Merge, Finch or Apideck give you one schema across many HR systems. Good when you need breadth, less good when you need unusual fields. |
| iPaaS platform | 2 to 6 weeks | Workato, Boomi or similar. Faster than coding it, and someone has to own the recipes afterwards. |
| Custom API build, one system | 4 to 12 weeks | Auth, field mapping, pagination, error handling, retries and monitoring. The engineering is rarely the hard part. |
| Custom build against enterprise HCM | 8 to 16 weeks | Workday Studio, RaaS reports or SOAP endpoints. Getting a sandbox tenant and the right integration credentials can eat the first month on its own. |
One warning that applies to all six rows: the build is not the long pole. Waiting for sandbox access, getting security sign-off, and agreeing which system is the source of truth for each field routinely take longer than writing the integration. If you are scoping a project, budget calendar weeks for those conversations rather than developer days.
HR software implementation timeline by platform
Published timelines vary widely because vendors measure from different starting points. The ranges here reflect elapsed time from contract signature to go-live for a mid-market customer, which is the number you can actually plan around.
| Platform | Typical time to go-live | Notes |
|---|---|---|
| HR Buddy Manager (hrbuddy.ie) | 1 to 3 weeks | Built for Irish SMEs, so leave rules, contract templates and handbook content ship configured to Irish employment law rather than needing to be built from scratch. Annual leave, time tracking, shift planning, e-signatures, gender pay gap reporting and payroll export via API are included, and onboarding is supported by their HR team rather than left self-serve. That combination is what compresses the timeline: most of the delay in a small rollout is policy decisions, not software setup. |
| Sage HR | 3 to 6 weeks | Quick if you are already on Sage payroll. Reporting is thinner than the mid-market alternatives. |
| BambooHR | 4 to 8 weeks | Well-drilled onboarding process. Payroll is US-centric, so non-US customers integrate out. |
| Employment Hero | 4 to 10 weeks | Broad feature set covering HR and payroll. Configuration takes longer precisely because there is more of it. |
| Personio | 6 to 12 weeks | Strong European coverage. Approval workflows and org structure setup are the slowest steps. |
| HiBob | 6 to 12 weeks | Flexible data model, which is a benefit and a time cost. Expect real effort in structuring fields properly. |
| Workday HCM | 4 to 12 months | The Launch package targets the short end for smaller deployments. Full HCM with payroll and integrations sits at the long end, almost always with a partner. |
| SAP SuccessFactors | 6 to 12 months | Modular, so timelines depend on how many modules you take at once. Phasing them is usually the sensible call. |
| Oracle Fusion HCM | 6 to 14 months | Heavy configuration and testing load. Rarely done without a systems integrator. |
| Dayforce | 6 to 12 months | Continuous payroll calculation means payroll testing is deeper than most and cannot be rushed. |
Where implementations actually lose time
Across most delayed projects, the cause is one of five things, and only one of them is the software.
- Dirty data. Duplicate records, missing start dates, inconsistent job titles, leave balances that do not reconcile. This is the single biggest cause of slippage at every company size.
- Undocumented policy. Teams discover mid-configuration that three departments calculate leave accrual differently and nobody has authority to pick one. Weeks disappear into that decision.
- No named owner. If the project is somebody’s fifth priority, the timeline stretches to fit whatever attention is left over.
- Scope creep during configuration. Someone sees the demo and asks for performance reviews too. Adding a module mid-build typically costs four to six weeks.
- Integration dependencies. Your payroll bureau’s availability, not your HRIS vendor’s, often sets the critical path.
How to hit the short end of the range
The teams that go live fastest tend to do the same handful of things.
- Clean the employee data before signing, not after. One CSV with correct start dates, employment types, managers, salaries and leave balances removes most of the risk.
- Write down the policies you will configure, including the exceptions, and get them signed off by whoever can overrule a department head.
- Go live with core HR first, then add payroll, then add performance or learning. Phasing beats a big bang at nearly every size.
- Name one internal owner with real time allocated, ideally a day a week for a mid-sized rollout.
- Book the parallel payroll runs into the calendar at kick-off, because they are the phase everyone under-plans.
- Pick a cutover date at the start of a pay period and well away from year-end.
Judging whether a vendor’s timeline is realistic
A quoted timeline is a sales artefact until you test it. Three questions usually reveal the truth. Ask whether the estimate starts at contract signature or at project kick-off, because the gap between those is often three weeks. Ask how many customers of your size and complexity went live in that window last year. And ask what the implementation team needs from you, by date, because a vendor who cannot answer that has not planned the project.
If a vendor quotes six weeks for a 2,000-person rollout including payroll, they are either excluding the parallel run or excluding your effort. Neither makes for a comfortable go-live.
Common questions
Can an HRIS be implemented in under a month?
Yes, for a small team on a platform with prebuilt policy templates, no legacy system to migrate from, and clean data. Anything involving payroll cutover or multiple entities will not fit.
How long does data migration take on its own?
Three to ten days for a small business, four to eight weeks for a large one. The variable is data quality, not record count.
Does switching HRIS take longer than a first implementation?
Usually yes, by roughly 20 to 30 percent. You are migrating history as well as current records, and you have to run both systems until you trust the new one.
When should we start if we want to go live in January?
For a small business, October. For 250 to 1,000 employees, the previous June. For 2,000 employees, the previous spring, and consider a February go-live instead so the parallel payroll runs are not competing with year-end.