Mercury access control migration

Migrate your Mercury estate. Not your infrastructure.

Change the ageing software layer that manages your controllers without automatically ripping out the field hardware you have already paid for.
Mercury access control migration means replacing the management software while retaining compatible HID Mercury controllers, readers and cabling. For qualifying estates, WaveFusion offers a route to browser-based, multi-site management with door decisions kept local at the controller. Compatibility is confirmed per estate, not assumed.
Keep in the field
  • Compatible Mercury controllers and sub-panels
  • Readers and credential hardware
  • Door hardware, I/O boards and cabling
For IT and infrastructure
  • Proprietary / ageing management software
  • Move to browser-based, multi-site management
01
Compatibility first
Controllers qualified before any replacement is assumed.
02
Phased rollout
Site-by-site cutover, not a single big-bang switch.
03
Local decisioning
Door decisions stay at the controller through migration.
04
Device-based licensing
No per-operator-seat charge as teams grow.
The modernisation dilemma

The bottleneck is usually the software — not the controller.

Rip-and-replace is the instinctive vendor answer. For estates built on Mercury infrastructure, it is often unnecessarily expensive, disruptive and risky.
Mercury controllers have been an enterprise standard for over three decades and use an open architecture designed to work with multiple software providers. When leadership wants better reporting, IT flags cybersecurity, or the current platform can no longer integrate, the constraint is almost always the proprietary software sitting on top of sound hardware — not the hardware itself.
01
Vendor lock-in
Proprietary platforms tie hardware and software together, keeping switching costs high.
02
Integration limits
Closed systems resist connecting to video, identity directories and building systems.
03
Replacement waste
Full hardware swaps discard controllers, readers and cabling that still perform.
Compatibility, qualified

Which Mercury controllers can stay?

Support depends on controller generation and firmware. This is an indicative guide — the definitive answer for your estate comes from an assessment, not a blanket claim.
Mercury controller family
Typical role
Migration position
Notes
MP Intelligent Controllers
Current-generation intelligent controllers with an embedded application environment
• Retain and assess
Newest platform; supports edge-based decisions and modern protocols.
LP series
Widely deployed enterprise controllers
• Retain and assess
Broadly supported; confirm firmware. Vendor firmware runway commonly cited through 2028.
EP series
Established estates and mixed installations
• Assess per site
Frequently retained; model and firmware checks determine scope.
Older firmware / mixed hardware
Legacy builds and non-Mercury sub-systems in the same estate
• Review required
May need a non-disruptive firmware update or separate handling for third-party panels.
Indicative positions only. Actual compatibility depends on controller model, firmware version, connected readers and credential formats, network design and existing integrations. Wavestore confirms supported components and any required work as part of a Mercury estate assessment before a migration plan is agreed.
What actually changes

Change the software. Keep the field hardware.

Field hardware can represent the majority of total access-control deployment cost. A software-layer migration targets the part that is holding you back.

Stays in the field

  • Compatible HID Mercury controllers and sub-panels
  • Card readers and existing credential formats
  • Door hardware, I/O boards and interface modules
  • Structured cabling and network infrastructure

Gets modernised

  • Proprietary or ageing management software
  • Per-operator-seat licensing model
  • Isolated, per-site administration
  • Limited integration with video and identity systems
The extent to which hardware is retained depends on the outcome of the compatibility assessment. Some components may require firmware updates or, in specific cases, replacement.
Estate assessment

A migration plan starts with what is already installed.

Before selecting a platform or setting a go-live date, a structured assessment maps the estate and ranks sites by complexity and risk. It is the input that makes the rest of the migration predictable.
  • Inventory controllers, firmware, readers, doors and credentials
  • Confirm compatibility rather than relying on assumption
  • Map current integrations, network topology and data
  • Produce a compatibility matrix and risk-ranked rollout
01
Assess the estate
Document controllers, firmware, readers, credential formats, integrations, network topology and operational dependencies across every site.
02
Plan and design
Define the target state, data migration approach, stakeholder requirements and a per-site rollback procedure before anything is touched.
03
Map integrations
Connect the platform to controllers over the existing IP network, then map access levels, schedules, identity directories and video where required.
04
Pilot and phase
Validate on a low-risk site using a parallel-run model, then cut over door-by-door and site-by-site so no door is left unmanaged.
05
Optimise
Once stable, unlock capabilities the legacy platform could not offer and decommission the old software connection.
Cloud-managed, edge-resilient

Central management convenience. Local door continuity.

Cloud-managed access control does not have to mean cloud-dependent doors.
WaveFusion separates administration and estate-wide visibility from time-critical door decisions. Teams manage the system through the browser, while compatible Mercury controllers continue to make local access decisions — including during a connectivity interruption.
  • Central administration and multi-site visibility through the browser
  • Controller-level access rules and door decisions at the edge
  • Existing IP network reused — no new cabling for management
Management layer
Authorised browser users
Central services
WaveFusion multi-site management
Local decision layer
Compatible Mercury controllers
Controlled environment
Doors, readers and credentials
During a connectivity interruption, local access decisions remain at the controller.
Clear capability status

What is available now — and what comes next.

An honest migration conversation starts with a precise view of today's capability, established Wavestore workflows and the stated product direction.
Available now

WaveFusion access control, video management and data

  • Browser-based management
  • Multi-site access-control oversight
  • Compatible Mercury controllers
  • Local controller decisioning
  • Device-based licensing
  • Fast streaming video
  • Export videoclips
  • View live system health
  • Maps with interactive icons
COMING SOON

Deeper WaveFusion
unification

  • Video verification linked to access events where supported
  • Operator workflows defined by the selected integration
  • Deployment-specific compatibility review
  • De-warping of fisheye cameras
  • HotSpots for easy navigation around your sites
  • Elevator controls
  • Alarm intrusion integration
  • Mobile credentials
  • Visitor management
Product availability, compatibility and roadmap timing should be confirmed with Wavestore for the proposed deployment. Roadmap items are directional and are not a commitment to a specific release date.
For systems integrators
Modernise reporting and control without a rip-and-replace budget.
Protect a working hardware investment while removing the limitations of the current platform.
For IT and infrastructure
Bring access control onto standards you can govern.
Reuse the existing network and integrate with identity directories, with local resilience retained.
For enterpriFor integrators and consultantsse teams
Offer a lower-disruption path from legacy control.
Assess what can remain, define the transition and give clients a clearer lifecycle plan.
When to explore WaveFusion

The right move when the software constrains, but the estate does not.

A Mercury migration is worth assessing when the current platform is limiting operations but wholesale controller replacement is difficult to justify.
Legacy software is approaching end of life
Renewal and support fees keep rising
Sites need consistent central management
Integration with video or identity is blocked
Mercury infrastructure remains serviceable
A phased programme is preferred over big-bang
Start with your estate

Request a Mercury estate assessment.

Share a few details about your current environment and Wavestore can help frame the right compatibility and migration questions for your estate. The public form is deliberately short — deeper technical detail is gathered after the first conversation.
  • An indicative view of which controllers can be retained
  • The main compatibility and migration questions for your sites
  • A sense of a realistic, phased sequence and next steps
Mercury migration FAQ

The first questions, answered.

Every estate is different. These answers set the direction; compatibility and migration details are validated against your proposed deployment.
Your system, your choice

Find out how much of your estate can stay.

Bring your controller inventory, site structure and operational priorities. Wavestore can help you frame the right compatibility and migration questions before any change begins.