Migrate from HipChat Server to HipChat Data Center
If you previously used HipChat Server, and are ready to migrate to a HipChat Data Center deployment, use this guide and the HipChat Data Center deployment guides to set up your new deployment and migrate users.
On this page:
Before you begin
Hold your horses! Before you do anything:
- Read the architecture information, and decide how you will deploy HipChat Data Center.
HipChat Data Center is currently available for deployment on VMware and AWS only, however you can now deploy it either with a single HipChat node, or with a three-HipChat-node cluster for scale or higher availability. Regardless of how many HipChat nodes you deploy, you also need to provide the external data stores for the service and manage SSL termination within your network.
- Plan your deployment.
Use the information in the HipChat Data Center system requirements to determine what component servers and services you need in order to deploy.
The requirements guide also includes important sizing information, so don't skip it!
- Read the full deployment guide to understand the deployment process, and check the release notes for your destination version.
The release notes will alert you if you need to do anything special before you deploy.
Deploy and test on an evaluation instance first.
We don't need to tell you this, it's just a good practice.A Pro Tip if you're comfortable using snapshots...
- Schedule an outage or maintenance window for your deployment.
Although we designed the upgrade process to minimize downtime for your deployment, you should do this just in case.
Deploy a HipChat Data Center cluster
- Choose the Deployment option that best serves your organization, and deploy the required components.
- Configure the components using the instructions in the Configuration requirements for HipChat Data Center.
- Finally, Deploy HipChat Data Center to the prepared cluster, and configure your instance's optional features.
Export your HipChat Server data
Export the data from your production HipChat Server instance.
Make a list of the integrations and API tokens on your old HipChat Server instance. (You'll re-enable and reconfigure them on the new HipChat Data Center instance once it's set up.)
Prepare the HipChat Data Center deployment
- Verify that the destination HipChat Data Center cluster is up and functioning correctly. All external data stores must be configured before you import your data archive.
- Run the
sudo dont-blame-hipchatcommand. (This allows you to write to the file store in the next step.)
- Copy the data archive file to the NFS host and put it in the
Import the archive
- Import the data archive into your HipChat Data Center deployment.
- Restore the integrations (now called add-ons) and API tokens that you were using in HipChat Server.
Connect to a external authentication sources or import users
If your organization uses an external authentication source (such as Active Directory, LDAP, Crowd, or a SAML identity provider such as Okta or OneLogin), connect your new HipChat Data Center instance to that source or provider after you import the data from your old server.
Verify the deployment
Test your deployment to make sure that all of the functionality is working as intended. You should confirm that:
- users can log in using your organization's authentication source
- users can view (and if enabled, edit) their profile information
- users can send and receive messages in chat rooms
- emoticons are working in chat messages
- any integrations that are enabled are working
- users can upload and view files
- users can search for messages in their chat history
- if enabled, users can send and receive 1-to-1 chats
- if enabled, video chat is working
Notify and let your users in
Once you've confirmed that the new HipChat Data Center deployment is up and running, tell your users and let them log in! Woohoo!
Was this helpful?
Thanks for your feedback!