Stonesoft exported_data.xml files have the capability to define, in one single config file, multiple configurations for multiple devices.
From what we have learnt so far, there are cases in which the configuration XML defines the mapping between different security policies and devices. Recently we have found a couple of cases in which this mapping is not directly defined in the data_export.xml file, or at least I have not determined yet with certainty how this mapping is defined. We are investigating the logic that the people at Forcepoint are using to identify the mappings based on the XML.
Sometimes it is the FW device name, which matches the policy name. Other times, it is an additional granted policy mapping, and some other cases seems to have an alternative method that I am trying to find out. (the dbkey that the different elements have in the XML file does not seem to be the final answer).
In the case you would find that the Migration Tool did not manage to import the security policies for your Stonesoft exported_data.xml file, please do the following.
<fw_cluster auto_reboot_timeout="10" cluster_mode="balancing" db_key="999"
<fw_policy db_key="1111" [...]
[...] template_policy_ref="The Template" template_policy_ref_key="111">
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE generic_import_export SYSTEM "generic_import_export_v5.8.dtd">
<generic_import_export build="8824" update_package_version="632">
[... more lines come below ...]
This mapping, clearly defines that the FW (a cluster in this case) "The-Firewall-Cluster" should load the policy with name "The-Firewall-Policy"; and that "Another-Firewall-Single" should load the policy "Its-Firewall-Single-Policy".
When we get more information in how Stonesoft determines this mapping based on original exported_data.xml, we will implement the logic so you do not need to manually include the mappings.
We wish you a great migration process,