What's actually changing: Unity vs Alta

Avigilon (owned by Motorola Solutions, headquartered in Chicago) ships two video paths today. Avigilon Unity is the on-prem path: cameras, ACC (Avigilon Control Center) software on a Windows server or HD Video Appliance, plus annual ACC Software Maintenance. Lower recurring cost, higher Day 1 hardware bill, and full on-prem analytics including Appearance Search and Unusual Motion Detection.

Avigilon Alta is the cloud path. Cameras phone home to Alta cloud, no on-prem server, per-camera cloud license recurring. Closer in shape to Verkada's model. Alta also includes Alta Access (formerly Openpath) for doors, so video plus access can run on one tenant. Ava analytics (Motorola acquired Ava in 2022) layer extra behavior detection into Alta.

Both paths are NDAA Section 889 compliant per Avigilon's published statement. The migration question is whether the cloud-only model fits your IT shape, retention policy, and 5-year TCO.

Stay on Unity or migrate to Alta: the honest read

Half the customers we audit don't need to migrate. Avigilon and resellers have an incentive to move you to recurring SaaS. We don't. Here's the unbiased read.

  • Active 5-year ACC warranty + healthy analytics: If your ACC cameras are inside warranty and Appearance Search plus Unusual Motion Detection do what you need, migration is paying twice. Stay on Unity until the next hardware refresh boundary. We'll tell you that on the audit.
  • On-prem-required deployments: Alta is cloud-only. If your security or compliance team requires on-prem video storage (some healthcare, government, data-sovereignty cases), Alta is the wrong direction. Unity stays the right answer, or migrate sideways to Genetec or Milestone.
  • Large camera-count single sites: Unity scales cleanly into thousands of cameras per site (transit hubs, stadiums, ports, large campuses). The architecture and licensing are tuned for that scale. Alta is improving here, but Unity is still the answer for the largest single-site deployments.

When migration makes sense:

  • Multi-site lean-IT deployments: Multi-site retail, K-12 districts, healthcare networks where each site has thin or no IT and managing per-site ACC servers is the real burden. Alta's cloud-only model removes the server count entirely. This is the cleanest migrate case.
  • Aging ACC server hardware: If your HD Video Appliance or ACC server is past 5 to 7 years and refresh is on the horizon anyway, Alta migration aligns with the refresh boundary. You replace cameras and retire the server in one project instead of paying twice over five years.
  • Consolidation with Alta Access (formerly Openpath): If you're already running or planning Avigilon Alta Access for doors, video on the same Alta tenant gives you one operator console and one license stack. Worth weighing in the 5-year TCO model.

Realistic migration timeline

A 30 to 80 camera single-site migration lands inside 6 to 10 weeks once cabling is confirmed. A 200+ camera multi-building campus runs 10 to 14 weeks. We phase camera replacement so the site is never blind.

  1. Week 1: site assessment + path decision: Camera inventory, ACC version audit, server age check, retention policy review, and a frank conversation about why you're considering Alta. Half the customers we audit don't need to migrate. Output: a written stay-vs-migrate recommendation with 5-year TCO for both paths.
  2. Weeks 2 to 3: hardware order + parallel network prep: Alta-compatible cameras ordered. Existing Cat6 runs tested for PoE+ headroom. Switch capacity confirmed. Outbound HTTPS firewall rules drafted (Alta is cloud-only). The old ACC server stays running so retention isn't broken during the cut.
  3. Weeks 3 to 5: phased camera replacement: Cameras replaced in waves so the site is never blind. Old ACC keeps recording legacy cameras while new Alta cameras come online. Operator workflows shift gradually instead of all at once.
  4. Weeks 5 to 6: Alta tenant setup + integrations: Alta cloud tenant configured, multi-site hierarchy mapped, SSO wired (Okta, Azure AD, Google Workspace), event Webhooks pointed at SIEM if applicable. Avigilon Alta Access doors brought into the same tenant if you're consolidating.
  5. Weeks 6 to 8: ACC retention compliance + decommission: The old ACC server runs through your retention compliance window (commonly 30 to 180 days) before decommission. Footage exported to long-term storage if your policy requires it. Server hardware retired or repurposed. Final operator training on Alta delivered.

Biggest delay risk: cabling that doesn't carry 4K plus PoE+ at scale. The audit tests existing runs and switch capacity before scoping the migration.

What carries forward, what gets replaced

Carries forward: Cat6 cabling (if it's clean), PoE+ switches with adequate headroom, identity provider integration (Okta, Azure AD, Google Workspace), HID and standard prox/iCLASS credentials at doors if you're moving to Alta Access in the same project, and your existing retention policy.

Gets replaced: Cameras (ACC cameras don't run native on Alta with full analytics), the on-prem ACC server or HD Video Appliance (decommissioned after the retention compliance window), and any custom ACC integrations without an Alta equivalent. Your operator playbook also gets rewritten, because the Alta UI is meaningfully different from ACC Client.

Sometimes carries forward: Older ACC cameras can stream into Alta via a hybrid bridge in specific scenarios with reduced analytics. Useful as a transition step, not a long-term destination. We model the hybrid path against full migration in the audit when it applies.

Integration with what you already run

Alta plays well with most modern enterprise infrastructure. SAML SSO (Okta, Azure AD, Google Workspace) wires in cleanly, Webhook outputs cover SIEM and SOC pipelines, and the open API supports custom integrations. Avigilon Alta Access on the same tenant unifies video and door events in one operator view.

Where Alta is more constrained than Unity: third-party camera support is limited (Unity tolerates ONVIF cameras with reduced analytics; Alta primarily expects Avigilon Alta-compatible hardware). If you have a working Axis, Hanwha, or Bosch fleet you want to keep, Alta isn't the bridge. Genetec or Milestone are open-platform VMS alternatives we present in the audit when this applies.

For the Motorola Solutions ecosystem (radios, CommandCentral dispatch, ALPR), both Unity and Alta tie in natively. Public-safety and large-enterprise security ops with Motorola in place tend to weigh this heavily.

What Tec-Tel adds vs going direct

Avigilon-direct sales and channel partners with Avigilon-only loyalty have an incentive to move you to Alta. Tec-Tel doesn't. We install Verkada, Avigilon (Unity + Alta), Genetec, Axis, Hanwha, Milestone, and Eagle Eye Networks. If staying on Unity is the right answer, that's what we'll recommend. If Alta makes sense for the multi-site lean-IT shape, we'll scope the migration honestly. If neither fits and Genetec or Milestone is the better unified answer, we'll say that.

Beyond the recommendation, Tec-Tel adds install-side accountability: phased camera replacement so the site is never blind, cabling audit, switch sizing, mounting and weather-sealing, motion-zone tuning, false-positive reduction, operator training, and a written runbook. We're a 15-year nationwide integrator, and one accountable project manager runs your install from the first call through every site, to one spec and one standard.

A note on partner-status language. Tec-Tel installs and integrates Avigilon Unity and Alta. We don't claim a specific Avigilon partner certification on this page. If your contract requires a vendor-certified install, ask in the audit and we'll confirm the credentials we hold or pair the work with a certified partner where required.