...

The user used for sync doesn't need any System Rights at all.

It only needs access to the containers configured for sync, and all the objects in those containers which should be synced.
For the containers and objects, only "Read" access right is required

...

Specifying import criteria

All devices under the sync containers will be synced into Unimus.
(Unimus will find all nodes bound to each sync container and all containers under the sync container)

...

If only the container name is specified, the first container found in NetXMS matching the name will be used. To do so, following key value formant need to be used "container=Name".

For example "container=Customer A" (without quotes) would sync from container with name Customer A.

...

For example, specifying "id=1574" (without quotes) would sync from container with ID 1574.

Behavior pre-1.5.1

Before Unimus 1.5.1, NetXMS importer will import only devices which are direct members of the sync containers.
(it will not import devices in the downwards structure under the sync containers)

For each sync container, the importer finds the first NetXMS container that matches the name, and import the devices in that container.

When using NetXMS importer pre-1.5.1, we recommend creating a single sync container.
(for example, named "Unimus sync")

For that container, setup auto-bind rules to have all devices bound to the container you want to be synced to Unimus.

Then in Unimus, simply specify the 'Unimus sync' container to sync from.

How to configure the importer

...

For example: "10.2.0.111"

 22) Provide Username and password to access NetXMS.

...

4) Optionally, you can also schedule the importer.

You simply need to select an existing (or use the default) schedule.With this configuration, Unimus will sync against the NMS periodically.