For organizations running Hanwha Wisenet WAVE, the cameras are probably the last thing on the list to replace. They're already installed, doing their job, and swapping them out across multiple buildings or campuses rarely pencils out. Run the math a few years forward, though, and the decision often flips: per-channel licensing keeps climbing, on-prem servers age toward a refresh, and the platform underneath the cameras becomes the more expensive problem.

Coram is an AI native unified physical security platform that connects to your existing ONVIF cameras and replaces the WAVE or SSM management layer. Recording and AI processing move to Coram Point, an on-prem appliance that sits where your NVR does today, while management, search, alerting, and remote access run in the cloud. Whether you're adding another site, replacing WAVE with an alternative, or looking for a simpler way to manage video across multiple locations, the migration doesn't necessarily mean starting from scratch. If your Wisenet cameras support ONVIF, they stay part of the deployment while WAVE or SSM gets replaced. The cameras usually aren't the problem. The management layer sitting on top of them is.

What Actually Carries Over from Your Hanwha Wisenet Stack

A standard WAVE or Wisenet SSM deployment includes Wisenet IP cameras, Wisenet NVRs or recording servers, WAVE Sync for remote access, and the WAVE or SSM platform managing video across your sites. During a migration, each of these components gets evaluated separately, because they don't all move forward the same way.

Two things carry over largely intact: the cameras, if they support ONVIF, and everything around them. Coram can adopt ONVIF-compliant Wisenet cameras without a hardware swap. The same goes for cabling, PoE switches, and the underlying network infrastructure — none of it needs to change.

The video management layer is what actually changes. The WAVE or SSM server, the Wisenet NVRs, and per-channel perpetual licensing all go away, replaced by Coram Point for local recording and AI and a subscription license per camera feed. You still have hardware on site. What you no longer have is a VMS server your team is responsible for sizing, patching, and upgrading.

ONVIF preserves core camera functionality, but not everything. On-camera AI analytics and WAVE-specific integrations don't automatically transfer to another VMS. Before planning further, check a few things:

• Whether your existing Wisenet cameras support ONVIF.
• The condition of your network and available bandwidth.
• Whether your WAVE server or Wisenet NVRs are already due for refresh.
• Any SSO or identity integrations that need to be recreated.
• Your WAVE maintenance and licensing renewal dates, so you can align the migration with existing contracts.

Wisenet WAVE vs. Coram: Quick Comparison

The table below breaks down the core differences between Wisenet WAVE and Coram, dimension by dimension.

The Migration Path, Step by Step

Every Wisenet deployment looks a little different, but the migration process follows the same pattern: understand your current environment, validate compatibility, and move in phases so the current system keeps running while the new one comes online.

1. Audit Your Existing Deployment

Before planning the migration, take stock of what you have today. Document your Wisenet camera models, firmware versions, ONVIF support, WAVE or SSM servers, Wisenet NVRs, active channel licenses, and maintenance renewal dates. That inventory is the starting point for everything else, and it's where compatibility gaps tend to surface before they turn into delays.

2. Identify What's Reusable

The next step is figuring out what actually needs to change. Check which Wisenet cameras can connect to Coram over ONVIF, and identify any locations relying on WAVE-specific features or camera-based analytics. That way, you can plan around those dependencies instead of discovering them halfway through the migration.

3. Parallel-Run, Don't Rip-and-Replace

Instead of migrating your entire deployment at once, start with a Coram Point at one site and a small group of ONVIF-compatible cameras, and run Coram alongside WAVE. Use this phase to verify recording, playback, remote access, user permissions, and any workflows your operators rely on every day. Once everything works as expected, expand the rollout with greater confidence.

4. Phased Cutover

After the pilot has been validated, migrate one site, building, or campus at a time. A phased approach keeps the rest of your environment operational while giving your team room to resolve issues before moving to the next stage. As each phase is completed, the corresponding WAVE or SSM servers and Wisenet NVRs can be retired.

5. Decommission, License/Maintenance Wind-Down

Lastly, retire the remaining WAVE infrastructure and align the cutover with your maintenance or license renewal dates wherever possible. This helps you avoid unnecessary overlap in licensing costs and ensures you're not maintaining infrastructure you no longer need.

Where Coram Fits

If you've invested heavily in Hanwha Wisenet cameras, replacing them just to switch VMS platforms doesn't hold up financially. Coram is built around the opposite idea: keep the camera investment where it makes sense, replace the management layer where it doesn't.

That gives IT teams a path to cloud management, AI search across every camera, and access control on the same platform without treating the migration as a full infrastructure refresh. Because video and Access Control run in one system, a door forced open or a tailgating alert surfaces next to the footage that explains it, instead of leaving your team to reconcile two tools mid-investigation. Coram is SOC 2 Type II audited and HIPAA compliant, which matters if your organization has compliance requirements riding on the platform. It also holds a 4.9/5 rating on G2, with particularly strong marks for ease of use and ease of admin — relevant if a lean IT team is the one who'll be running it day to day.

How to Decide If Now Is the Right Time to Migrate

There's rarely a perfect time to migrate, but there are clear signals it's worth evaluating your options. If your current WAVE environment is starting to create operational, financial, or administrative challenges, the following scenarios can help you decide whether now is the right time to start planning a move. It may be the right time to migrate if:

• Your Wisenet NVRs or WAVE servers are due for replacement, and you're deciding whether to invest in new on-prem infrastructure or move to a cloud-managed platform.
• You're approaching a WAVE end-of-life milestone or major version upgrade, making it a natural point to review long-term platform costs instead of upgrading by default.
• Managing multiple sites remotely has become increasingly time-consuming, especially as users, locations, or camera counts continue to grow.
• You're weighing perpetual per-channel licenses plus ongoing maintenance against a subscription model, and want the five-year total rather than the next purchase order.
• Your organization is rolling out SSO or identity management across business applications, and you want your physical security platform to align with the same authentication strategy.
• Your security team wants cross-camera AI search and alerts, but your current workflows rely heavily on camera-specific configurations or separate tools.

Note: If you're still under a WAVE maintenance contract, use that time to prepare. Confirm ONVIF compatibility, review your camera inventory, and build a phased migration plan so you're ready to transition when your renewal cycle makes it financially feasible.

What's Next

A migration plan is only as good as the assumptions behind it. Before comparing platforms, confirm which Wisenet cameras support ONVIF and review your WAVE maintenance timeline. Those two inputs often determine not just how you'll migrate, but whether the timing makes financial and operational sense.

To validate those assumptions, book a demo with Coram for a migration assessment and map out the most practical path forward.