For  object-group PING , if you filter address group object contains “PING” you should find it    expedition only support remap to layer 3 interface , for vlan interface you will need to recreate the interface .    ... View more

So if you need to keep those interfaces, you can click "remap interface" to remap them to PAN-OS naming convention.  as long the interface name does not duplicate between three ciscoasa configs , you are able to merge without a problem.    ... View more

Hi @mss.support , 1 you will zip all three asa config into a zip file  2. upload your asazip file in the import -> cisco -> upload multiple files  3. Upload your PAN-OS config under Import -> Palo Alto -> upload a single file. upload your base config here . it can be either firewal or panorma config depends where your policy going to be managed at.  4.  You will need to fix all the red number showing in the dashboard for each of the cisco asa file , you can switch the context located at the right bottom corner to get to each of the ciscoasa config and make modification for each of the ciscoasa config  5.  Since you are merging three ciscoasa firewall into one palo alto firewall, you will need to review which network interfaces you would like to migrate to the palo alto network, if there are not many interfaces, you can build the interfaces and zone on the firewall directly, please make sure the zone name needs to match the zone name in the policy.  If there are a lot of interfaces you would like to keep from ciscoasa config, you will need to fix the interface configurations under each cisocasa config, make sure you rename each of the interfaces to PAN-OS naming conventions and each of the configs do not have duplicated interface names, also you might only need one VR depends on your use case. When you ready to merge the source and base configs, you can go to "Export" -> " Mapping" -> if you need to merge the network interface, you will first start with ciscoasa1 config, check all checkbox under "network", drag and drop them to "network" section onto the right side base config (If you already built interfaces and zone on the firewall, you do not need to merge the network configuration ) for policy and objects, under vsys1, drag and drop them to the right side vsys 1, continue for ciscoasa2 and ciscoas3      6. Once you finished drag and drop, you should see configuration from 3 ciscoasa moved to base config as below :   7. You can then click on "Merge" to merge the config  8. Once the merge is done, you can then click "Generate XML and set output" to download the merged xml file.  9 You could then load the config using "load config partial" or if you have direct access between expedition and firewall, you can then do an API calls from expedition to firewall to push the configuration over.                    ... View more

Hi @mss.support Yes, you could import all three of the Cisco ASA configs and merge them to a single base config in one project.  If you already make three projects , you could export merged config and do load config partial command to load objects and policy one by one in the target firewall ... View more

@PabloStanic  which link you refer to?  To find the serial# of your firewall, you will log in to your firewall GUI and under Dashboard, you should see the serial#.  For Adding Device to the Expedition, you will go to devices -> click on the "+" on the right upper corner to add the new device, fill in all the fields, and optionally, you can fill in the serial# of HA if you have two firewalls in cluster mode.          ... View more