Just to be clear, InfluxDB was never an official HA app. It was provided by the “Home Assistant Community Apps” repository, that is managed by Frenck.
For those of you considering other options, just know that if you move to another community-supported solution then you are at risk of this happening again in the future. I was also caught out by this issue, but my solution is to self-host my own repository of apps including my own InfluxDB v2 database.
I realise that’s not feasible for all users, but you need to understand the risks of using third-party repositories to support your HA installation. Any community-supported or third-party repository can remove an app at any time, or they can change the app in a way that you might not want. You are handing over full trust to that third-party.
We trust, we learn. But deleting the addon and its data with the result of a single click is far from fair…
One possible solution could be, to show 2 buttons (for remove and don’t remove) and in case of removing more than just an App code an additional Warning: 5GB of additional data will also be removed.
The chance to remove a huge DB with a simple commit button will be significantly reduced.
I always wounder WTH the backup dialog also does not show the size off Apps being included in the backups. Would be a huge improvement as well.
Regarding VictoriaMetrics, can anyone confirm or disconfirm that text entities and non-floating point number entities are supported?
Anything else that could break when migrating from InfluxDB1 to VictoriaMetrics?
This is irrilevant.
And the behaviour of Freck is somewhat criminal (and incompetent).
Where is the problem?
Just use your backup and everything is fine.
You have no backup?
Sorry, that is somewhat criminal (and incompetent).
This is of course true, but certainly beside the point. The issue here is not necessarily the deprecation of this software which is EoL, it is the interaction between this repository’s management (a repo owned by an HA maintainer and available-by-default in a fresh HA installation for many years, mind you) and HA’s behavior, leading to: an un-ignorable and frankly pushy prompt directly alongside the update notifications which will, if clicked once, delete an entire database. I have luckily avoided getting caught by this, but my Influx DB contains over four years of sensor data, integrated with Grafana dashboards, etc. Of course one should back up their data, etc, but this still disrupts production deployments and unexpectedly creates an hours-long recovery/migration task.
People who have been running HA for a while will know that Influx V1 was an extraordinarily common recommendation for long term data storage for a long time, cited countless times in forums and tutorials. This unfortunate combination of factors create a massive potential pitfall for a substantial fraction of long term users with no clear or documented migration path. This long term data is very valuable to users, and, at the very least, archived repos need to be handled more carefully by HA. Likely this situation was not anticipated, but it is absolutely reckless UX. At the very least, the “press submit to uninstall” flow for archived repos must be reconsidered.
“Just use your backup and everything is fine.” => sadly if you press submit on the suggested “repair” you can not restore the app/add-on from backup as the repo is gone. Only thing left is a data migration where you extract influx data from the backup tar file.
It clearly says so in the message (see first post in this thread) but you must admit this is a rather drastic action to put behind a simple Submit button in a repair dialog box.
Of course I admit that the behavior is absolutely unexpectable and leds to dataloss.
But no excuse for blaming someone as “criminal” and “incompetent”.
Btw: my backup is a proxmox snapshot.
The deprecation of the InfluxDB V1 Add-on came at rather short notice. Something that caught quite a few of us (myself included) by surprise. 
As a stop bleeding solution, I’ve created a fork of the original add-on and updated it to the newest Debian base image along with the latest available InfluxDB V1 version.
To be clear: I don’t consider this the real mid- to long-term successor. It’s simply meant to buy us some time until a proper solution comes along.
You can find my fork and a migration guide here: GitHub - vistalba/addon-influxdb: InfluxDB - Home Assistant Community Add-ons · GitHub
Created with a little help from Qwen3.8. 
It’s certainly not criminal or incompetent. I expect the devs are being as thoughtful and considered as they can. But I expect many of us are prone to clicking too quickly (thankfully, I didn’t). As such, it probably should carry a bright crimson warning like, “This is irreversible and may break things. Don’t click this until you’ve migrated your data”.
P.S. Restoring is further complicated by the fact the addon is no longer available. Not incurable but certainly more involved. Another reason to deploy on Proxmox.
The warning is pretty clear. I did not click submit and made this thread in the community forum for alternatives to migrate to.
All the words are there, far from criminal.
I strongly second this. I had a very professional impression of HA / Frenck through the last years. But then this, just with a little button to click “OK”? 
@frenck help us !
There’s a Github issue (unfortunately rather a stub)
I asked for help solving the actual purpose of this thread, and instead I got bored to death with ‘how to ask a good question’ info. Much appreciated, very kind of you.
You tagged somebody who wasn’t part of this conversation. The link I sent you pointed you towards the explicit paragraph that mentions it. Seems like you didn’t bother to click it.
You’re very welcome, btw.
It’s notable that (AFAICT) there has been zero response from @frenck on this.
I relay on influxdb for loads of data. I get that products become eol, but to have this happen with zero advanced warning is very close to being “FUHA”.