Checkpoint migration to PA-820

Showing results for 
Show  only  | Search instead for 
Did you mean: 
Please sign in to see details of an important advisory in our Customer Advisories area.

Checkpoint migration to PA-820

L0 Member


Im trying to migrate a CheckPoint to PA-820, but am having issues importing the CheckPoint json config files.  I get the error:

JSON error - Syntax error, malformed JSON


There are 439 security rules, 36 NAT rules


I have access to the new PA-820, but I don't have access to the CheckPoint - I request info, and hopefully it is executed and sent back to me as requested.

I have Expedition v1.1.13 running on VMWorkstation.

I've added the PA-820 device and seems to be linked sufficiently. 

I've imported a sample palo alto config into a test project, and see the Project Statistics sufficiently.


I requested the CheckPoint admin run these commands, and send me the files:

For the Security Rules:

mgmt_cli show access-rulebase name "yourRulebaseName" details-level "full" use-object-dictionary true --format json


For the NAT rules:

mgmt_cli show nat-rulebase package "yourRulebaseName" details-level "full" use-object-dictionary true --format json


For the Routes:

Routes file can be created by running from the Firewall the command "netstat -nr" or "show route all"



I have the csv export of the Security and NAT rules, as well as the config file.

The config file shows: Language version: 13.1v1 (is that the Checkpoint software version?)


The security rules.json file has source and destination fields that seem to be some kind of object database key.  Could it be they didnt run the object-dictionary part of the command?

"source" : [ "97aeb369-9aea-11d5-bd16-0090272ccb30" ]


Help would be greatly appreciated.



L5 Sessionator

you will need to validate the json formatting. You can try to open the file in firefox for example which provides debug messages as to the source of the malformed json format. 


Otherwise if you email the json file to fwmigrate I can look at the file.

Thanks, the leading text in the file:


 before the first opening bracket was the issue as you suggested.

The files imported after removing that text before the first opening {


  • 2 replies
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

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!