01
FortiGate migration
Existing rules, objects, NAT, VPN, routing, dependencies, and public services are translated into a controlled migration plan.
Fortinet consulting and engineering
Fortinet environments designed as systems—not isolated appliances.
JMB plans, migrates, repairs, and standardizes FortiGate, FortiSwitch, FortiAP, FortiLink, VPN, SD-WAN, and segmented multi-site environments with the operational consequences in view.
Request an IT leadership reviewArchitecture before configuration
A firewall is only one decision inside the network.
Reliable Fortinet deployments require addressing, VLANs, switching, wireless, routing, internet failover, authentication, security policy, management access, logging, licensing, documentation, and recovery to agree with one another.
Jaen’s project experience includes coordinated Fortinet rollouts with 400-series switching, dozens of managed access points, multi-building fiber, remote warehouses, redundant internet, and production cutovers delivered under real operational constraints.
What the work covers
A practical path from risk to a supportable environment.
02
FortiSwitch & FortiLink
Switching, trunks, VLANs, uplinks, PoE requirements, management, and resilient topology are designed as part of the firewall environment.
03
FortiAP wireless
Corporate, guest, voice, device, and operational wireless networks receive deliberate coverage, segmentation, policy, and internet paths.
04
SD-WAN & resilient internet
Multiple circuits, health checks, preferred paths, failover behavior, and site dependencies are tested instead of merely configured.
05
VPN & multi-site connectivity
Site-to-site and remote-access designs account for routing, identity, segmentation, overlapping networks, and business application flow.
06
Standardization & remediation
Existing environments are documented, corrected, templated, and prepared for consistent support across locations.
When to call
The Fortinet stack exists, but no one trusts the whole design.
- Policies accumulated without a documented security model
- FortiLink, VLAN, or routing changes regularly create outages
- Failover is configured but has never been proven under load
- Sites use inconsistent naming, addressing, firmware, or administrative access
- A SonicWall, Cisco, Ubiquiti, or legacy firewall migration needs senior ownership
Common questions
Straight answers before the first call.
Can JMB take over an existing Fortinet environment?
Yes. The first step is establishing administrative ownership, configuration backups, licensing, topology, firmware, critical services, and a safe change process.
Can you migrate from another firewall platform?
Yes. Experience includes migrations from SonicWall and other platforms, with attention to NAT, VPN, routing, public services, identity, and cutover risk.
Can you work through another IT provider?
Yes. JMB can provide senior engineering directly or work within a clearly defined co-managed or subcontracted engagement. Attribution and client ownership remain transparent.
Do you sell hardware?
Hardware sourcing can be coordinated when appropriate, but the engagement begins with requirements and architecture—not a predetermined appliance sale.
Direct access. Senior judgment.
Make the Fortinet stack predictable before the next cutover or outage.
Bring the diagram, configuration, failure pattern, or migration objective. JMB will start by identifying the decisions that carry the most risk.