Let’s assume that there is a Slack Enterprise Grid org where one or more workspaces live. What if we need to move one of these workspaces (or a part of a workspace) into a new one, or merge it with an existing one?

Let me show you how to do this.

First, let’s call the workspace in the Enterprise Grid that we’re going to import the source workspace. Respectively, let’s call the new or existing workspace the destination workspace.

Basically, we need to perform two steps:

  • Get the data from the source workspace. We need somehow to get the data from the source workspace formatted in such a way that it can be used for importing to Slack. Usually the format is a Slack-standard ZIP file.
  • Import the data into the destination workspace. Having the data available as a ZIP file we can use the Slack import tool to import the data into a new or existing workspace.

1. Getting the data from the source workspace.

So we need to get the data from the source workspace (a workspace in the Enterprise Grid org) formatted as a ZIP file that Slack import tool understands.

There are two alternative ways to do that:

  • 1.1 Export at the org level.
  • 1.2 Export at the workspace level.

1.1 Export at the org level. You can export the source workspace or multiple source workspaces at the org level as described here. Please note however, Enterprise Grid orgs exports have a special structure so they cannot be imported directly to Slack:


In order to make the export importable, you may consider using the Backupery for Slack Export tool. This tool allows you to convert the export so it can be imported to Slack. Here is how:

  1. Download and install the Backupery for Slack Export tool.
  2. Close the running app (if it is running) by clicking the Exit menu item: 
  3. Navigate to the following directory:

    C:\Users\<USERNAME>\AppData\Local\Backupery for Slack Export
  4. Open user.config using any text editor.
  5. Locate the following section in the file:

    <ImportableJsonConversionSettings>
          <Enabled>false</Enabled>
  6. Replace the lines mentioned above with the following lines:

     <ImportableJsonConversionSettings>
       <Enabled>true</Enabled>
       <ExtractWorkspacesFromEnterpriseGridExport>true</ExtractWorkspacesFromEnterpriseGridExport>
    ​
    so the changed portion of user.config will look like this:
  7. Save user.config.
  8. Run the app and press the Run Export Wizard link:
  9. Specify your Enterprise Grid org export ZIP file.
  10. On the Files window deselect the Download files option:
  11. On the Select formats to present the exported data window make sure there are no selected options:
  12. Process your export file. As a result, you will have multiple ZIP files each of which represents a single workspace from your original Enterprise Grid org export. Now you can import each of these files into Slack.

1.2 Export at the workspace level. If the org-level export is not available, you can export the data from the source workspace at the workspace level. To export the data from a specific workspace in the Enterprise Grid org you may consider using the Slack native export tool. The important point here is that you need to use the tool at the workspace level. Here is how:

  • Click your organization name in the sidebar.
  • Select Tools & settings from the menu, then click Workspace settings.
  • Select the source workspace and click Open.
  • Once opened, click Import/Export Data in the top right.
  • Select the Export tab.
  • Below Export date range, click the drop-down menu to select an option.
  • Click Start Export. Slack will send you an email once your export file is ready.
  • Open the email and click Visit your workspace’s export page.
  • Click Ready for download to access the ZIP file.

Please also see the gif below that illustrates the mentioned steps:


Some users however report that they are not able to export the data at the workspace level using the standard Slack export tool. In this case, you may consider using Backupery for Slack that allows you to export the data at the workspace level. The tool exists in two variants: the desktop (Windows only) and the cloud one (any operating system) so please find two manuals below:

The export process is a pretty straightforward, the only important point is that the tool should be installed and user at the workspace level, not at the whole org level. That means that when you’re installing the tool to Slack, you should select a specific workspace to add the tool into, not the whole org:


As you see on the screenshot, I can install the app to the whole org (My Organization), but I’m installing into a specific workspace (myworkspace-49a8-002).

As you have the data exported from the source workspace, you are ready to import it to the destination workspace.

2. Import the data to the destination workspace.

The import process is well documented here: https://slack.com/help/articles/217872578-Import-data-from-one-Slack-workspace-to-another

Just a couple of additional recommendations:

  • Review Slack import data manual and Import FAQ. Both articles provide useful information about capabilities and limitations of the tooling.
  • Don’t expect a complete clone of your source workspace. Due the nature of the export-import tooling, it transfers a lot of data, but not all. For example, apps are not transferred and must be set up the destination workspace after the import has completed.
  • To import the files into the destination workspace, both the user who shared the file and the conversation where it was shared must be imported. So in order to import specific files into the destination workspace, the user must be invited to the destination workspace. It is not possible to import files without inviting the user who shared the file.

Hope this helps. If you have any questions or concerns, we’re listening!

Leave a Reply

Your email address will not be published. Required fields are marked *