A system is an external IT application or database that has been connected to NIM. All data that NIM reads & writes ultimately comes from, or goes to, a system.

To get started, Add a system or Import a system.

The following systems are officially supported:

  • Microsoft Active Directory

  • AFAS Profit

  • Microsoft Azure Active Directory

  • CSV files (source only)

  • Google Workspace

  • Microsoft Exchange

  • Microsoft Exchange Online

  • Microsoft SQL

  • Oracle SQL

  • PowerSchool

  • Skyward Qmlativ

  • Windows directory system (target only)


To test NIM with simulated HR source data, Add a File system and configure it with the HR500 test dataset.

It is also possible to add custom systems. This requires creating Custom connectors (REST or PowerShell).


The two most important aspects of a system are:

  1. Its data model (see Data models)

  2. The data collected from it, which depends on its data model

When you work with a system in the NIM Studio, you are generally working with its data model or its data.

In some user provisioning tools, there is a strong distinction between source and target systems. Not so in NIM. There is no such thing as separate "source" and "target" system objects. There are only system objects. Whether a system is a source or target simply depends on the current context in which it's being used, i.e., if it is being read from or written to.

Therefore, when this documentation refers to "source systems" or "target systems," it is only a pragmatic distinction based on the current context.


For example, if you're using a filter to feed data collected from system X into a mapping for system Y, system X is the source system and system Y is the target system. However, in a different context, it is conceivable that system Y might be used to feed data into system Z. In that context, system Y is now a source system.

The source and target capabilities available for different systems depends on their underlying Connectors. All official connectors support baseline source capabilities (i.e., data collection). However, target capabilities (i.e., CRUD functions of Mappings and Roles) tend to vary. For example, HR system connectors generally don't support target capabilities. This is because in provisioning scenarios, HR systems are typically used as read-only sources of truth.

If an official connector is missing a feature that you need, contact Tools4ever.