Bring your communitywith you.

Channels and roles, in one step.

Channel groups, channels, voice rooms, forums and roles with their colors and permissions. Messages and members stay where they are.

• A server template linkPaste a template link from the chat service your community uses now. Hubs reads the structure only, with no messages and no member lists.
• Or a snapshot fileA JSON file of a server's structure, up to 4 MB, in the snapshot format Hubs reads.
• What comes acrossCategories become channel groups. Text channels, voice rooms, forums and roles come across with their colors, their permissions and who can see each channel. Up to 600 channels and 300 roles.
• A preview firstBefore anything is made, you see what will be created, what already exists and what stays behind, with a reason for each.

The import makes everything in one go or nothing at all, and keeps a report of what it did. Nobody gets a role until an admin gives it to them.

Past conversations, kept as an archive.

Bring a workspace chat export you're allowed to keep. You review it first, choose which channels to keep, and choose who can read the ones that were public.

• A workspace chat export (ZIP)The ZIP a workspace export gives you: channels.json, with users.json and groups.json if you have them, and a folder for each channel with one JSON file per day. Up to 45 MB zipped and 60 MB unzipped.
• What comes acrossMessages with their times, edits, replies and reaction counts, under the names people had there. Files come too when they are inside the ZIP; links are never fetched.
• What stays behindDirect and group messages, and the old workspace's roles, permissions, apps and workflows.
• Labeled, never impersonatedHistory arrives as a read-only archive that only the owner sees at first. It never adds people to your hub or posts as them.