Connect. Secure. Manage.
Fortinet Network Integration
Support defined integration or migration work between Fortinet and Cisco or Meraki environments, with compatibility and operational ownership agreed first.
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.
Fortinet network integration helps you retain a defined Fortinet role while connecting it to a Cisco or Meraki-led estate. MCI assesses the shared boundary, the applications crossing it and the responsibilities needed to operate it safely. The work can support an inherited branch, an existing security platform or a phased migration where immediate replacement would add unnecessary cost or disruption.
The scope depends on the actual products and functions in use. A Fortinet gateway at an internet edge is not the same integration problem as a wider branch environment. We establish that distinction before making assumptions about what the surrounding network must provide.
A clear requirement
Turn the business need into a practical network scope with visible dependencies.
A controlled delivery
Plan implementation, testing and rollback before production changes begin.
A supportable result
Leave useful records, ownership and escalation routes behind.
Decide what is being retained and why
We review the business reason for coexistence, the equipment involved and the planned lifetime of the arrangement. A permanent specialist platform needs a sustainable operating model; a temporary migration boundary needs a clear exit plan.
Existing licensing, software and support arrangements also matter. Retention should not be justified solely because a device is currently passing traffic if the intended role cannot be maintained appropriately.
The result is a defined integration objective. That might be connecting a retained site, preserving a security function or moving selected services while other parts of the environment remain unchanged.
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
Understand the traffic and policy handoff
We identify addressing, segmentation, route ownership and the authorised application paths. Where translation or tunnels are involved, the design records how the destination is represented on each side.
The integration must preserve relevant security boundaries. A new route should not become an accidental bypass around controls that the existing design relies on.
For branch connections, the operating behaviour of each platform is assessed separately. Features described using similar SD-WAN terminology should not be assumed to form one shared proprietary control system across vendors.
A useful starting point
Not sure where to start?
Bring the requirement. We will help you define the engineering work.
Assess the exact interoperability requirement
A standards-based connection can be a practical way to join systems, but the supported configuration still needs checking. We review the actual platform versions and the features required at the boundary.
For VPN connections, third-party VPN interoperability provides a focused service around peer settings, routing and recovery tests. A tunnel that establishes successfully is only one part of the application path.
Where the intended combination is uncertain or business-critical, a limited test environment may be appropriate before production work. The test should target the uncertain behaviour, not become an elaborate demonstration of features unrelated to the decision.
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 the change around branch operations
A branch may have local applications, payment services, telephony or third-party connections that are not obvious from a central diagram. We establish representative tests and local contacts before changing the shared boundary.
Implementation includes preparation for remote access loss and a clear recovery decision. A change to the very connection used for administration needs particular attention to how work can continue if the expected path disappears.
The plan also identifies which supplier changes each system. Coordinated activity avoids a situation where the Cisco or Meraki side is ready but the retained platform’s owner has not approved the corresponding work.
Document the permanent or temporary arrangement
The handover explains what remains on Fortinet, what is handled by Cisco or Meraki and how traffic passes between them. Temporary settings have owners and review points rather than becoming undocumented exceptions.
Monitoring and escalation should reflect the whole connection. When a user reports a problem, the teams need a practical way to establish whether the issue lies before, at or beyond the shared boundary.
Describe your estate and the reason for integration through our contact page. MCI’s Cisco and Meraki network services can then be aligned with the retained Fortinet function without presenting every platform as interchangeable.
Fortinet integration questions
Can you retain a Fortinet firewall during a Cisco refresh?
That can be appropriate where the platform and design meet the requirement. We review the connection, routing and policy dependencies before confirming the scope. A retained firewall should be an informed design choice, not an unexplained exception.
Can different SD-WAN products become one system?
Do not assume that proprietary management or overlay functions interoperate simply because both products use the SD-WAN label. We assess the supported boundary and may use a defined routed or VPN connection where appropriate, rather than promise shared control features.
Will you migrate all Fortinet settings to Meraki?
A migration requires a functional assessment, not a direct configuration translation. Required features, licences and operating differences must be checked. Migration to Meraki covers the wider decision and transition process.
Can you investigate an existing mixed-vendor fault?
Yes, within an agreed scope and access arrangement. Evidence from both sides is important. We work with the relevant owner and identify any visibility limits instead of treating an incomplete view as proof that the other platform is responsible.
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.