Do you have a modern HR system, but still rely on Excel files, double entry and information that has to be moved manually between systems? Then there is more value to be gained. In a joint webinar with Exsitec, who are both a Hailey customer and help our customers build integrations, we discussed how HR and IT can create a more connected system landscape. Here, we summarise the key insights from the conversation between Jenny Clark from Hailey HR and Isak Hofvenstam from Exsitec.
The system landscape is an HR issue
HR is expected to be a strategic partner to the business. That also requires understanding how the HR system fits together with the organisation's other systems, and which data needs to move between them.
Jenny Clark, Enterprise Sales Manager at Hailey HR, believes that HR today cannot be a strategic partner without also bringing in the IT perspective and looking at the bigger picture of the organisation. This includes streamlining and automating processes, supporting managers, ensuring compliance and creating clearer business value from the investments being made.
When systems are not connected, the consequences quickly become tangible: the same information has to be entered in several places, employees spend time searching for information and the risk of errors increases. That is why the system landscape is not just a technical issue. It affects how effectively HR can work and how much value the HR system can actually create.
Integration is relevant for companies of all sizes, but the challenges become especially clear in larger organisations. There, the system landscape may consist of many legacy solutions that are not integrated with each other.
Manual processes create unnecessary risks
When an employee joins or leaves, information needs to be updated in several different systems. At the same time, the right permissions must be added or removed.
Isak Hofvenstam works as a business developer at Exsitec. He describes a common scenario where one or two people in the organisation need to keep full track of what information should be transferred between the HR system, the payroll system and other systems. When someone leaves, their personal data must be purged, and when someone joins, the same details are needed in several places, for example so that salaries can be paid.
“A lot of information is needed in many different places and systems,” says Isak Hofvenstam.
If the systems are not connected, the process relies on someone remembering to update the information in every place. This takes time, creates key-person dependencies and increases the risk of something being missed.
The HR system is the foundation that holds everything together
For the system landscape to work, the HR system needs to be the central source of employee and organisational data. That way, you only need to update the information in one place when an employee joins, changes role or leaves. With the right integrations, those changes are passed on automatically to the other systems.
This is particularly important in organisations that use several specialised systems. The HR system serves as the common foundation, while other systems handle areas such as payroll, scheduling, travel and expenses, or learning and development.
The information should flow both ways. If an employee completes a course in a separate learning platform, that record can be transferred back to the HR system automatically. This gives HR, the manager and the employee a single, complete picture.
Involve IT earlier
Whether you want to develop your current system landscape or are about to choose a new HR system, you need to start by understanding where you are today. Which systems do you use, how are they connected, and where are the biggest problems? This gives you a better basis for deciding whether to build on what you have or make a bigger change.
If you are planning to buy or replace an HR system, it is especially important to involve the IT department early in the process. Otherwise, integration can easily end up low on the priority list, which makes it harder to bring the system landscape together later on.
By involving IT early, HR can get help with:
- understanding which systems and data flows are affected
- identifying technical and security risks
- assessing which integrations are possible
- creating a better basis for priorities and budget
This does not mean everything has to be integrated from day one. Isak Hofvenstam emphasises that it can be perfectly reasonable to hold off on certain integrations. What matters is that it is a deliberate choice, and that there is a plan for how the system landscape will develop.
For HR, working with IT is about being able to describe the needs: Which processes do we want to improve? Which data needs to be available where? And where do our current ways of working create the most friction?
6 steps to a smarter system landscape
You don't need to have all the technical answers from the start. Begin by mapping where you are today and identifying where the greatest potential for improvement lies.
1. Map your systems and data flows
Start by building a picture of how information moves through the organisation:
- Which systems handle employee data?
- What data does each system hold?
- What information needs to be transferred between systems?
- Where is the same information entered more than once?
- Which people or functions depend on the information?
HR can do an initial mapping, but involve IT and finance to get the full picture.
2. Find the manual steps
Next, look at what happens between the systems. Where does someone need to export a file, copy information, re-enter the same information or remember to update another system?
Also try to estimate how much time the work takes. A manual step that only takes a few minutes can still eat up a lot of time if it is repeated often or for many employees.
3. Assess risk and consequence
Not all manual work is equally important to automate. So also ask what happens if something goes wrong. Isak Hofvenstam highlights two perspectives that are particularly useful when prioritising:
Risk and consequence: How likely is it that something goes wrong, and what would the error mean?
Time and manual work: How much time does the organisation spend keeping information up to date between systems?
A process that requires a lot of manual work and has major consequences if something is missed is a natural candidate to prioritise.
4. Identify which systems need to talk to each other
Once you have mapped your current situation, it becomes easier to see where integrations can actually create value. Common areas to look at more closely include:
- Payroll: so that core employee data doesn't have to be entered again.
- Time and scheduling: when several systems need the same employee and organisational data.
- Travel and expenses: for example for personal data and approval workflows.
- Learning: so that the right employees get the right training and completed activities can be followed up.
- Permissions and licences: so that access to systems follows the employee's role and employment.
Which integration should come first depends on your organisation. Start from your own needs, risks and time sinks rather than from whichever integrations happen to be available.
5. Find out what the integration actually does
When evaluating a new HR system, it is important to look at which standard integrations are available and what they actually do. The fact that an integration exists doesn't automatically mean it meets your needs.
Find out:
- what data is transferred
- how often the information is updated
- which fields are included
- whether the flow works for your processes and needs
A standard integration can be fully sufficient and a good way to get started. In other cases, a more tailored solution may be needed. You can also combine standard integrations with custom flows.
Jenny Clark gives a concrete example: an integration that only transfers first and last names is of limited use if the organisation also needs information about, for example, managers, organisational changes and dates.
6. Review the system landscape continuously
An HR system is never really “finished”. The organisation changes, new needs arise, and systems that worked well a few years ago may need to be used differently today.
That is why the system landscape needs ongoing follow-up. Ask, for example:
- Have our processes or needs changed?
- Are there new manual steps or time sinks?
- Are we using the systems the way we intended?
- Is there data that still has to be managed in several places?
- Have new integration needs emerged?
Jenny Clark points out that HR only gets the real return on the investment once the system works in day-to-day operations and is actually used across the organisation. The goal, then, is not to build a “finished” system landscape, but one that keeps evolving alongside the organisation.
Good data also lays the foundation for AI
There is another reason to get your system landscape in order: AI. Isak Hofvenstam points to clear master data and systems that can communicate with each other as an important foundation for AI-driven work.
But more AI doesn't automatically make a messy system landscape better. First, the organisation needs to know where its data is, who has access to it and how it is managed.
For HR, this means that questions around data security, compliance, permissions and data retention become even more important. A well-thought-out system landscape not only makes it easier to automate what you do today. It also gives you a better starting point for taking advantage of new technology in the future.
Build on what you have or start fresh with a new HR system?
Getting more out of your HR system doesn't always mean replacing it. Sometimes it is enough to connect the solutions you already have and improve the flow of information. In other cases, a new HR system can be the starting point for building a more connected system landscape from the ground up. What matters is starting from your organisation's needs and creating a solution that keeps working as the business develops.


