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 an open-platform video management system who want the detections to ship with the software rather than be assembled on top of it.
The cameras do not move, so switching changes what sits behind them and where the detections come from. Both rows describe what each vendor publishes.
Four moments when teams running an open-platform video management system start this conversation. If none of them are true, staying put is a reasonable answer.
XProtect is on-premises first, so the estate carries recording servers and storage on a capital cycle. When that cycle comes round the money is approved and the disruption is already scheduled, which makes it the cheapest moment to ask whether the replacement should be the same architecture with newer hardware. Model three years both ways against the same camera count and the same retention.
Milestone's own comparison chart marks XProtect LPR, Access, Transact, Retail, Incident Manager and Smart Wall as requiring a license, and BriefCam is a separate product with its own editions. So the detections a team actually wants usually mean another product, another contract and another integration. Write down the five things you need spotted, then ask each vendor which of them ship inside the platform.
Milestone publishes a four-stage product lifecycle, General Availability to Limited Availability to Discontinued to Terminated, with a stated minimum availability period of four years per VMS product. When a version reaches the end of that window the upgrade is happening either way, which makes it the honest moment to compare. Ask for both quotes against the identical site list over three years.
Milestone states plainly that it no longer updates drivers in the legacy device pack, that it will not fix bugs or extend their feature set, and that technical support on the system continues. That is a clear, published position rather than a gotcha. It does mean the oldest cameras in a mixed estate are frozen where they are, and it is worth knowing which ones before you plan a refresh around them.
The structural differences that decide whether a switch is worth starting.
Swipe the table sideways to see every column.
Milestone data comes from Milestone's own product pages, comparison chart and support documentation as of August 2026. Where Milestone publishes nothing, this table says so rather than guessing.
A rollout that keeps coverage live throughout. Most sites go live inside six weeks.
Inventory the fleet per site: manufacturer, model, resolution, codec and network path, plus which channels arrive through encoders and which cameras sit on the legacy device pack Milestone no longer updates. Then list the platform around it: the XProtect edition per site, the licensed add-ons, and every partner application with its renewal date. That second list decides how big this project is, because a site carrying two analytics vendors is a different cutover from a site carrying none.
Run one site live on both platforms at once. XProtect keeps recording while the same cameras stream to an Intelligent Video Recorder, so search, detection quality and what happens after a detection are compared on identical footage rather than on a demo reel. Pick the site with the messiest camera mix, because a fleet assembled over ten years is the real test and the newest site flatters everybody.
Move site by site rather than estate-wide, keeping XProtect 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. Retire a recording server only once the site behind it is signed off, and sequence the sites whose partner-application renewals land soonest to the front of the queue.
Once coverage is stable, the work moves from parity to the questions the recording layer was never asked: 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 where a hardware refresh turns into an operations project.
The six that come up in every one of these conversations.
Milestone publishes the license type per edition and it is perpetual, so those licenses are a sunk cost and the money does not come back whichever way this goes. The number that decides it is what the next three years cost from here: Care renewals, the server refresh already on the plan, storage growth, and every licensed add-on and partner application the detection list depends on. Compare that forward number, not the one already spent.
No, and the plan is built to make that structural rather than a promise. XProtect 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 on the recording servers under the retention you configured and does not migrate. Milestone documents exports in XProtect format with the Smart Client Player included, and in AVI or MKV, with password protection and a digital signature for authenticity. Export anything under a legal or insurance hold before those servers are decommissioned, and treat that list as a deliverable of the assess phase.
Camera reuse is common ground, and a page arguing that Milestone is closed is arguing with Milestone's own positioning. What changes is where the intelligence comes from. Milestone's chart marks LPR, Transact, Retail and the rest as licensed add-ons and publishes BriefCam as a separate product, so breadth is assembled. Spot AI ships 15+ pre-trained agents across security, safety and operations, plus Iris for a detection specific to your process.
It depends on your retention, your site count and how many partner applications the detection list currently needs, and anyone answering without those numbers is guessing. The shape of the spend changes: capital for servers and storage plus per-application licensing, against a per-camera subscription covering the software and the IVR. Quote both against the identical site list over three years.
Six things, and they are the same six whichever way you go. When each support agreement and partner-application license ends, and what notice each needs. Whether licenses are per device, perpetual or co-terminated. The export format and any time limit on historical footage. Which cameras are still under warranty. Who owns the camera VLAN at each site. And your own retention and data-residency policy in writing.
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. XProtect supports ONVIF and PSIA devices across its editions, so the fleet is already standards-based, and Spot AI reads any IP camera that speaks ONVIF or RTSP. Analog channels arriving through encoders today connect through the Intelligent Video Recorder instead. Nothing on the wall moves and no coax is pulled.
They stay with XProtect, because they are separate products with their own licenses and renewal dates. List them during assess and check which of their jobs a pre-trained agent covers, because that comparison is usually the clearest part of the business case and the easiest to get wrong from memory.
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 stream to an XProtect recording server and to an Intelligent Video Recorder at the same time, so the pilot compares search, detection and response on identical footage. XProtect keeps recording at every site until that site has passed a full week of sign-off.
XProtect is an open recording platform whose breadth comes from the ecosystem around it: on-premises servers, four editions, and analytics added as separate products. Spot AI keeps the on-site recording model, with full-resolution video on the Intelligent Video Recorder and only metadata leaving the building, and ships the detections inside the platform.