What are the limitations of Expedition Migration tool when migrating other vendors firewalls

[Luiz_Saqer]

Hi,

Can any one name the technical limitations of using Expedition tool for migrating to PAN.

Thanks and regards. 

[BPry]

@Luiz_Saqer,

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. 

[Luiz_Saqer]

Hi BPry,

no specific vendor information, if we can summarize as below choices, what could be the best answers

Time consuming

or

Doesn't support NATing

or

Doesn't support Routing

or

Doesn't support App conversions

or

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. 

[IRana]

The limitation are based on Vendor. Below is the brief table which summarizes the supported functionalities.

https://live.paloaltonetworks.com/t5/expedition-articles/expedition-supported-3rd-party-vendor-matri...