There's no magic importer for AIDA64 panel files; you'll be rebuilding your layout. The upside is that rebuilding in a drag-and-drop editor is usually faster than the original config-file surgery was, and templates give you a finished starting point.
> Before you switch: check these_
- ■CLU VIEW is a sensor panel, not a diagnostics suite. If you rely on AIDA64's benchmarks, stress tests or hardware audits, keep it for those jobs.
- ■LCD/VFD character displays (e.g. Logitech keyboard LCDs) are AIDA64-only. CLU VIEW targets graphical screens.
- ■Full sensor access (temperatures, FPS) wants admin privileges and the open-source LibreHardwareMonitor driver.
> The migration, step by step_
Download CLU VIEW and install (SmartScreen: "More info" → "Run anyway"; there's no code-signing cert yet).
Screenshot your AIDA64 panel for reference, note which sensors it shows, then close AIDA64 (two tools polling the same sensors can conflict).
Set the canvas to your screen's resolution, then either rebuild from the widget gallery or import a template close to your old layout and adapt it.
Point each widget at your hardware in the Monitor picker: CPU/GPU temps, usage, RAM, fans, FPS.
Switch to Panel Mode and select your secondary display. Save the profile; make variants for gaming/work if you like.
> What you gain_
The obvious one is the license: $0. Beyond that you get a freeform canvas with multi-select, undo/redo and zoom instead of a grid editor, plus 216 widget styles, 19 effects and 11 full-screen filters AIDA64 doesn't have. The rules engine can recolour widgets or switch profiles on sensor thresholds, running apps or time of day, and profile switching is instant across 50 slots.
Full comparison in the AIDA64 alternative guide.