HR migration
Your client switches HR system, and the accounts carry on as normal
Moving to another HR system is a project for HR with its own schedule. For IT it is a risk: if the integration recognises nobody on switchover day, it looks as if everyone has left. With Joinly you see in advance whether the new system matches up.
The short answer
If a client switches HR system, you connect the new system in Joinly alongside the old one. A trial import shows you in advance whether the employees from the new system match the accounts that already exist, and a threshold stops an import that would suddenly block a lot of accounts. Your client's roles and workflows stay in place; only the source changes.
Why an HR switch is tense for IT
An integration recognises employees by what is in HR. When the system changes, the employee numbers, department names or the way roles are recorded sometimes change too. An integration that is not prepared for that sees an empty list on switchover day, or a list full of new people.
Connecting the new system alongside the old one
Joinly supports multiple HR sources at the same time. You connect the new system while the old one is still running, and run a trial import, a dry run. It shows in advance which employees match an existing account, and where something does not add up. You fix that before you switch over.
If something still goes wrong on switchover day, a threshold stops an import that suddenly changes far more than you expect. It only goes ahead once someone has looked at it.
Roles and workflows stay in place
Your client's roles, naming and workflows are based on job title, department and location. Which system that data comes from makes no difference to the roles, so they keep working after the switch. You only record which field in the new system means what.
HR migration
Frequently asked questions
What happens to the accounts when a client switches HR system?
Nothing, if the switch is well prepared. A trial import shows you in advance whether the employees from the new system match the existing accounts.
Can the old and the new HR system run side by side for a while?
Yes. Joinly supports multiple HR sources at the same time.
What if something still goes wrong on switchover day?
Then a threshold stops an import that suddenly changes far more than you expect, until someone has looked at it.
Do the roles have to be set up again?
No. Roles and workflows stay in place. You record which field in the new system means what.
- Joinly for MSPsFor an MSP, every joiner and leaver at a client is a ticket, a checklist and work that is hard to bill for. Joinly picks up those changes from your client's HR system and handles accounts, groups, licences and access automatically. For all your clients, from one login, with each client in its own environment.
- An HR integration per clientOne client uses AFAS, the next Nmbrs and a third a system you have never heard of. For an MSP, that is normal. Joinly connects them all to Microsoft Entra ID or Active Directory in the same way.
- Onboarding a new clientWhen you take over a client, you also inherit everything that has piled up over the years before you: accounts of former employees, shared logins and groups whose purpose nobody remembers. With Joinly you put HR next to your client's environment in the first few weeks and start with a clean slate.
- Multiple employmentsA nurse who also works evening shifts at another location. A teacher with a post at two schools. In HR those are two employments, and a simple integration turns them into two accounts. Joinly recognises that it is one person.
Account management for your clients as a standard service?
In an introduction we walk through how Joinly would work for your clients: which HR systems, which environments and where you want to start. We agree the terms of a partnership in the same conversation.
Book an introduction