• What Horilla HRM Is and Who It Suits

• Phase 1 — Infrastructure and Environment Setup

• Phase 2 — Core HR Configuration

• Phase 3 — Data Migration

• Phase 4 — Integrations

• Phase 5 — Testing and User Acceptance

• Phase 6 — Go-Live and Hypercare

• What Makes a Horilla Implementation Go Well

• Working With an Implementation Partner

• Frequently Asked Questions

If you are evaluating Horilla HRM, the platform itself is only half the decision. The other half is understanding what implementation actually involves — how long it takes, what you need to prepare, and where projects typically run into trouble.

This article walks through the setup process from first configuration to go-live, so you can plan realistically rather than discover the hard parts mid-project.

What Horilla HRM Is and Who It Suits

Horilla is an open-source HRM platform covering the core people operations most growing businesses need: employee records, leave management, payroll, attendance tracking, recruitment pipelines, and performance management. Because it is open-source, it can be self-hosted and customised without per-seat licensing costs accumulating as your headcount grows.

That makes it a practical choice for UK SMEs and scale-ups that have outgrown spreadsheets and basic HR tools but are not ready for the enterprise pricing of Workday or SAP SuccessFactors.

The trade-off is implementation complexity. Horilla requires proper technical setup, configuration against your specific HR policies, and data migration work. It does not run out of the box the way a SaaS tool does.

Phase 1 — Infrastructure and Environment Setup

Before any HR configuration happens, the platform needs a home. This phase covers server provisioning, environment configuration, and initial deployment.

For most businesses, that means choosing between cloud-hosted deployment — AWS, Azure, and GCP are the common options — and on-premise installation. Cloud hosting is the more common choice for SMEs because it reduces the maintenance burden and makes disaster recovery simpler to manage.

The implementation team sets up the production environment, a staging environment for testing, and the database layer. SSL, domain routing, and basic access controls are configured here too. This is not glamorous work, but doing it poorly creates problems that compound throughout the rest of the project.

A clean Phase 1 typically takes one to two weeks, depending on infrastructure complexity and how quickly decisions get made on the client side.

Phase 2 — Core HR Configuration

This is where the platform starts to reflect your actual business. Configuration covers:

• Organisational structure — departments, job titles, reporting lines, and employee classifications

• Leave policies — annual leave entitlements, carry-over rules, approval workflows, and public holiday calendars

• Attendance settings — shift patterns, working hours, overtime rules, and flexible working arrangements

• Payroll parameters — pay periods, deduction categories, statutory requirements, and any custom pay components

The detail here matters. Horilla is flexible, but that flexibility means every policy decision has to be made explicitly during setup. If your leave policy has edge cases — part-time staff, probation period restrictions, different entitlements by seniority — those need to be documented before configuration begins, not discovered during user acceptance testing.

The most common cause of Phase 2 delays is incomplete requirements. Businesses often discover mid-configuration that their HR policies exist informally in people's heads rather than in any documented form. The implementation process forces that documentation, which is ultimately valuable — but it adds time if not anticipated.

Phase 3 — Data Migration

Moving employee data from your existing system into Horilla is one of the higher-risk parts of the process. The data involved typically includes:

• Employee personal records and employment history

• Historical leave balances and accruals

• Payroll history, if migrating mid-year

• Organisational hierarchy and role assignments

The quality of your source data determines how smooth this phase is. If your current HR records are spread across multiple spreadsheets with inconsistent formatting, the migration team will need to clean and normalise before any import can happen.

A structured migration follows a clear sequence: extract from source, map to Horilla's schema, clean and validate, import to staging, verify, then import to production. For payroll-critical data, running a parallel period — where both the old system and Horilla are live simultaneously for a defined window — is a sensible precaution.

Phase 4 — Integrations

Most businesses need Horilla to connect with at least one other system. Common integration points include:

• Payroll software or accounting platforms

• Recruitment tools or applicant tracking systems

• Identity providers for single sign-on

• Communication tools for notifications and approval workflows

Integration scope varies significantly. A simple webhook-based notification to Slack is a different exercise from a two-way sync with a payroll platform. This phase needs to be scoped carefully upfront — integrations added late in a project almost always create timeline pressure.

If you are running Odoo ERP alongside Horilla, there is meaningful overlap in HR and payroll data. Implementing both systems together avoids duplication and produces a cleaner data architecture than tackling them independently.

Phase 5 — Testing and User Acceptance

Testing is not optional, and it is not something the implementation team does alone. User acceptance testing requires HR team members to work through real scenarios in the staging environment: submitting leave requests, running payroll, processing a new joiner, handling a resignation.

The goal is to surface anything that does not match how your business actually operates before go-live. Training also happens here — for HR administrators managing the system and for employees using self-service features.

A structured UAT phase typically runs one to two weeks. Businesses that compress this phase to hit a deadline tend to discover the gaps they skipped in the first weeks after go-live. That is a worse outcome.

Phase 6 — Go-Live and Hypercare

Go-live is not the end of the engagement. The period immediately after launch is when real usage patterns emerge and edge cases that did not appear in testing show up.

A hypercare period of two to four weeks — where the implementation team remains closely available — is standard practice for any HRM deployment. During this window, configuration adjustments are made, user questions are answered quickly, and any data issues are resolved before they become embedded problems.

After hypercare, the engagement transitions to ongoing support: a defined arrangement for configuration changes, system updates, and new requirements as your business evolves.

What Makes a Horilla Implementation Go Well

The implementations that run smoothly share a few characteristics that have nothing to do with the platform itself.

A single internal owner on the client side — someone with the authority to make HR policy decisions — is the most important factor. When every configuration question requires a committee discussion, timelines slip.

Complete, documented HR policies before Phase 2 begins saves significant time. If your leave policy is not written down, write it down before the implementation starts.

Realistic data quality expectations matter too. If your current employee records need cleaning, build that into the project timeline rather than discovering it mid-migration.

Finally, treat UAT as a genuine testing exercise, not a sign-off formality. That is when problems are cheapest to fix.

Working With an Implementation Partner

Horilla's open-source nature means the platform is accessible, but the implementation expertise is not built in. Most businesses that attempt a self-managed setup underestimate the configuration depth and run into problems that an experienced team would have anticipated.

Working with a partner that has done this before means configuration decisions are made with an understanding of what causes problems downstream, data migration is handled with proper validation steps, and integration work is scoped accurately from the start.

We handle full Horilla HRM setup, configuration, data migration, and ongoing support as a live service. The same team that implements the platform supports it after go-live — there is no handover gap. You can see the kind of structured, outcome-focused work we bring to enterprise system implementations in our Pasalka Enterprises case study, where we eliminated paper-based processes and reduced operational costs by 35%.

If you are also evaluating broader people and workflow tooling, our HireVia case study shows how we approach HR-adjacent product builds that sit alongside or integrate with core HRM systems.

Learn more about our enterprise systems work at wireapps.co.uk.

Frequently Asked Questions

How long does a Horilla HRM implementation typically take?
For most SMEs, a full implementation from environment setup to go-live runs six to twelve weeks. The range depends on the complexity of your HR policies, the quality of your existing data, and the number of integrations required. Businesses with clean data and documented policies tend to land at the shorter end.

Do we need technical staff in-house to implement Horilla?
No. Horilla requires technical setup, but you do not need an in-house developer to run the implementation. An external partner handles the infrastructure, configuration, and migration work. Your HR team's involvement is needed for policy decisions and user acceptance testing — not technical tasks.

What data do we need to prepare before the implementation starts?
At minimum: a complete employee list with employment start dates and current role assignments, your documented leave policies and entitlements, your payroll structure including any custom pay components, and your organisational hierarchy. The cleaner and more complete this data is before the project starts, the faster the migration phase runs.

Can Horilla integrate with our existing payroll or accounting software?
Yes. The feasibility and effort depend on what your current platform exposes via API. This should be scoped during the discovery phase of the implementation — not added as an afterthought.

What happens after go-live?
A well-structured implementation includes a hypercare period of two to four weeks where the implementation team remains closely available to resolve issues and make configuration adjustments. After that, ongoing support covers system updates, configuration changes, and new requirements as your business grows.

Is Horilla suitable for a business with fewer than 50 employees?
Yes. Horilla is a practical option for businesses from around 20 employees upward, particularly where per-seat SaaS licensing costs are a concern or where specific HR policy customisation is needed. Below 20 employees, simpler tools may be sufficient.

What is the difference between Horilla HRM and Odoo HR?
Odoo HR is one module within the broader Odoo ERP suite, which also covers CRM, finance, inventory, and other business functions. Horilla is built specifically for people operations. If your primary need is HR management and you are not looking to consolidate other business systems, Horilla is often the cleaner choice. If you need HR alongside finance, inventory, and CRM in a single system, Odoo is worth evaluating. We implement both.