@rcelyte Just wanted to tag you in here - this PR would automatically migrate previous BT configs. For BT servers we can assume that they will run their API on `http://<previous_hostname>:<new_arbitrary_api_port>".

If there's something different we should do/assume for BeatUpServers when migrating configs it'd be good to put that in now so we can reduce end user headaches

BeatUpServer will utilize the existing status URL for graph requests. The classic hostname will not be required or used in the new connection flow.

If there's something different we should do/assume for BeatUpServers when migrating configs it'd be good to put that in now so we can reduce end user headaches

Guess that fell through? This'll be a rough time explaining to my users why their configs spontaneously broke x_x