field note

Security system takeover: the first weeks on a new account

A security system takeover is when an integrator inherits another company's install. How to recover access, inventory the cameras, and quote what is wrong.

2026-10-25

A security system takeover is when an integrator takes over service of a camera (CCTV) system that another company installed, usually because the customer has stopped working with the original integrator. The installed base is already there, the customer is already unhappy with the service they had, and the first few weeks decide whether the account becomes steady service revenue or another complaint.

Takeovers are some of the best accounts an integrator can win. There is no install to bid against three competitors. The customer has already decided to switch. And the previous integrator usually left a list of problems that becomes the first quote. The risk is that the new integrator inherits those problems without documenting them, and ends up blamed for failures that were there on day one.

Before signing: ask for what you will need

Ask the customer for these before the agreement is signed. What comes back, and what does not, tells you how hard the takeover will be.

  • Admin credentials for every camera, recorder, and the VMS, or confirmation that nobody at the customer has them.
  • As-built drawings and a device list, however old.
  • VMS licenses and support status, including who holds the license account.
  • Network information: which VLANs the cameras are on, who manages the switches, and a contact on the customer’s IT team.
  • Warranty and support status for cameras and recorders still under manufacturer coverage.
  • The reason they are switching. It tells you what the customer will judge you on first.

Many integrators charge a takeover inspection fee to cover the first visit and the inventory. It is real work, and a customer who will not pay for it is often a customer who will not pay for service either.

Access is the first problem

On most takeovers, the hardest step is getting into the cameras. The previous integrator may hold the only admin passwords and may not be in a hurry to hand them over. Sometimes nobody knows them at all.

A factory reset is the only way back into a camera whose admin password nobody knows. That is a physical action at the camera, it wipes the configuration, and the camera then has to be set up again and re-added to the VMS. Every camera without known credentials is a site visit, not a remote task. Price and schedule it that way.

When credentials are recovered, rotate them. Shared passwords, factory defaults, and accounts the previous integrator created should not survive the takeover. The order matters, because the VMS and anything else that logs in to the cameras must get the new password at the same time. The safe sequence is in how to rotate camera passwords without breaking your VMS.

The first weeks of a security system takeover. Week one recovers access and resets cameras with unknown passwords. Week two inventories every device from the devices themselves. Weeks three and four record a dated baseline of what is wrong and deliver a findings report with a quote. After that, the account runs on a service agreement. a takeover in four steps, each one dated week 1 recover access reset unknowns week 2 inventory from the devices weeks 3-4 dated baseline findings, quote then service agreement the baseline is the line between their problems and yours anything found before it is a finding. anything after it is service
Recover access, inventory, record the starting state with a date, then quote. The dated baseline is what protects the new integrator from inheriting blame.

Inventory from the devices, not the drawings

As-built drawings on a takeover are usually out of date. Cameras were swapped, added, moved, or removed, and nobody updated the drawing. Build the inventory from what each camera reports about itself: make, model, serial, firmware version, network address, and location.

The inventory almost always turns up surprises:

  • Cameras on the drawing that no longer exist, and cameras on the network that are not on the drawing.
  • Mixed firmware across identical models, because some were updated and others were not.
  • Cameras on factory default or shared passwords.
  • Models past the manufacturer’s end of support.
  • Hardware from manufacturers covered by Section 889 of the NDAA, sometimes sold under another brand name. The NDAA camera checker covers how to identify it.

Record a dated baseline

Before fixing anything, record the state of every camera with a date: what is reachable, what is offline, what firmware each runs, which credentials are known, which SD cards are failed or missing, and which certificates are expired or close to it. Share it with the customer in writing.

This baseline protects the integrator. A camera that was offline before the takeover is a finding, not a failure on the new integrator’s watch. Without a dated record, the customer will remember every problem as starting after the switch.

Turn the findings into a quote

The baseline becomes the first proposal. Sort findings into three groups the customer can act on:

GroupExamplesHow to present it
Fix nowCameras offline, failed recording, default passwords, expired certificatesQuoted as one remediation project, done in the first month
PlanModels past end of support, covered NDAA hardware, inconsistent firmwareQuoted as a phased refresh, with each camera named
OngoingMonitoring, firmware, rotation, reporting, preventive visitsThe service agreement that keeps it from drifting back

Present the fix-now group as the cost of getting the system back to a known good state. Most customers who switched integrators expected that list, and the integrator who brings it with names and locations attached looks like the right choice.

Doing this across 500 cameras

On a small site, a technician with a laptop can recover access and build an inventory in a day. On a takeover of hundreds of cameras across several sites, the inventory and baseline are a week of work by hand, and they start going stale before the findings report is written.

MentatNOC is a white-label managed services toolkit for security integrators. Once access is recovered, it puts every camera under management on continuous watch and builds the inventory from the devices themselves: model, firmware and its support status, reachability, storage, certificates, and time. The record is dated from the first day, which is the baseline. Credential rotation runs as a staged change that keeps monitoring working. It monitors device health, not video.

A takeover is the moment to write it into the new service contract, bundled with the monitoring the integrator already sells. From day one, each alert opens a classified ticket in the integrator’s own ticketing system under their own SLA, so dispatch knows which inherited camera failed at which site before the truck leaves, and the new integrator is the one calling the customer about an outage instead of hearing about it. The layers are on the platform overview, and the live demo shows a 500-camera fleet with its findings.