Connect. Secure. Manage.
Meraki Network Split and Combine
Plan supported Meraki network restructuring, checking the effect on device settings, history and integrated services before changing dashboard organisation.
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 network split and combine work changes how devices are grouped in Dashboard. We check the effect on settings, ownership and support before moving them. The grouping should match how the sites are run. This is distinct from changing physical links, but it can still affect the service even when no cables are moved.
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 outcome rather than start with the button
A request to combine networks might mean grouping switching, wireless and security devices for one site. It might instead mean merging two wireless settings, consolidating buildings or transferring assets between companies. Those are different projects. We establish the intended operational result and identify the supported workflow that actually produces it.
Similarly, splitting a combined dashboard network does not on its own create separate security zones or isolate users. Routing, VLANs, firewall policy and identity remain technical controls that require their own design. We make this distinction clear so a cleaner admin view is not mistaken for a completed segmentation project or a change in the underlying commercial ownership of 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
Inspect configuration at every relevant level
We review organisation, network and device-level settings, including templates, firmware targets, access permissions and relevant integrations. Each proposed move is mapped to the settings that need to remain consistent. The review also identifies setup that is deliberately different between sites, such as local addressing or provider handoffs, rather than forcing everything into one standard.
A physical port map is useful even for an admin reorganisation. It connects switch interfaces to real endpoints and upstream equipment, making it easier to assess the effect of a lost or changed port setting. We also record wireless names, authentication dependencies and security-appliance interfaces where those products are included. The inventory becomes the basis for verification after the change.
A useful starting point
Not sure where to start?
Bring the requirement. We will help you define the engineering work.
Choose whether to combine, split or rebuild
Combined networks can provide a coordinated dashboard view for supported product types, but eligibility and interactions with templates need checking. Other reorganisations may require moving devices to a newly prepared network. We compare the available methods and document which setup is expected to remain, which will follow the destination and which needs manual recreation.
The simplest-looking method is not necessarily the lowest-risk one. A new destination with carefully staged settings may be clearer than modifying a heavily customised production container. Conversely, rebuilding a network solely to change its presentation can introduce unnecessary work. We recommend the approach that meets the operating need with a realistic recovery route and the least avoidable disruption.
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 the destination and the maintenance window
Where a new network is required, we establish its setup, naming, access model and intended firmware before moving equipment. We check that connected services will recognise the resulting arrangement. Monitoring systems, automation and support documentation can refer to network identifiers rather than visible names, so their dependencies need to be reviewed clearly.
The rollout plan identifies the expected effect on each device group and the order in which changes occur. Staff should know whether the work is purely admin or could interrupt network access. We agree a maintenance window where appropriate, retain necessary access and define the point at which the team would stop rather than continue through an unexpected setup difference.
Compare actual behaviour with the original service
After the split or combination, we check devices against the recorded inventory and check the relevant setup. Tests include management access, client network access, authentication, permitted traffic and alert routing. For switching, we inspect representative ports and uplinks; for wireless, we check the SSIDs and client experience rather than relying on the access points appearing online.
The comparison should also cover the new operational boundaries. Administrators intended to support only one part of the estate should receive the right access, and the helpdesk should be able to identify the correct network from the site information it receives. We test these everyday tasks because admin restructuring is usually justified by improving operations, not by changing a dashboard label alone.
Keep the resulting structure understandable
The final records explain the relationship between physical sites, dashboard networks and the people responsible for them. We update diagrams, monitoring references and change procedures, then identify any old containers or access arrangements that can be retired. Historical information is retained where required through an agreed method rather than assuming it will always remain available in the same place.
This service can sit within a wider Meraki platform migration or be a focused housekeeping project. MCI can assess the current structure and provide a supported change plan for your engineers, or deliver the reorganisation with acceptance testing. The proposal states exactly what will be reorganised and avoids implying that admin grouping alone changes network security, availability or licence ownership.
Technical references
- Combined dashboard networks — Cisco / Cisco Meraki
- Network portability — 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.