Blocking on webalizer presence

[ispcolohost]

Is your feature request related to a problem? Please describe.
The conversion will fail if webalizer is present. That was the default webstats on Plesk for many years. I have hundreds of servers to convert, I don't have time to find and convert every site to awstats, and if I blindly convert every site via something like

plesk bin site --list | while read i; do
    if plesk bin site --info "$i" | grep -qi "web statistics.*webalizer"; then
        echo "Converting $i..."
        plesk bin site --update "$i" -webstat awstats
    fi
done

it will take an incredibly long time because that causes a re-running of all the prior logs. It's also undesirable because it will wipe out the stats that had been there.

Describe the solution you'd like
It would be ideal that, if a given site is using webalizer, those files are preserved in an offline location so they're not unintentionally exposed if they had been password protected previously, but are still able to be made accessible if a customer needs them. Once that is complete, a blind conversion to awstats can occur, but in a way that does not rebuild all the history at this time, let that occur during the next normal nightly stats execution so it doesn't slow down the conversion..

Describe alternatives you've considered
Currently I'm forced to just blindly convert and remove:

plesk bin site --list | while read i; do
    if plesk bin site --info "$i" | grep -qi "web statistics.*webalizer"; then
        echo "Converting $i..."
        plesk bin site --update "$i" -webstat awstats
    fi
done
plesk installer remove --components webalizer

I'm looking for any alternative that the script can do itself, unattended, without damage.

Additional context
Add any other context or screenshots about the feature request here.

[mperryment]

AWStats and Webalizer, are unmaintained, I would suggest switching to GoAccess.

[ispcolohost]

I'm fine changing it to goaccess, the issue is really that the tool knows this is a blocker but we must now perform manual steps. For example, even after changing sites, it still fails

Doing preparation checks...
Required pre-conversion condition "checking if the 'webalizer' package is installed" not met:
	Webalizer is not supported on AlmaLinux 9 - consider switching it (remove the component) before conversion
Conversion can't be performed due to the problems noted above

The sites on this server I converted to GoAccess, so it should simply perform the conversion and not care if webalizer is still installed, or it should remove it if it must care for some reason.

[ukablan-wpc]

You need to remove the Webalizer component with installer

[ispcolohost]

Umm okay, well if it's not available and not supported, then the conversion tool should handle this scenario since any copy of Plesk older than a few years likely still has all its sites set to webalizer. If we have to do everything ourselves, then the conversion tool doesn't serve much purpose.

[ukablan-wpc]

See new release v1.3.0 where manual package uninstall is not required