Following recent VMware pricing changes under Broadcom, many IT teams are taking a fresh look at where Fiery XF runs in their environment. If you’ve decided to move Fiery XF off VMware, the key is doing it cleanly and safely, without disrupting production.

This post focuses on moving Fiery XF with minimal downtime by following best practices for:

• Creating complete Fiery XF backups
• Handling licensing (including a temporary safety net)
• Restoring and validating your configuration on the new platform

High-Level Migration Flow

Here’s the recommended end‑to‑end sequence:

1. Create a complete .ebk backup for the production server.
2. Export individual environment .xfe files for the production server.
3. Record the Fiery XF licensing codes (LACs) and store them in a safe location.
4. Deactivate Fiery XF licensing on the old server.
5. Apply a 30‑day temporary license code on the outgoing server as a fallback, in case you need to reactivate during migration.
6. Install Fiery XF on the new platform.
7. Reactivate permanent licensing on the new server.
8. Restore the full .ebk backup (and use .xfe files as needed).
9. Test printer configuration and workflows thoroughly.
10. Recreate hotfolders, share and activate in Fiery as needed.
11. Decommission the old server once testing is complete and satisfactory.

If you’d like help planning your specific migration, want us to review your backup and licensing approach, or would like to discuss and schedule a dedicated migration window, please reach out to us—we’re happy to work through the details with your team.

You can call us at 415-382-8681 or contact us on our website.