Forcepoint Migration issues in import phase

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Forcepoint Migration issues in import phase

L1 Bithead

 

Hi Team,

Do you have a guide on how to migrate from Forcepoint to Palo Alto using the Expedition Tool?

Which are the required files and steps to action this?

We have tested multiple combinations of file import and here’s the constatations :

*While importing ZIP with data.zip , I could fing the policy name for the dedicated firewall , but it imports just the objects and networks

Also, I could’t not find the policy name if I import the policy file.

*** I tried to import just XML with the FW-cluster and policies , so it doesn’t show anything in dashboard, also with the copy paste in sidewinder .

I need to know if it is related to the exportation from the Forcepoint , or it’s related to Expedition .

Thanks.

9 REPLIES 9

L4 Transporter

Hi @Bouthaina 

Thanks for reaching out.

Please follow the notes given by email.

Best regards,

David Puigdomenech 

L0 Member

@dpuigdomenec  I am having same issue. Could you please help me about this issue ?

 

Sure, I just answered your email to DL fwmigrate@paloaltonetworks.com
Thanks,

L1 Bithead

Hi Team,

 

I am also facing the same issue. I have written to fwmigrate@paloaltonetworks.com . Any help/suggestions would be greatly appreciated.

L1 Bithead

@dpuigdomenec Request your help on this one. I am stuck with this issue for a long time

L1 Bithead

Hi @Bouthaina / @Ihsan-Beydogan ,

 

Did you get a resolution for your issue?

Hi @sarveshvc,

 
I just answered your email but let me copy here the content.
 
As of January 1st, 2025, Expedition has reached its End-of-Life (EOL) status, and support for it is now exceptionally limited.
For migration assistance, please reach out to your sales account representative for Migration Factory services onboarding.
For further details, kindly refer to the complete EOL announcement accessible at https://live.paloaltonetworks.com/t5/expedition-articles/important-update-end-of-life-announcement-f....

As a troubleshooting guide for Stonesoft migrations.
 

1) Make sure you are mapping the policy during import. That means that just after uploading your XML file you should select under the "Policy Grid" the "Config File Name" with a "Firewall Name" and a "Policy Name".

 
 
dpuigdomenec_1-1737374427418.png
2) Check the XML file is properly exported. Make sure it contains one of the XML tags. 
  • fw_single
  • fw_cluster
  • virtual_fw
Let me know if you that works for you,
Best,
David

L1 Bithead

Hi @dpuigdomenec ,

 

Really appreciate your help. Could you please let me know if the "Policy Name" can be anything or should it match the Policy name which is there on the forcepoint?

The problem I have is that I don't have access to the Forcepoint and I am dependant on a separate team for the info.

Hi @sarveshvc 

 

The values you need to map ("Config File Name", "Firewall Name" and "Policy Name") should be populated by Expedition after uploading the XML file.

 

The Stonesoft can have multiple FW and policies so you should select the once you need to import.

 

Hope this helps,

 

David

  • 1645 Views
  • 9 replies
  • 0 Likes
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!