Migration · Discord
Migrating a Discord server used for work to Enclessa is manual, and it maps better than most: categories become categories, channels become channels, and Discord’s roles translate onto a permission bitmask with allow and deny overwrites per category and channel. The two things to test before committing are the always-open voice channel, which has no direct equivalent, and the fact that Discord offers no server-wide export for an owner to rely on.
Open betaThe platform is being built in the open, so parts of it are not there yet, behaviour changes between releases, and no availability figure is committed while it is in beta. What is still being built.
Enclessa has no automated importer. No tool moves messages, files, members or permissions out of another product and into Enclessa, and none is promised. Migration is a manual exercise: you rebuild the structure, run both systems side by side for a fortnight, and cut over on a date everybody knows. Every guide here is written for that reality rather than around it.
Discord’s habit of leaving a voice channel open and dropping in is the thing teams miss most. Enclessa calls are started in a channel with screen sharing, a lobby and host controls. Run a week of real work on that before deciding, because it is a working-culture change rather than a feature comparison.
A working Discord server usually has several bots. Enclessa has no bot ecosystem and nothing loads third-party code, so each one is rebuilt as an incoming webhook, a custom slash command calling your own endpoint, or an API integration — or it goes.
Servers accumulate members. Establish who is staff, who is a contractor, and who joined through an invite link two years ago, because everybody in Enclessa is an account in your organisation rather than a member of a public room.
Work that happened in Discord direct messages is invisible to the organisation and unrecoverable by it. Decide what has to be brought into channels before the people involved stop looking at Discord.
Establish this early, because the answer determines whether individual people need to request their own data before the server goes quiet. There is no owner-level export to fall back on.
| Discord | Enclessa | What changes |
|---|---|---|
| Server | Organisation, or one team inside it | A server used for one company usually becomes one organisation with one team. |
| Category | Category | A direct match, including having permissions of its own that channels inherit. |
| Text channel | A managed channel | Server-readable, so search, retention, export, webhooks and bots work in it. |
| Voice channel | Calls started in a channel | The weakest mapping in the list. Calls have screen sharing, a lobby and host controls, but they are started and ended rather than permanently open. |
| Roles with per-channel overwrites | Roles over a permission bitmask, with allow and deny overwrites | Unusually close. Enclessa resolves permissions per role and per member with overwrites on a category or a channel, which is the model Discord users already have in their heads. |
| Threads | Threads | Replies collapse under the message that started them, with a dedicated thread inbox. |
| Direct messages and group DMs | Direct messages and group direct messages | Always end-to-end encrypted here, with no administrator override and no server-side search. |
| Bots and slash commands | Incoming webhooks, custom slash commands, the API | A custom command calls your own endpoint and answers within three seconds, publicly or privately. There is no bot marketplace to install from. |
| Invite links, stage channels, forum channels, boosts | Nothing | People are invited to accounts. There is no public join link, no stage, no forum channel and no boost. |
Spend a week running real work with calls started in a channel rather than an always-open voice room. If dropping into a permanently open channel is how your team actually works, that is the thing most likely to make this migration fail, and a week of testing is cheaper than finding out afterwards.
For each bot, write down what it does and which of three answers applies: an incoming webhook, a custom slash command calling your own endpoint, or nothing. There is no bot marketplace here and nothing loads third-party code, so the third answer is common and better acknowledged early.
Create the team, then the categories, then the channels that are actually used. Discord servers accumulate channels faster than most products, so rebuild what is alive rather than what exists.
Enclessa resolves permissions from roles over a bitmask, with allow and deny overwrites on a category or a channel. This is close to the model you already use, so write the translation out once, apply it, and check it against a member who is not an administrator.
Everybody becomes an account in your organisation with an email address. There is no public join link, which is a loss for a community and the entire point for a company.
Discord has no owner-level server export, so anybody who needs a copy of their own messages has to request their own data package from Discord’s settings, and that takes time to arrive. Start this before the server goes quiet, not after.
Keep Discord open while people learn where things go, answer questions in Enclessa regardless of where they were asked, then announce a date and stop posting. Leave the server as an archive rather than deleting it.
Discord does not provide a server-wide export for an owner. The route that exists is a personal one: an individual requests a copy of their own data from the application’s privacy settings, and Discord prepares a package and sends a link, which takes time. That means there is no way for an organisation to produce the history of its own server centrally, which is worth stating plainly in whatever justifies the migration.
The zero-risk way to test this migration is the Free plan: up to ten people, permanently, with no payment card and nothing to cancel. Run one team on it for a fortnight before you commit anybody else.
See the Free planCreate a workspace in a couple of minutes. It is yours at your-team.enclessa.app, hosted in the European Union, with encrypted direct messages from the first one you send.
Open beta. Free plan, no payment card to start.