Overig · Overig
IAM and legacy systems, how to cleverly integrate older applications
Many organisations want to modernise IAM, but still use older or hard-to-integrate applications. With Joinly, you can securely and automatically integrate legacy systems into your Identity & Access Management processes. Thanks to flexible integrations, smart data mapping, and HR-driven provisioning, even outdated software becomes part of a future-proof and compliant IAM landscape without replacing systems.

Morten Broers · IAM specialist · 10 min read
IAM and legacy systems – how to cleverly integrate older applications
Identity & Access Management (IAM) is not just about modern cloud applications and trendy SaaS solutions. In many organisations, legacy systems still play a crucial role. Think of older tools, custom applications, or on-premise systems that once performed perfectly but now struggle to keep up with a modern security and compliance strategy.
However, there's good news: you don't have to replace these systems to professionalise IAM. At Joinly, we believe you can move forward with your existing application landscape. With the right approach, you can cleverly, securely, and automatically integrate older systems into your IAM processes.
Why legacy cannot be ignored
Legacy systems are often deeply embedded in processes and contain critical data. Replacing them is expensive and risky and sometimes simply not feasible. But they do pose a risk if:
Accounts are created manually,
Users retain access for too long,
Passwords are not managed centrally,
Authorisations are not set up uniformly.
IAM helps mitigate these risks but must integrate with those older systems.
The challenge: different languages, different times
Modern systems talk API. Legacy systems… sometimes do not.
Many older applications communicate, for example, through:
CSV files,
File drop mechanisms (FTP/SFTP),
Database connections,
Proprietary formats,
Or even strictly GUI-driven workflows.
This often makes most IAM solutions too limited. They expect modern interfaces, while organizations need that flexibility to support a mixed landscape.
The solution: smart coupling technology + HR-driven IAM
Joinly is built on one principle: everything can be connected. Including older systems. We achieve this with a combination of:
1. Flexible integrations via our platform
Joinly can handle both modern and traditional integration possibilities, such as:
APIs (REST, SOAP),
CSV import/export with validation rules,
SFTP transfers,
Direct database connections,
Mapping and conversion scripts for differing data models.
This allows us to include legacy applications in an automated IAM flow.
2. Smart conversion and data mapping
Legacy systems often have their own structures for functions, departments, or roles. Therefore, Joinly uses smart mapping modules that:
Automatically convert data,
Resolve inconsistencies,
Standardise authorisations,
And translate old structures into modern IAM roles.
You retain your old system, but with a modern IAM layer on top.
3. HR-driven provisioning as a foundation
Joinly ensures that employees, based on HR data, automatically:
Receive accounts in all relevant systems,
Have rights granted or revoked,
Have accounts deactivated upon leaving the company,
Have temporary roles and guest accounts managed securely.
Even older systems are included in this lifecycle — without manual work.
4. Applying Zero Trust, even to legacy
Zero Trust means: never assume someone should have access. Joinly easily incorporates legacy applications by:
Centralised password and account management,
Multi-factor authentication where possible,
Authorisations that are always traceable,
Logging and reporting for audits (e.g., ISO 27001).
In this way, you prevent legacy from becoming a weak point in your security model.
Practical example
Many organisations have older systems that do not offer modern API. Joinly can:
Read data via CSV or SFTP processes,
Automatically convert this to IAM roles,
Provision accounts in AD, Entra ID, or other target systems,
And process changes in real-time.
The result: employees are onboarded faster, fewer errors, less management, and 100% control over access.
Modernising IAM without replacing your landscape
The biggest misconception about IAM and legacy is that you can only modernise once you leave old systems behind. But in reality, you can start today by cleverly connecting, automating, and regaining control.
At Joinly, we combine modern IAM technology with powerful integrations, so that every system participates. New or old.
Also want to connect your legacy landscape smarter?
Do you want to discover how Joinly can modernise your IAM processes without major migrations? We are happy to demonstrate how our integrations work from modern SaaS systems to the most idiosyncratic legacy applications.
Get in touch with us, and we'll think along with you.
Explore more blogs

Segregation of Duties (SoD): wat het is en hoe je het afdwingt
Wat is segregation of duties (functiescheiding)? Uitleg, voorbeelden en waarom het vaak misgaat. Plus hoe je SoD-conflicten automatisch tegenhoudt.
Marcel van Beek · 4 min read

How do you apply AGDLP in a hybrid Entra/AD environment? (And why you shouldn't want to anymore)
Short answer: preferably not. AGDLP (Accounts → Global groups → Domain Local groups → Permissions) is a concept from the era of manual management. The entire nesting construction exists for one reason: to allow a human to assign permissions with as few mouse clicks as possible. As soon as an agent assigns group memberships directly based on HR data, this reason disappears and only the complexity remains. Moreover, in a hybrid environment, this complexity actively works against you, because Entra ID completely ignores nesting for licences and app assignment. In this article, you can read how AGDLP works and why it was once smart, where it breaks down in a hybrid environment, and what the modern alternative looks like: direct memberships, managed by automation.
Marcel van Beek · 5 min read

How do I set up role-based access control (RBAC) and least privilege for a municipality?
Start with the roles in your HR system and map them to roles, not to individual permissions per person. Group each role with precisely the access required for the job, adhering to the principle of least privilege. Manage these roles centrally and let an orchestration layer automatically assign and revoke them. This keeps access predictable, limited and demonstrable.
Mike Fraanje · 4 min read
See what Joinly can do for your organisation?
Start a free trial today or get in touch for advice on your HR and Microsoft environment.