mirror of https://github.com/zulip/zulip.git
docs: Remove HipChat migration guide.
As of Feb 15th 2019, Hipchat Cloud and Stride have reached End Of Life and are no longer supported by Atlassian. Since it is almost 2 years now we can remove the migration guides.
This commit is contained in:
Aman Agrawal
parent
df9e40491d
commit
62d721e859
|
|
@ -74,8 +74,8 @@ If the script gives an error, consult [Troubleshooting](#troubleshooting) below.
|
|||
## Step 3: Create a Zulip organization, and log in
|
||||
|
||||
On success, the install script prints a link. If you're [restoring a
|
||||
backup][zulip-backups] or importing your data from [HipChat][hipchat-import],
|
||||
[Slack][slack-import], or another Zulip server, you should stop here
|
||||
backup][zulip-backups] or importing your data from [Slack][slack-import],
|
||||
or another Zulip server, you should stop here
|
||||
and return to the import instructions.
|
||||
|
||||
[hipchat-import]: https://zulip.com/help/import-from-hipchat
|
||||
|
|
|
|||
Binary file not shown.
|
Before Width: | Height: | Size: 94 KiB |
|
|
@ -1998,13 +1998,6 @@ nav {
|
|||
margin-top: 20px;
|
||||
}
|
||||
|
||||
.portico-landing.hello .call-to-action-bottom .atlassian-migration {
|
||||
margin-top: 60px;
|
||||
text-align: center;
|
||||
font-size: 1.3rem;
|
||||
font-weight: 300;
|
||||
}
|
||||
|
||||
.portico-landing.hello .call-to-action-bottom .zulip-octopus {
|
||||
margin: 130px auto 0 auto;
|
||||
width: 32px;
|
||||
|
|
@ -2309,12 +2302,6 @@ nav {
|
|||
background-image: url(../../images/landing-page/security.jpg);
|
||||
}
|
||||
|
||||
.portico-landing.why-page .bg-pycon.atlassian {
|
||||
background-size: 300px;
|
||||
background-image: url(../../images/landing-page/atlassian.jpg);
|
||||
background-repeat: repeat-x;
|
||||
}
|
||||
|
||||
.portico-landing.why-page .bg-pycon.why-zulip {
|
||||
background-image: url(../../images/landing-page/why-zulip-threads.jpg);
|
||||
}
|
||||
|
|
|
|||
|
|
@ -1,34 +0,0 @@
|
|||
{% extends "zerver/portico.html" %}
|
||||
{% set entrypoint = "landing-page" %}
|
||||
|
||||
{% block title %}
|
||||
<title>Migrating from HipChat and Stride</title>
|
||||
{% endblock %}
|
||||
|
||||
{% block customhead %}
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
{% endblock %}
|
||||
|
||||
{% block portico_content %}
|
||||
|
||||
{% include 'zerver/landing_nav.html' %}
|
||||
|
||||
<div class="portico-landing why-page">
|
||||
<div class="hero bg-pycon atlassian">
|
||||
<div class="bg-dimmer"></div>
|
||||
<div class="content">
|
||||
<h1 class="center">Migrating from HipChat and Stride</h1>
|
||||
<p></p>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div class="main">
|
||||
<div class="padded-content">
|
||||
<div class="inner-content markdown">
|
||||
{{ render_markdown_path('zerver/atlassian.md') }}
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
{% endblock %}
|
||||
|
|
@ -1,72 +0,0 @@
|
|||
Zulip runs on-premises or in the cloud, and integrates with the rest of
|
||||
Atlassian’s products. The following describes some typical steps for
|
||||
migrating from Atlassian’s HipChat or Stride to Zulip.
|
||||
|
||||
## Do a trial of Zulip.
|
||||
|
||||
* [Install Zulip
|
||||
on-premise](https://zulip.readthedocs.io/en/stable/production/install.html)
|
||||
or [create a Zulip Cloud
|
||||
organization](https://zulip.com/new). Installing a Zulip server takes
|
||||
just a couple of minutes.
|
||||
|
||||
* Stop by the [Zulip community server](https://chat.zulip.org) to see
|
||||
what an active Zulip organization looks like. The Zulip community
|
||||
server has around 10,000 users with several hundred weekly actives.
|
||||
|
||||
* Try to get at least a few very busy people to take a look at topic-based
|
||||
threads on the [community server](https://chat.zulip.org) and/or read
|
||||
[Why Zulip](/why-zulip). Zulip has a unique threading model that makes
|
||||
everybody more productive, but those in meetings all day are often the
|
||||
first people to “get it” and be strong advocates for Zulip internally.
|
||||
|
||||
A user experience trial of a team chat tool like Zulip works best if
|
||||
you have a team spend a week using it as their primary work
|
||||
communication tool; this allows the trial group to get familiar with
|
||||
the tool (and with Zulip, experience the magic of topics).
|
||||
|
||||
## Import your HipChat data.
|
||||
|
||||
You can export from HipChat or Stride, and import into Zulip Cloud or Zulip
|
||||
on-premise. Instructions are available [here](/help/import-from-hipchat).
|
||||
|
||||
If you’re importing into Zulip Cloud, we recommend doing a test import
|
||||
with us a few days before, and then scheduling a migration date to
|
||||
make sure there is as little interruption in service as possible. The
|
||||
import can take anywhere from a few seconds to several hours depending
|
||||
on how much data you have.
|
||||
|
||||
## Set up third-party integrations.
|
||||
|
||||
Zulip has over [100 native integrations](/integrations), and hundreds more
|
||||
through Zapier, Hubot, and IFTTT.
|
||||
|
||||
Instructions for integrating with [JIRA](/integrations/doc/jira),
|
||||
[Bitbucket](/integrations/doc/bitbucket2),
|
||||
[Trello](/integrations/doc/trello),
|
||||
[Statuspage](/integrations/doc/statuspage), and
|
||||
[OpsGenie](/integrations/doc/opsgenie) are linked.
|
||||
|
||||
We recommend integrating via [Zapier](/integrations/doc/zapier) for
|
||||
Confluence, Bamboo, Fisheye, Crucible, Crowd, and Sourcetree.
|
||||
[Contact us](/help/contact-support) if you get stuck and we’d be happy to help
|
||||
you out.
|
||||
|
||||
## Read our guides.
|
||||
|
||||
We have a guide for
|
||||
[setting up your Zulip organization](/help/getting-your-organization-started-with-zulip),
|
||||
as well as a [guide for new Zulip users](/help/getting-started-with-zulip).
|
||||
|
||||
You may also want to send out material like [Why Zulip](/why-zulip), the
|
||||
[tour on the Zulip homepage](/), or our
|
||||
[guide to streams and topics](/help/about-streams-and-topics) to users being
|
||||
migrated, so that everyone gets a running start with Zulip’s thread-based
|
||||
chat model.
|
||||
|
||||
## Decide on a payment plan.
|
||||
|
||||
See [zulip.com/plans](https://zulip.com/plans) for Cloud
|
||||
pricing, or email <support@zulip.com> for on-premise support
|
||||
options. We also offer affordable paid installation help that includes
|
||||
installing and configuring Zulip.
|
||||
|
|
@ -34,8 +34,8 @@
|
|||
{% endif %}
|
||||
<div class="bottom-text">
|
||||
Or import
|
||||
from <a href="/help/import-from-slack">Slack</a>, <a href="/help/import-from-mattermost">Mattermost</a>,
|
||||
<a href="/help/import-from-hipchat">HipChat</a> or <a href="/help/import-from-gitter">Gitter</a>.
|
||||
from <a href="/help/import-from-slack">Slack</a>, <a href="/help/import-from-mattermost">Mattermost</a>
|
||||
or <a href="/help/import-from-gitter">Gitter</a>.
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
|
|
|
|||
|
|
@ -540,10 +540,6 @@
|
|||
{{ _('Sign up now') }}
|
||||
</a>
|
||||
{% endif %}
|
||||
<p class="atlassian-migration">
|
||||
Migrating from HipChat or Stride?
|
||||
Check out our <a href="/atlassian">Atlassian migration guide</a>.
|
||||
</p>
|
||||
<div class="zulip-octopus"></div>
|
||||
</div>
|
||||
</div>
|
||||
|
|
|
|||
|
|
@ -1,159 +0,0 @@
|
|||
# Import from HipChat/Stride
|
||||
|
||||
Starting with Zulip 1.9, Zulip supports importing data from HipChat and Stride,
|
||||
including users, rooms, messages, avatars, and custom emoji.
|
||||
|
||||
This tool has been used to import HipChat teams with thousands of
|
||||
members, thousands of streams and millions of messages. If you're
|
||||
planning on doing an import much larger than that, or run into
|
||||
performance issues when importing, [contact us](/help/contact-support).
|
||||
|
||||
**Note:** You can only import a HipChat or Stride group as a new Zulip
|
||||
organization. In particular, you cannot use this tool to import data
|
||||
into an existing Zulip organization.
|
||||
|
||||
## Import from HipChat or Stride
|
||||
|
||||
First, export your data.
|
||||
|
||||
{start_tabs}
|
||||
{tab|cloud}
|
||||
|
||||
1. Log in at `yourdomain.hipchat.com/admin/`.
|
||||
|
||||
1. Click on the **Data Export** tab.
|
||||
|
||||
1. Select the data to export.
|
||||
|
||||
1. Set a **Password** to encrypt your export.
|
||||
|
||||
1. Click **Export**.
|
||||
|
||||
Once the export has completed, the export will be available to you in the
|
||||
admin console.
|
||||
|
||||
{tab|server}
|
||||
|
||||
1. Upgrade to the latest version to ensure you have the latest updates to
|
||||
the HipChat export dashboard.
|
||||
|
||||
1. Log in at the domain name configured for your HipChat Server.
|
||||
|
||||
1. Click on **Server Admin > Export**.
|
||||
|
||||
1. Select the data to export.
|
||||
|
||||
1. Set a **Password** to encrypt your export.
|
||||
|
||||
1. Click **Export**.
|
||||
|
||||
Once the export has completed, you will receive an **email** with a link to
|
||||
download the file.
|
||||
|
||||
!!! tip ""
|
||||
If you are not on the latest version of HipChat Server / Data Center,
|
||||
you can do a command line export with `hipchat export --export`. See
|
||||
HipChat's [command line export docs][cli-export] for more information.
|
||||
|
||||
{tab|stride}
|
||||
|
||||
1. Log in at `yourdomain.atlassian.net/admin/`.
|
||||
|
||||
1. Click on **Stride** in the bottom left in Application Settings.
|
||||
|
||||
1. Click **Create export**.
|
||||
|
||||
1. Select the data to export.
|
||||
|
||||
1. Set a **Password** to encrypt your export.
|
||||
|
||||
1. Click **Export**.
|
||||
|
||||
{end_tabs}
|
||||
|
||||
!!! warn ""
|
||||
**Note:** Only HipChat Group Administrators can export data from HipChat.
|
||||
|
||||
[cli-export]: https://confluence.atlassian.com/hipchatdc3/export-data-from-hipchat-data-center-913476832.html
|
||||
|
||||
### Import into Zulip Cloud
|
||||
|
||||
Email support@zulip.com with your exported archive and your desired Zulip
|
||||
subdomain. Your imported organization will be hosted at
|
||||
`<subdomain>.zulipchat.com`.
|
||||
|
||||
Also, see the [caveats section notes on room subscribers](#caveats)
|
||||
and consider whether you want to also send a HipChat API key to
|
||||
provide a more faithful import.
|
||||
|
||||
If you've already created a test organization at
|
||||
`<subdomain>.zulipchat.com`, let us know, and we can rename the old
|
||||
organization first.
|
||||
|
||||
### Import into a self-hosted Zulip server
|
||||
|
||||
First
|
||||
[install a new Zulip server](https://zulip.readthedocs.io/en/stable/production/install.html),
|
||||
skipping "Step 3: Create a Zulip organization, and log in" (you'll
|
||||
create your Zulip organization via the data import tool instead).
|
||||
|
||||
Use [upgrade-zulip-from-git][upgrade-zulip-from-git] to
|
||||
upgrade your Zulip server to the latest `master` branch.
|
||||
|
||||
Log in to a shell on your Zulip server as the `zulip` user. To import with
|
||||
the most common configuration, run the following commands, replacing
|
||||
`<exported_file>` with the HipChat export file and `<password>` with the
|
||||
password you set during the HipChat export.
|
||||
|
||||
```
|
||||
cd /home/zulip/deployments/current
|
||||
supervisorctl stop all # Stop the Zulip server
|
||||
openssl aes-256-cbc -d -in <exported_file> -out hipchat.tar.gz -md md5 -pass pass:<password>
|
||||
./manage.py convert_hipchat_data hipchat.tar.gz --output converted_hipchat_data
|
||||
./manage.py import '' converted_hipchat_data
|
||||
./scripts/restart-server
|
||||
```
|
||||
|
||||
This could take several minutes to run, depending on how much data
|
||||
you're importing. The server stop/restart is only necessary when
|
||||
importing on a server with minimal RAM, where an OOM kill might
|
||||
otherwise occur.
|
||||
|
||||
**Import options**
|
||||
|
||||
The commands above create an imported organization on the root domain
|
||||
(`EXTERNAL_HOST`) of the Zulip installation. You can also import into a
|
||||
custom subdomain, e.g. if you already have an existing organization on the
|
||||
root domain. Replace the last line above with the following, after replacing
|
||||
`<subdomain>` with the desired subdomain.
|
||||
|
||||
```
|
||||
./manage.py import <subdomain> converted_hipchat_data
|
||||
```
|
||||
|
||||
{!import-login.md!}
|
||||
|
||||
[upgrade-zulip-from-git]: https://zulip.readthedocs.io/en/latest/production/upgrade-or-modify.html#upgrading-from-a-git-repository
|
||||
|
||||
## Caveats
|
||||
|
||||
While the import tool will correctly import the subscribers of private
|
||||
rooms, HipChat does not store or export the list of subscribers for public
|
||||
rooms. You can pick one of the following options for handling this:
|
||||
|
||||
1. Subscribe all users to all public streams (the default, which is good for small organizations).
|
||||
|
||||
1. Subscribe only HipChat room owners to public streams (and plan for users
|
||||
to subscribe to the imported Zulip streams manually after the import
|
||||
completes) using the `--slim-mode` option to `manage.py convert_hipchat_data`.
|
||||
|
||||
1. Use the [HipChat API][hipchat-api-tokens] to fetch each room's current
|
||||
room subscribers as of the moment the import is run. Because HipChat
|
||||
doesn't store subscribers to a room when clients are not connected, these
|
||||
subscriptons will be incomplete for users who don't have an actively
|
||||
connected client at the time of the import. You need to pass a HipChat
|
||||
access token via `--token=abcd1234` in `manage.py convert_hipchat_data`
|
||||
(or include it in your request, if importing into Zulip Cloud).
|
||||
|
||||
[upgrade-zulip-from-git]: https://zulip.readthedocs.io/en/latest/production/upgrade-or-modify.html#upgrading-from-a-git-repository
|
||||
[hipchat-api-tokens]: https://developer.atlassian.com/server/hipchat/hipchat-rest-api-access-tokens/
|
||||
|
|
@ -106,7 +106,6 @@
|
|||
## Organization basics
|
||||
* [Review your organization's settings](/help/review-your-organization-settings)
|
||||
* [Create your organization profile](/help/create-your-organization-profile)
|
||||
* [Import from HipChat/Stride](/help/import-from-hipchat)
|
||||
* [Import from Mattermost](/help/import-from-mattermost)
|
||||
* [Import from Slack](/help/import-from-slack)
|
||||
* [Import from Gitter](/help/import-from-gitter)
|
||||
|
|
|
|||
|
|
@ -138,7 +138,6 @@ class DocPageTest(ZulipTestCase):
|
|||
self._test('/for/companies/', 'in a company')
|
||||
self._test('/for/working-groups-and-communities/', 'standards bodies')
|
||||
self._test('/security/', 'TLS encryption')
|
||||
self._test('/atlassian/', 'HipChat')
|
||||
self._test('/devlogin/', 'Normal users', landing_page=False)
|
||||
self._test('/devtools/', 'Useful development URLs')
|
||||
self._test('/errors/404/', 'Page not found')
|
||||
|
|
|
|||
|
|
@ -743,7 +743,6 @@ i18n_urls = [
|
|||
path('for/working-groups-and-communities/', landing_view,
|
||||
{'template_name': 'zerver/for-working-groups-and-communities.html'}),
|
||||
path('security/', landing_view, {'template_name': 'zerver/security.html'}),
|
||||
path('atlassian/', landing_view, {'template_name': 'zerver/atlassian.html'}),
|
||||
|
||||
# Terms of Service and privacy pages.
|
||||
path('terms/', terms_view),
|
||||
|
|
|
|||
Loading…
Reference in New Issue