The trigger moments that start this conversation, what actually changes on day one, and a four-phase plan that keeps every site recording throughout. Written for teams running Avigilon Unity or Avigilon Alta who want one answer across the estate rather than two.
The cameras do not move, so switching changes what sits behind them and how many platforms the estate runs. Both rows describe what each vendor publishes.
Four moments when teams running Avigilon start this conversation. If none of them are true, staying put is a reasonable answer.
Avigilon publishes two suites, Alta for cloud and Unity for on premises, and states in its own transition FAQ that there is no planned interoperability between them at this time. An estate that acquired sites on both lines is therefore running two platforms and two habits. That is a structural fact rather than a criticism, and it is usually what starts the conversation.
On the Alta side third-party cameras connect through an Alta Cloud Connector, and Avigilon publishes the ceilings: up to 200 camera sources per connector depending on model, and up to 50 connectors per deployment. It also lists several connector models as discontinued. Get the connector count for your real site list before you compare anything else, because that is what reuse costs.
Avigilon's own AI NVR 2 datasheet is precise about this: AdaptAI 5 is supported as server-side analytics for cameras without analytics of their own, while AdaptAI 6 is not supported as server-side analytics at this time. So the cameras that most need the server-side path get the previous generation. Ask which analytics apply to each camera model you actually own.
The published analytics are security, access and facilities shaped: Appearance Search, unusual motion and activity detection, license plate recognition, occupancy and mailroom. If the new asks are dock dwell, PPE on the night shift or a fire door propped at 02:00, write the list down and ask both vendors which of those arrive pre-trained.
The structural differences that decide whether a switch is worth starting.
Swipe the table sideways to see every column.
Avigilon data comes from Avigilon's own product pages, datasheets and documentation as of August 2026. Where Avigilon publishes nothing, this table says so rather than guessing. Avigilon cameras are ONVIF cameras and a compatibility partner here, not a competitive weakness.
A rollout that keeps coverage live throughout. Most sites go live inside six weeks.
Inventory the fleet per site, then note which Avigilon line each site runs, because a Unity site and an Alta site are different migrations. On Unity, list the servers and any AI NVR appliances and the licensed analytics on top. On Alta, list the Cloud Connectors and what each one carries, since that is the appliance count reuse currently depends on. Both lines are ONVIF-based, so the camera list is a coverage map rather than a replacement list.
Run one site live on both platforms at once. Avigilon keeps recording while the same cameras stream to an Intelligent Video Recorder, which is the only honest way to compare search, detection quality and what happens after a detection on identical footage. Pick a site with cameras that carry no analytics of their own, because that is where the server-side question actually bites and where the comparison is most useful.
Move site by site rather than estate-wide, keeping Avigilon recording at each site until its replacement has run a full week. Cameras do not move and cabling does not change, so a cutover is a configuration change plus an IVR. Sequence the sites whose subscription terms end soonest to the front, and retire a Cloud Connector or an AI NVR only once the site behind it has been signed off.
Once coverage is stable, the work moves from parity to what a security-shaped analytics list was never asked for: operations and safety agents on the same cameras, an Iris detection built in natural conversation for something specific to your process, and a decision about what fires at 03:00 with nobody watching. This is the phase where the switch stops being a consolidation exercise.
The six that come up in every one of these conversations.
Camera reuse is common ground and not the reason to move. Avigilon documents ONVIF support on both lines and its AI NVR datasheet says no rip-and-replace of existing cameras is required. What changes is the rest: one platform instead of two with no planned interoperability between them, an agent set that reaches into safety and operations, and full-resolution video staying in the building.
Most switches start before a term ends, because assess and pilot cost little and the comparison is more honest with both systems live. Avigilon publishes 1, 3, 5 and 10-year subscription SKUs per camera, so read your own end dates first, run the pilot on one site during the overlap, and time each site's cutover to its own term rather than paying twice across the estate.
No, and the plan is built to make that structural rather than a promise. Avigilon keeps recording at each site until its replacement has run a full week, the cameras never move, and cutover happens site by site. If a site fails its sign-off test, that site stays where it is while the others proceed.
It stays where it is, under the retention that site is configured for, and it does not migrate. Export anything under a legal or insurance hold before a subscription lapses or a server is decommissioned, and confirm which player is needed to open the export, because a native format that only opens in the vendor's own viewer is a problem you want to find in week one rather than in a deposition.
Six things, and they are the same six whichever way you go. When each subscription or support plan ends and what notice it needs. Whether licenses are per camera, per site or per appliance. The export format and any time limit on historical footage. Which cameras and appliances are still under warranty, including any connector model listed as discontinued. Who owns the camera VLAN at each site. And your own retention and data-residency policy in writing.
It depends on your camera count, your retention and how many appliances the current architecture needs, and anybody answering without those numbers is guessing. Price the connector or NVR count on each side, add the analytics that carry an additional license today, and quote both against the identical site list and the identical retention obligation over three years.
Bring a camera list and we will tell you what works as it is.
Customer-reported outcomes from named Spot AI customers.
Staccato went from first conversation to full deployment across an 800-acre campus in seven weeks, on the camera infrastructure it already had.
Bridge33 Capital standardized video across 25 plus properties, each acquisition arriving with a different camera system, and cut footage search from hours to minutes.
The YMCA of Greater Richmond deployed 17 locations in two weeks and standardized retention across the estate.
"Within four minutes of the alarm going off, Spot AI gave us video footage of the incident on the responding officers' phones. We had five recoveries within the hour."
No, and that includes the Avigilon cameras. They speak ONVIF, and Spot AI reads any IP camera that speaks ONVIF or RTSP whoever made it. Channels arriving through ONVIF encoders today connect through the Intelligent Video Recorder instead. Nothing on the wall moves and no coax is pulled.
It changes the assess phase rather than the plan. Avigilon states there is no planned interoperability between the two solutions at this time, so today those sites are administered separately. List which line each site runs, along with its appliances and term dates, then migrate in whatever order those dates suggest. The cutover itself is the same either way.
Most estates are live inside six weeks: a week to assess, a fortnight of pilot on one site, then site-by-site cutover. Sites go live individually rather than in a big-bang switch, so the timeline scales with how many sites you have rather than how many cameras.
Yes, and the plan depends on it. A camera can feed the Avigilon system and an Intelligent Video Recorder at the same time, so the pilot compares search, detection and response on identical footage. Avigilon keeps recording at every site until that site has passed a full week of sign-off.
Avigilon splits the decision by line: Alta is the cloud-native suite and Unity the on-premises one, with third-party cameras on Alta connecting through a Cloud Connector. Spot AI is one hybrid edge to cloud platform on any ONVIF or RTSP camera, with full-resolution video kept on the Intelligent Video Recorder in the building and only metadata leaving it.