since our instance of HipChat Server is behind the firewall, it's not a trivial task to get IT Security approval to change the FW rules, would this work as a 'workround' upgrade:
I'd be really grateful if you could review these steps and let me know if it looks ok, or if not, what could be missing there.
Yes, those steps look correct. Have you considered the offline upgrade? https://confluence.atlassian.com/hipchatkb/how-to-perform-offline-upgrades-in-hipchat-server-826878852.html
The reason I ask is that the export archive only contains messages, users/user data, and rooms/room data and specifically excludes integrations, passwords, API tokens, and server settings (as dictated at Exporting and Importing your HipChat data).
Running the offline upgrade is an easier solution (be sure to snap-shot your instance before upgrading!) than standing up a fresh install.
HipChat Server Support Engineer | Atlassian
...from the beginning. We have built up a lot of content in HipChat, with it being a core tool in our distributed company model. While it is true that we didn’t need to move to Slack immediately, we felt it...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs