Supplemental Slack info for you and your team.Tips and tools for beginners and experts alike.Get familiar with Slack Enterprise Grid for large organizations.If you're curious about what's new in Slack — and what's changed — you're in the right place.Develop your skills and prepare to become Slack Certified!Launching a new team or joining one for the first time?
Our easy-to-read guides help your team work better, together, from day one.Ready to level up? Browse our time-saving tricks and practical tips for
making Slack work for you.All kinds of teams thrive with Slack — take a look at our department-specific guides.
More coming soon!Learn how Slack works, from top to bottom!Want to learn more about setting up your team? Look no further!Welcome to Slack! We're so glad you're here. Let's get started!Adjust your profile and preferences to make Slack work just for you!Simplify your daily work with apps and tools.Tips and tools for beginners and experts alike.
Slack is experiencing some connectivity issues — please stand by. Check Status
A third-party app: HipChat, Flowdock, Campfire, or Chatwork
Step 1: Plan your import
Before you get started, it's helpful to understand exactly what can be imported into Slack. We've broken this down for you below.
Invite as many or as few of your former members to Slack as you'd like. For each one, you can do the following:
Create a Slack account and invite the member to your workspace
Create a disabled account and invite the member to join later
Import a member's messages, but choose not to invite the person to your workspace (messages will display as bot messages instead)
Choose not to import the member or their messages at all
Note: Members with no email address will be imported to Slack as bot users. You can leave them as is, or create Slack accounts for them if you'd like.
When mapping messages to Slack, you can choose where they should go, channel by channel. You can do the following:
Map imported content to a new or existing public channel
Map imported content to a new private channel (that you've joined)
Choose not to import certain messages to Slack
Note: It's not possible to import content from private channels or direct messages from one workspace into another.
Step 2: Start your import
From your desktop, click your workspace name in the top left.
Select Administration, then Workspace settings from the menu.
Click Import/Export Data in the top right.
Click Import next to the service you’re importing from.
For Slack, Hipchat, Hall, Chatwork, or a CSV or text file, click Choose File, attach your file, then Click Start Import. For Flowdock, authenticate your account to begin your import. For Campfire, enter your Campfire URL and token.
When your import is ready, you'll get an email and Slackbot message. 💌
Warning: Please do not edit the .zip, .csv, or .txt file before importing to Slack — this causes errors during the import process.
Note: Large imports may take time and could temporarily affect your Slack app's performance. You can start one import per hour.
Step 3: Map your import
Hooray, your import is ready! Now it's time to map your imported members and message history into your Slack workspace:
Locate and open your confirmation email and click Continue your import. Or, from the Import Data page, click Information required.
Decide what data to import and where it should go. Members and messages are automatically mapped for you, but in cases where we didn't get it right, you can manually make adjustments.
Click Save Changes.
When you're ready, select Yes, proceed with import.
Once your import has completed, you'll receive a confirmation email.
Keep in mind: You can cancel an import in progress, or rollback once it's complete, and start again. Click Cancel or Start Rollback from the Import Data page for the service you've imported from.
Who can use this feature?
Workspace Owners and Admins can access this feature.
Available on free and paid plans.
Thanks so much for your feedback!
Thanks for your feedback.
If you’d like a member of our support team to respond to you, please send a note to email@example.com.
Oops! We're having trouble. Please try again later!