Do you have a specific vendor that you are attempting to migrate, or just the overall downfalls of the migration tool? The number one downside of migrating a configuration is that it isn't going to be app-id based, nor will the policies really be optimized for PAN. I always think it's far better to simply re-build the configuration with PAN specific statements instead. Essentially, I find it better to simply optimize the rulebase from the getgo instead of getting everything working and attempt to optimize the rulebase when it's in active production use.
If you have a specific vendor in mind I would also recommend telling us what vendor you want to migrate from. Some configs the migration tool does a little bit better than others.
no specific vendor information, if we can summarize as below choices, what could be the best answers
Doesn't support NATing
Doesn't support Routing
Doesn't support App conversions
Doesn't support VPN configurations
In my opinion, i think its Doesn't support VPN configuration such as IKE profiles.
Waiting for your feedback.
Thanks and regards.
The limitation are based on Vendor. Below is the brief table which summarizes the supported functionalities.
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!