Server to organisation
Categories carry over, voice channels become calls
Server
General
- announcements
- lounge
Dev
- builds
- help-forum
Organisation
General
- announcements
- Calls started in a channel
Dev
- builds
- No forum channels
The plan
Migrate from Discord to Enclessa
- Test the calling habit before anything elseSpend 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.
- List the bots and decide what replaces eachFor 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.
- Rebuild the categories and channelsCreate 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.
- Translate the roles and overwritesEnclessa 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.
- Invite people as accounts, not through a linkEverybody 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.
- Have anyone who needs their history request it nowDiscord 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.
- Run both for a fortnight, then make the server read-onlyKeep 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.
Before anybody moves
Audit Discord first
- Whether the always-open voice channel is load-bearing
- Which bots are doing something you would pay for
- Who is actually in the server
- What is in the direct messages
- Whether anything must be retained
Leaving Discord
Getting your data out of Discord
- Look for the data request in Discord’s user settings under privacy, as an individual rather than as a server owner.
- The package is prepared asynchronously and delivered by a link, so start well before you need it.
- It covers that person’s own data, not the server’s history as a whole.
- There is no owner-level or administrative export of a server, so plan for the history staying where it is.
- Check the current behaviour in the application before planning around it; Discord’s privacy tooling changes.
FAQ
Moving from Discord: questions
- No, on both counts. Discord has no server-wide export for an owner — only a personal data request an individual makes for their own data — and Enclessa has no Discord importer. The history stays in Discord.
- No. Calls are started in a channel, with screen sharing, a lobby and host controls, and they end when they end. For a team used to dropping into a permanently open voice room, this is the change most worth testing before committing.
- Closely. Enclessa resolves permissions from named roles over a bitmask, with allow and deny overwrites on a category or a channel, which is the same model Discord users already work with at organisation, team and channel level.
Bring your team over this afternoon
Free for up to 10 people, with encrypted direct messages and video calls. No payment card, no time limit, no server to run.
For businesses and organisations only — not available to consumers.