This works the same across every supported RMM — Datto, NinjaOne, N-central, N-Sight, ConnectWise Automate, ConnectWise Asio, and Kaseya VSA X. The mapping is keyed on devices, not on vendor-specific sites or organizations.
How Neo maps devices automatically
On every RMM sync, Neo resolves each device’s PSA company using the strongest signal available:- Exact name match — the device’s RMM organization or site name is matched (case-insensitive) against your synced PSA company names.
- Asset overlap — for devices an exact name can’t place, Neo looks up their hostnames among your PSA configuration items and maps the device to the company that owns them, but only when the evidence is near-unanimous.
Automatic mapping can’t resolve every device. Common cases: an RMM organization named differently from the PSA company (a rebrand), sites named by location code rather than company, or a PSA with few or no configuration items to match against. Those devices stay Unmapped until you assign them on the Device Mapping tab.
The Device Mapping tab
Open Integrations, select your connected RMM, and choose the Device Mapping tab. The header shows Total devices, Mapped, and Unmapped counts. The table lists each device with:| Column | What it shows |
|---|---|
| Device | The device name |
| Organization / Site | RMM context, where the vendor provides it |
| PSA Company | The mapped company (or ”—” when unmapped) |
| Source | How it was mapped — Auto, Manual, or Unmapped |
| Mapped by | Who set a manual mapping, and when |
Assign devices to a company
Filter to what you need
Use the Unmapped status filter to find devices that still need a company (or search by name).
Select the devices
Tick individual rows, or use the header checkbox to select the current page. When more devices match than fit on one page, click Select all N matching to select the entire filtered set across pages.
