Ask an MSP technician where the client’s network documentation lives and you’ll usually get a pause. The servers are documented. The workstations sync from the RMM. But the switches, the gateway, the access points scattered across the office? Those tend to live in one place only: the UniFi controller. And the controller is great at running the network and terrible at being a record you can search, audit, or hand to the next technician.
So the network inventory stays in Ubiquiti’s dashboard, disconnected from the rest of the client’s documentation. When you need to know which switch a printer is plugged into, or what firmware the gateway is running, or whether that access point in the back room is even still online, you’re logging into yet another portal instead of looking it up where everything else lives.
Weavestream’s UniFi integration closes that gap. It pulls device inventory from your UniFi controller directly into the client’s asset records, so your network gear is documented in the same place as everything else — and stays current without anyone typing it in.
What Gets Synced
The UniFi driver imports network inventory from your controller as asset records in the mapped tenant. For each device it brings over:
- Device name — the display name from the UniFi controller
- Model — the hardware model identifier
- Site — which UniFi site the device belongs to
- IP address — the current management IP
- MAC address — the device MAC
- Firmware — the installed firmware version
- Last seen — the last controller check-in timestamp
- Status — whether the device is online or offline
That’s the difference between a documentation record that describes the network and one that reflects it. A static asset entry someone typed during onboarding tells you what the network looked like two years ago. A synced record tells you the gateway is on firmware 7.x, last checked in four minutes ago, and is sitting at the IP you’d expect. When something’s wrong, that current-state view is the first thing you want.
Why Network Gear Belongs in Your Documentation, Not Just the Controller
The UniFi controller is an operational tool. It exists to configure and monitor the network in real time, and it’s good at that. But it was never meant to be your system of record, and using it as one creates the same problems as any other vendor dashboard that holds data nobody else can see.
Your network documentation is fragmented. Endpoints come from the RMM, servers are documented by hand, and network gear lives in Ubiquiti’s portal. To understand a client’s full environment you’re stitching together three sources. With the UniFi integration, the switches and access points sit in the same asset inventory as everything else, under the same company record.
There’s no audit trail tying network changes to the rest of the client’s history. When a device’s firmware changes or an access point drops offline, the controller knows, but that knowledge doesn’t connect to the client’s broader documentation. In Weavestream, every sync run and field change is written to the audit log alongside every other change in that client’s workspace.
And access is all-or-nothing in the controller. Anyone who needs to look up a switch model needs controller access. In Weavestream, the synced network records follow the same role-based access controls and client-portal scoping as the rest of your documentation — a technician can read the inventory without being handed the keys to reconfigure the network.
How It Fits the Bigger Picture
The real value shows up when the UniFi data sits next to everything else Weavestream already documents for that client. The access point’s management IP lines up with the subnet you’ve reserved in IPAM. The gateway shows up next to the domain and SSL monitoring entries for the services behind it. The switch a server connects to is one click from the server’s own asset record.
That’s the case for centralising network documentation rather than leaving it in a vendor dashboard: not that the dashboard is bad, but that the network is only one part of a client’s environment, and documenting it in isolation means you’re always cross-referencing by hand. Pull it into the same platform as the asset records, the credential vault, the IPAM subnets, and the audit log, and the network stops being a separate thing you have to go look up.
Because the sync uses upsert behaviour keyed on each device’s unique identifier, records are created on the first run and updated on every run after that. A device removed from the controller isn’t deleted from your documentation — it’s flagged as stale, so you keep the history of gear that’s been decommissioned or swapped out.
Setting It Up
You’ll need your UniFi controller URL and API credentials. In Weavestream, go to Admin → Integrations → New Integration, select UniFi as the provider, and enter the controller URL and credentials. Map the integration to the Weavestream company that represents the client, then click Save & Sync to run an initial import.
After the first sync, the integration detail page shows the last-run timestamp and any errors. Subsequent syncs can be triggered manually whenever you want a fresh pull, or run automatically on a schedule when background sync is enabled — so the network inventory stays current without anyone remembering to refresh it.
If you manage multiple clients on separate controllers, you configure one UniFi integration per tenant, each mapped to its own company. The network documentation for every client stays scoped to that client, just like the rest of their workspace.
Weavestream is a free, self-hosted, open-source IT documentation platform for MSPs and IT teams. It runs on Docker and Postgres, and includes asset management, a credential vault, IPAM, domain and SSL monitoring, a client portal, audit logging, and integrations with tools like NinjaOne, Action1, UniFi, and Cloudflare. Find out more at weavestream.io.