BigFix Software Distribution Limitations and Legacy Compatibility

Packages created in the legacy BigFix SWD Dashboard (Console) or legacy BigFix WebUI are not visible in the new BigFix UI, and packages created in the new BigFix UI cannot be imported back into legacy tools — migration is one-directional and requires an explicit export-and-import process.

Legacy Package Visibility

Note:
The Package export feature is not available in the new BFUI.
Packages created using the following legacy tools are not visible in the new BigFix UI and cannot be used or managed from it:
  • The legacy SWD Dashboard in the BigFix Console.
  • The legacy SWD application in the BigFix WebUI.

Conversely, packages created in the new BigFix UI are not visible in the legacy Console or WebUI. The two environments maintain completely separate package stores.

Migrating Packages from Legacy Tools to the New BigFix UI

Note:
For security reasons the import of packages cannot accept zip files. The user must unzip the folder containing the package and import the row folder. Be careful that it is possible to export from the BF Console multiple packages at the same time, in this case a single zip file is created, it contains multiple zip files for each exported package. If you want to import these multiple packages you have to unzip all of them one by one before loading them in the interface.

To reuse a package previously created in the legacy Console or WebUI within the new BigFix UI, you must perform an explicit migration using the following steps:

  1. Export the package from the legacy BigFix Console or legacy BigFix WebUI using its export function.
  2. Import the exported package file into the new BigFix UI via the More options icon → Import on the Software Explorer page.

During the import process, the new BigFix UI recreates all content from the legacy package:

  • Tasks — new Tasks are created in the BigFix Platform for each task in the imported package.
  • Files — all files from the imported package are uploaded to and stored in the new BFUI File Server.

Migration Direction Restriction

Restriction:
Migration is one-directional only. It is not possible to import into a legacy BigFix Console or legacy WebUI a package that was exported from the new BigFix UI. If you need to share a package with a team still using legacy tools, that package must be recreated natively in those legacy tools.

Additional Limitations and Operational Notes

Note:
Adding or removing files or packages may take a moment. Please do not close or move out of the page until the process is complete.