Connect. Secure. Manage.
Meraki Campus Fabric Migration
Assess a staged migration from traditional campus switching to a supported Meraki-managed fabric, including pilot validation and rollback boundaries.
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.
Meraki campus fabric migration introduces a supported cloud-managed Cisco fabric without losing control of the existing services that users rely on. MCI Network Services plans the transition from discovery and pilot through staged cutover and operational handover. We focus on gateway changes, authentication, external routing and the temporary connections between old and new networks. The objective is a defined production state, not simply completing a deployment workflow while leaving important applications dependent on undocumented exceptions.
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.
Establish the approved destination and starting state
A migration should follow an agreed design and readiness assessment. We confirm the intended fabric roles, supported platforms, segmentation model and external handoffs before creating the cutover plan. The current network is recorded with enough detail to understand where users connect and how their applications are reached. Unknown dependencies are treated as discovery work, not as surprises to resolve during the outage window.
We identify which configuration and service properties must remain stable. Addressing, gateway identity and authentication behaviour can affect endpoints differently. Some changes may be necessary for the new architecture, while others can be deferred. Separating those decisions reduces the number of variables introduced at once and makes it easier to diagnose a problem if a migrated group behaves differently from the pilot.
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
Design coexistence rather than assume a single cutover
Most working campuses cannot be moved as one undifferentiated block. We define the relationship between retained access areas and the new fabric, including temporary routing or Layer 2 connections where supported. Each coexistence path has a purpose, an owner and a removal condition. The transition should not create loops, duplicate gateway ownership or unintended access between security domains.
External services may need changes before the first endpoint moves. We coordinate firewall, WAN and shared-service updates with their owners and confirm the return paths. Where both old and new networks advertise related destinations, the plan states which path should be preferred at each stage. This avoids a migration that appears successful locally while traffic elsewhere follows an obsolete or asymmetric route.
A useful starting point
Not sure where to start?
Bring the requirement. We will help you define the engineering work.
Pilot the difficult dependencies
A useful pilot includes representative endpoint types and application flows, not only a small set of managed laptops. We test authentication, addressing, shared services and relevant policy decisions. Where wireless or specialist devices are involved, their specific behaviours are included. The pilot’s hardware, software and configuration conditions are recorded so later waves can be compared against a known baseline.
The pilot also exercises the operating process. Engineers should be able to locate an endpoint, interpret the relevant forwarding state and collect evidence when a test fails. If troubleshooting depends on undocumented knowledge held by one person, the migration is not ready to scale. We use the findings to refine documentation, monitoring and escalation before moving a larger population.
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 ↗Prepare each production wave with clear decision points
The wave plan identifies the affected users, physical connections, configuration changes and test owners. We capture the pre-change state and confirm management access, including a recovery path where practical. Communications explain the expected interruption and the route for reporting problems. The team should know when to continue, pause or invoke the agreed recovery procedure.
Rollback is assessed for the actual stage of migration. Returning a cable may not reverse an addressing change, policy update or external route advertisement. We document the sequence required to restore the previous service and the point beyond which a forward repair may be more appropriate. Those decisions are agreed before the window rather than improvised under pressure after several dependent changes have been made.
Validate service and isolation after the move
Acceptance combines network observations with representative application tests. We check endpoint reachability, expected segmentation, external paths and operational visibility. Where the design claims resilience, agreed fault tests are performed safely or recorded as outstanding. A fabric deployment status marked complete is not a substitute for proving that the business services work under the intended policy.
We also watch the transition period for symptoms that may not appear immediately. Scheduled jobs, occasional specialist devices and applications used only by certain teams can reveal missed dependencies. The plan defines how those reports are investigated and how long enhanced observation continues. Any workaround receives a documented owner and resolution path rather than quietly becoming part of the permanent design.
Remove transition dependencies and hand over
Completion includes retiring obsolete gateways, links, routes and access permissions after their removal is approved. We update the service diagrams and reconcile the final configuration with the intended design. The receiving team gets the migration record, known limitations and procedures for routine changes, software maintenance and incident escalation.
MCI can deliver the migration or support your internal engineers during defined stages. Our Meraki campus fabric operations service can provide an ongoing operating model where required. The project closes when the agreed services, records and responsibilities are accepted, not when the last device has merely appeared in dashboard.
Technical references
- EVPN multihoming in a cloud-managed fabric — Cisco / Cisco Meraki
- Cloud-managed EVPN fabric technical guide — 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.