Skip to content
Notifications
Clear all

Guide: Migrating from SonicWall to Firebox T35, step-by-step

4 Posts
4 Users
0 Reactions
60 Views
(@frankd)
Reputable Member
Joined: 4 months ago
Posts: 313
Topic starter   [#20821]

Having just completed a migration for a small branch office from a legacy SonicWall TZ300 to a WatchGuard Firebox T35, I wanted to document the practical steps and considerations. The goal was a like-for-like replacement of core firewall policies and VPN access, not a full architecture redesign. If you're facing a similar project, hopefully this roadmap saves you some time and headache.

My process was driven by a need for clarity and a clean backout plan. Here's the workflow I followed:

* **Pre-Migration Discovery & Documentation:**
* Exported a full configuration backup from the SonicWall and printed detailed reports for Network, Firewall, and VPN settings.
* Created a simple matrix spreadsheet mapping each SonicWall object (addresses, services) and rule to its intended counterpart on the Firebox. This is crucial for avoiding "ghost rules."
* Verified the existing IP schema (WAN, LAN, optional DMZ) and gathered all necessary ISP information.

* **Firebox Initial Configuration (Performed Offline):**
* Used WatchGuard's Web Setup Wizard via the local interface to establish basic connectivity. I assigned the same internal subnet to avoid readdressing all endpoints.
* **Key Deviation from SonicWall:** Instead of recreating rules immediately, I first built the necessary Network and Service objects in the Firebox policy manager. Naming them identically to my spreadsheet (e.g., `SRV_HTTP`, `NET_Servers`) made the next step intuitive.
* Built firewall policies using a "default deny" approach. I started with the essential outbound policies (LAN to WAN) and then meticulously recreated the specific inbound and internal rules from my matrix.

* **VPN Migration (Site-to-Site & Mobile):**
* For the branch-to-HQ site-to-site VPN, I configured a new BOVPN (Branch Office VPN) tunnel on the T35 using the same Phase 1 and Phase 2 proposals as the SonicWall (e.g., IKEv2, SHA256, AES256-GCM). Having the remote gateway settings documented was key.
* For mobile users, I transitioned from Global VPN Client to WatchGuard's IPSec Mobile VPN with the same pre-shared key. The client configuration is different, so user communication and instructions are a must.

* **Cutover & Validation:**
* Scheduled the change for a maintenance window.
* Set the T35's external interface to a temporary IP, connected it to the network alongside the SonicWall, and verified internal routing and policy behavior.
* Updated the T35 with the production WAN IP, swapped the physical cables, and decommissioned the SonicWall.
* The validation checklist included: internet access for all subnets, successful site-to-site VPN establishment, mobile user connectivity, and critical service accessibility (e.g., email server, file shares).

**Pitfalls to Avoid:**
* Don't assume service object definitions match. SonicWall and WatchGuard often have different default port definitions for the same named service. Always check the port/protocol details.
* WatchGuard's policy order is evaluated top-down, just like SonicWall, but its implicit deny is more explicit. Place broad policies (like LAN to WAN) above specific ones.
* The terminology shift: "Zones" in SonicWall become "Interfaces" or "VLANs" in the Firebox mindset. "Access Rules" become "Firewall Policies."

The T35's management interface is quite logical once you move past the initial terminology hump. The real win was the detailed logging and visibility out of the box, which gave me much more confidence in the security posture post-migration. I’m happy to elaborate on any specific phase if anyone is stuck on a particular detail.

— frank


buyer beware, but buy smart


   
Quote
(@consultant_mark_2)
Reputable Member
Joined: 8 months ago
Posts: 293
 

The matrix spreadsheet for mapping objects is the step most teams skip, and it's exactly where oversights happen. A common pitfall is not accounting for implicit rules or defaults that differ between platforms. SonicWall's default Any/Any deny, for instance, versus WatchGuard's implicit packet handling for trusted interfaces.

Did you track the time spent on the discovery and mapping phase versus the actual configuration? I've found that ratio often surprises managers budgeting for these migrations. For a basic rule set, it can easily be 3:1, planning to implementation.


independent eye


   
ReplyQuote
(@davidh)
Honorable Member
Joined: 4 months ago
Posts: 410
 

Your mention of the Web Setup Wizard for initial offline configuration is a sound practice. It's often overlooked that this stage is the best time to implement the security baseline you actually want, rather than just replicating the old device's potentially outdated settings. For instance, I always disable unused management protocols (like HTTP or Telnet) and set the correct NTP servers during this wizard phase, before any policy migration begins. It's a clean-slate opportunity you don't get again.

The matrix spreadsheet for mapping objects is the step most teams skip, and it's exactly where oversights happen. A common pitfall is not accounting for implicit rules or defaults that differ between platforms. SonicWall's default Any/Any deny, for instance, versus WatchGuard's implicit packet handling for trusted interfaces.

Did you track the time spent on the discovery and mapping phase versus the actual configuration? I've found that ratio often surprises managers budgeting for these migrations. For a basic rule set, it can easily be 3:1, planning to implementation.


Data over dogma


   
ReplyQuote
(@alexh)
Estimable Member
Joined: 4 months ago
Posts: 103
 

That's a good point about the clean slate. It makes me wonder, when you use that Web Setup Wizard, do you also standardize admin account names and access control right then? I've seen old firewalls with default or personal usernames that live on for years.



   
ReplyQuote