Skip to content

Move from Microsoft Teams

Moving from Microsoft Teams is manual. Rebuild conversations in Enclessa while keeping a separate plan for files in SharePoint and OneDrive, calendars and identity in Entra ID. Enclessa does not replace Office document editing. Members sign in through Entra ID over SAML or OpenID Connect, with SCIM provisioning.

Updated

In Microsoft Teams

In Enclessa

Tenant

Tenant

Organisation

Four things called Teams

Separate the chat from the platform around it

  • Conversations

    Teams and channels in Enclessa

    Plan into Enclessa

  • Identity

    Entra ID over SSO and SCIM

    Plan into Enclessa

  • Files

    Stay in SharePoint and OneDrive

    Plan separately

  • Meetings

    Calls from the calendar; no telephony

    Plan separately

What moves where

Teams structure, mapped onto Enclessa

  • TenantOrganisation
  • TeamTeam
  • Standard channelA managed channel
  • Private channelA private managed channel, or a group direct message
  • Shared channelNo equivalent
  • Chat and group chatDirect messages and group direct messages
  • Channel files tabUploads in the channel, or SharePoint left where it is
  • Planner and TasksTask boards
  • Entra ID accountsSingle sign-on and SCIM provisioning

Audit first

  • How accounts will come from Entra ID
  • Which teams are alive and which were created for one project
  • Where your files actually are
  • What depends on meetings and telephony
  • Which apps and tabs are doing real work

The plan

Migrate from Microsoft Teams to Enclessa

  1. Settle the identity question firstConnect Entra ID over SAML or OpenID Connect, decide whether single sign-on is optional or required, and switch on SCIM provisioning if accounts and groups should follow the directory. Everything after this step assumes accounts come from there.
  2. Separate the conversation from the document platformDecide 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.
  3. Rebuild the live teams and channelsCreate 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.
  4. Choose a room mode for each private channelA 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.
  5. Rebuild what the connectors and flows were doingAnything 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.
  6. Run both for a fortnight, then stop posting in TeamsKeep 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.

Limits

What this migration will not do

Enclessa compared with Microsoft Teams
  • There is no Teams importer and no migration tooling. Structure is rebuilt by hand and history stays with Microsoft.
  • There is no document co-authoring and no spreadsheet; the wiki is Spaces, an optional module. Files are stored, scanned, previewed and searched, not edited.
  • There is no dial-in, no PSTN calling and no webinar mode.
  • There is no equivalent of shared channels, tabs, connectors, Power Automate or Copilot.

FAQ

Moving from Microsoft Teams: questions

  • No. Enclessa imports Slack and Mattermost archives, not Teams, because Teams offers no export file an administrator can simply download. Microsoft documents two routes: the Teams Export APIs, which need administrator-consented application permissions and are metered, and a data export tool requested from Microsoft through a form, limited to tenants of up to 500 users and to 90 days, whose archive carries attachments as SharePoint and OneDrive links rather than files. Teams structure is rebuilt by hand, and chat history stays in Microsoft 365.
  • Yes. Enclessa signs members in through Entra ID over SAML 2.0 or OpenID Connect, an organisation can make single sign-on optional or required, and SCIM 2.0 provisioning creates, updates and deactivates accounts and groups from the directory.
  • 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.

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.