The internal tools did help parse the Sonicwall configuration, however since there is a significant technology/style difference between PAN and Sonciwall, you'll need to do a considerable amount of validation to ensure everything migrated and also a comprehensive SIT / UAT plan. Going from SonicWall's VPN clients to GlobalProtect can also be tricky since they are configured differently on their respective platforms.
I've done several the old fashioned way, exporting everything to ms excel worksheets and then converting to txt and modifing to cli scripts etc... I was going to test a old migration using the forti converter and then import into expedition. I just need to make sure that the forti converter preserves all of the static routes and objects correctly. The most important part of these sonicwall migrations is to "validate" everything which can be time consuming. Clients who did't want to perform that detailed comparrision failed (had major issues and had to roll back) their migrations.
So here is the latest scoop. My RE onsite was able to have one of the scripting ninjas somewhere in the deep dark reaches of Palo Corporate and was able to generate csv files containing different information groupings like address, services, interfaces... etc etc etc. I was able to import these into Expedition just fine. That is as far as i have gotten so far. Hopefully that update to Expedition to add this functionality isn't far off!
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!