Whether single sign-on is negotiable
Enclessa has no SAML, no OpenID Connect and no SCIM. If accounts must come from Entra ID, this migration does not work today, and finding that out in the audit costs an afternoon rather than a quarter.
Migration · Microsoft Teams
Most of what you call Teams is four products
Migrating from Microsoft Teams to Enclessa is manual, and it starts by separating what Teams actually is: chat stored in Exchange, files stored in SharePoint and OneDrive, meetings, and identity in Entra ID. Enclessa replaces the conversation and, with its modules, the boards and time tracking — it does not replace the document platform or the identity provider, and it has no single sign-on, which is the first thing to establish rather than the last.
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.
There is no importer
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.
At a glance
- Importer
- None. Structure is rebuilt by hand
- Teams and channels
- Map closely onto Enclessa teams and channels
- Files
- Live in SharePoint and stay there unless you move them
- Identity
- No single sign-on — accounts are created in Enclessa
- Meetings
- Calls exist; scheduling and telephony do not
- Trial
- The Free plan, up to ten people, no payment card
What to audit before anybody moves
Which teams are alive and which were created for one project
Teams tenants accumulate teams the way workspaces accumulate channels. Sort by recent activity and rebuild what is used; the rest is an archive question for your Microsoft 365 administrator.
Where your files actually are
Channel files are in the team’s SharePoint document library and chat attachments are in the sender’s OneDrive. Neither moves because you left Teams, and both are reachable independently — which is convenient, because it means the document platform is a separate decision from the chat platform.
What depends on meetings and telephony
Enclessa has calls with screen sharing, a lobby and host controls. It has no meeting scheduling from a calendar, no dial-in numbers, no PSTN calling and no webinars. If any of those are load-bearing, they stay with Microsoft or move elsewhere.
Which apps and tabs are doing real work
Tabs, connectors, Power Automate flows and bots have no equivalent. Each is rebuilt as an incoming webhook, a slash command or an API integration, or it is dropped. List them while you can still see them.
How Microsoft Teams maps onto Enclessa
| Microsoft Teams | Enclessa | What changes |
|---|---|---|
| Tenant | Organisation | One organisation, reached at your own subdomain. Enclessa has no cross-tenant federation. |
| Team | Team | The closest mapping in this list. An Enclessa team holds its own categories, channels and roles. |
| Standard channel | A managed channel | Server-readable, so search, retention, export, webhooks and bots all work in it. |
| Private channel | A private managed channel, or a group direct message | Managed keeps it searchable and exportable; a group direct message is end-to-end encrypted with no administrator override. Decide before creating it — the mode is permanent. |
| Shared channel | Nothing | There is no way to share a room with another organisation. External people need accounts in yours. |
| Chat and group chat | Direct messages and group direct messages | Always end-to-end encrypted here, with no administrator override and no server-side search. |
| Channel files tab | Uploads in the channel, or SharePoint left where it is | Enclessa stores, scans, previews and searches files. It does not co-author documents, so a document platform is a separate decision. |
| Planner and Tasks | Task boards | A board belongs to a team and inherits its roles, and a card links back to the message the work came from. Boards are a module. |
| Entra ID accounts | Accounts created in Enclessa | There is no directory synchronisation and no single sign-on. This is the constraint most likely to stop the migration. |
What comes across
- Your team and channel structure, once rebuilt — the mapping is closer here than for any other source.
- Files, if somebody uploads them again; they are scanned for malware and their text indexed for search.
- Planner-style work, if you rebuild it as boards.
- Anything posting through a connector, rebuilt as an incoming webhook.
What does not come across
- Chat history. Nothing imports it, and it lives in Exchange rather than in Teams itself.
- SharePoint and OneDrive content, unless you deliberately move the files.
- Identity. There is no single sign-on and no directory sync.
- Meetings, recordings, transcripts, dial-in numbers and PSTN calling.
- Tabs, apps, connectors, Power Automate flows and Copilot.
- Shared channels and cross-tenant access of any kind.
Running the migration, step by step
Settle the identity question first
Establish whether accounts must come from Entra ID. Enclessa has no SAML, OpenID Connect or SCIM, so if federated identity is a requirement rather than a preference, stop here — everything after this step assumes accounts are created in Enclessa.
Separate the conversation from the document platform
Decide explicitly whether SharePoint and OneDrive stay. Enclessa stores, scans, previews and searches files but does not co-author documents, so most organisations keep a document platform and move only the conversation. That is a smaller migration and a better one.
Rebuild the live teams and channels
Create the teams that are actually used, and their channels, grouped into categories. This mapping is close to one-to-one, which makes Teams the easiest of these migrations to plan and the hardest to finish, because the identity and document questions are the real work.
Choose a room mode for each private channel
A private managed channel is searchable, retainable and exportable. A group direct message is end-to-end encrypted and no administrator can read it or add themselves to it. The mode is fixed at creation, so this is a decision rather than a default.
Rebuild what the connectors and flows were doing
Anything that posted into a channel becomes an incoming webhook. Anything interactive becomes a custom slash command calling your own endpoint. Anything needing buttons, cards or approvals inside a message has no equivalent and needs a different answer.
Run both for a fortnight, then stop posting in Teams
Keep Teams readable while people learn the new structure, answer questions in Enclessa regardless of where they were asked, then announce a date and stop posting. Your Microsoft 365 administrator decides what happens to the tenant afterwards; the migration ends when the posting does.
Getting your data out of Microsoft Teams
There is no single button that exports a Teams tenant, because the data is not in one place. Channel messages and chats are stored behind Exchange, files are in SharePoint and OneDrive, and the supported route to message content is your tenant’s compliance and eDiscovery tooling in the Microsoft 365 administration centre. Your Microsoft 365 administrator is the person who can tell you what your licences actually allow, and that conversation should happen during the audit rather than after the cutover.
- Ask your Microsoft 365 administrator what your licensing permits before assuming a message export is available.
- Channel files live in the team’s SharePoint document library and can be downloaded directly from there.
- Chat attachments live in the sender’s OneDrive, which is a different place with different permissions.
- Message content is normally reached through the compliance and eDiscovery tooling rather than through Teams itself.
- Individuals can also request a copy of their own data through Microsoft’s privacy portal, which is a separate route with a separate scope.
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 planWhat Enclessa will not do for this migration
- There is no importer and no migration tooling. Structure is rebuilt by hand and history stays with Microsoft.
- There is no single sign-on, no directory synchronisation and no SCIM. For many Microsoft 365 organisations this alone is disqualifying, and it is better established early.
- There is no document co-authoring, no wiki and no spreadsheet. Files are stored, scanned, previewed and searched, not edited.
- There is no meeting scheduling, no dial-in, no PSTN calling and no webinar mode.
- There is no equivalent of shared channels, tabs, connectors, Power Automate or Copilot.
- There are no mobile apps. Enclessa runs in the browser and on macOS.
Related
Enclessa vs Microsoft TeamsWhere Teams is stronger, and where the trade is worth making.Read moreThe Free planTrial the move with ten people and no payment card.Read morePublic sectorThe sovereignty argument that usually starts this migration.Read moreSecurityWhat protects the data, and the certifications not held.Read more
Questions
Migrating from Microsoft Teams: questions
Can I import Microsoft Teams data into Enclessa?
No. Enclessa has no importer. Teams structure is rebuilt by hand, and chat history stays in Microsoft 365, where it is stored behind Exchange rather than in Teams itself.
Does Enclessa support single sign-on with Entra ID?
No. There is no SAML, no OpenID Connect and no SCIM provisioning. Accounts are created in Enclessa with an email address and a password, which is the constraint most likely to decide whether this migration is possible for you.
What happens to our SharePoint files?
They stay in SharePoint. Enclessa stores, scans, previews and searches uploaded files but does not co-author documents, so most organisations move the conversation and keep a document platform.
Can Enclessa replace Teams meetings?
Partly. There are video calls with screen sharing, a lobby and host controls, started from a channel. There is no calendar-driven meeting scheduling, no dial-in number, no PSTN calling and no webinar mode.
How do private channels map onto Enclessa?
A private channel becomes either a private managed channel, which stays searchable, retainable and exportable, or a group direct message, which is end-to-end encrypted with no administrator override. The choice is permanent, because a room’s mode cannot be changed after it is created.
Encrypted collaboration, hosted in Europe.
Create 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.