Connect. Secure. Manage.
Catalyst Cloud Monitoring Migration
Move eligible Catalyst switches from retired Cloud Monitoring to current cloud management, including software checks and cleanup of obsolete configuration.
Devices supported
across the UK
Client locations
supported
Traffic handled
at peak time
Average
response time
Average response is not a resolution time or a contractual guarantee. Support scope and response commitments are agreed for each engagement.
Catalyst Cloud Monitoring migration helps sites move on from Cisco’s legacy monitoring service, which ended on 31 March 2026. We assess eligible switches, plan a supported management approach and remove old settings where needed. Loss of monitoring does not by itself mean that traffic has stopped. The migration follows the switching features and control your network still needs.
Dashboard clarity
Structure organisations, networks and permissions around real operational ownership.
Consistent sites
Use repeatable standards without ignoring the differences between locations.
Practical operations
Keep cloud management connected to physical links, users and business services.
Identify the legacy deployment accurately
The initial inventory records which switches were onboarded to legacy Cloud Monitoring, their software versions and the dashboard organisations involved. We check whether each device has already transitioned, remains associated with an obsolete workflow or has been removed without setup cleanup. A disconnected dashboard entry does not prove the switch itself has failed. The local operating state and user services need separate verification.
The review also identifies ownership. An older onboarding may have been performed by a former provider or a different internal team. We establish who controls dashboard access and who is authorised to change the switch setup. The migration cannot be planned safely from an inventory list alone if the customer lacks a working admin or recovery route to the equipment.
Standards & partnerships
Confidence in the team behind your network.
Cisco Partner
Cisco Meraki
Cyber Essentials
Cyber Essentials PlusMCI Network Services is operated by Proxar Ltd. Certifications apply to the certified legal entity and the scope of its certificates. View accreditation information
Choose a supported destination
For eligible devices, cloud management with device setup can provide a route forward while preserving the intended local setup model. Fully cloud-configured operation is a different choice and requires its own feature assessment. We compare these options against the hardware, software, licensing and support needs rather than assume every switch should move to the same mode.
Our Catalyst Device Configuration service covers the device-led model in detail. The migration assessment identifies unsupported devices or required software changes before scheduling work. Where replacement or another management approach is more appropriate, that is stated openly. A lifecycle project should not force a technically unsuitable conversion merely to restore a green status in the dashboard.
A useful starting point
Not sure where to start?
Bring the requirement. We will help you define the engineering work.
Review old configuration before cleanup
Cisco’s retirement guidance distinguishes devices migrated before the service ended from those needing manual cleanup afterwards. We inspect the relevant setup and compare it with the documented legacy integration. Removal must be precise: accounts, access settings or services used by other management tools should not be deleted simply because their names look familiar. We preserve the original setup evidence and record each intended change.
Cleanup is coordinated with the new onboarding sequence. Some settings may need to be removed or adjusted before the supported integration can be established; other dependencies must remain until validation is complete. The rollout plan defines that order and the recovery method. We do not provide a universal deletion script for an estate whose previous setup and current management dependencies have not been inspected.
Different environments. The same care.
Built around the work
your network supports.
Finance, banking and the wider private sector. We start with the systems and people that depend on your connections.
Finance & banking
Market-data paths, routing and provider coordination on clients’ behalf.
Financial-market services ↗Offices & multi-site teams
Reliable access between people, workplaces and business applications.
Office network design ↗Data centres & cloud
Network boundaries, workload connections and operational ownership.
Data centre networks ↗Plan software and operational impact
The target model may require a software upgrade, entitlement check or other preparation. We assess the effect on current routing, authentication and connected devices, together with any stack or chassis considerations. Maintenance windows should reflect the actual upgrade and recovery process rather than the apparent simplicity of adding a device to a dashboard network.
For business-critical sites, we agree which services will be tested and who can approve the result. A pilot checks the procedure on representative equipment before broader rollout. The plan includes stopping conditions for unexpected setup differences, unavailable features or failed management network access. A migration that requires a redesign is returned for approval rather than improvised during the change window.
Validate the replacement service
After onboarding, we confirm the correct organisation, device identity and setup source. The requested visibility and diagnostic tools are checked, along with local administration and any current automation that should remain in use. We also check representative user traffic so that improved dashboard visibility does not conceal a regression in the network itself.
Historical monitoring information and the new service should not be assumed to form an uninterrupted record. We check what evidence remains available and what needs to be retained separately for operations or audit. The customer receives an accurate account of the transition rather than a promise that every historical field, graph and event has been carried into the replacement management model.
Close the lifecycle task properly
The completed handover records migrated devices, outstanding exceptions, obsolete settings removed and the support procedures now in use. Monitoring and alert recipients are reviewed so that old entries do not continue producing misleading incidents. The broader Meraki platform migration service can coordinate related ownership or organisation changes. This retirement applies specifically to the legacy Catalyst switching service; other Cisco cloud-visibility offerings are assessed on their own current documentation and must not be declared retired by association.
Technical references
- End of service for legacy Catalyst switch cloud monitoring — Cisco / Cisco Meraki
- Enable cloud management with device configuration — Cisco / Cisco Meraki
Talk to a specialist
What does your network need next?
Tell us what you are planning, changing or trying to improve. We will help define a practical next step and the engineering scope.
+44 203 196 6566Choose option 1
sales@proxar.co.ukUK-wide service.
Most of our engineers are based in Kent, with a focus on London, Sussex, Essex and Berkshire.
Existing customers should use their agreed support and escalation channels. This form is for service enquiries, not a monitored emergency ticket.
Tell us what you need.
A short outline is enough. Please do not include passwords or sensitive network details.
Thank you. Your enquiry has been submitted.
Please check your name, email and message, then try again.
Your form session expired. Please try again.
Please wait a minute before sending another enquiry.
We could not submit your enquiry. Please call or email us instead.