Skip to content

Migration · WhatsApp

The migration where the data is the smallest problem

Moving work off WhatsApp into Enclessa is less a data migration than a governance change: the history lives on personal handsets, WhatsApp exports one conversation at a time from within that conversation, and there is nothing an administrator can do centrally. What changes is that the organisation gets rooms it owns, accounts instead of personal phone numbers, roles, and a leaving process that actually ends access — and what you must test first is that Enclessa has no mobile apps.

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, and no realistic route to one
History
On personal devices; export is per chat, by the person
One group
Becomes several channels, by what it is used for
Identity
Accounts, not personal phone numbers
Test first
There are no mobile apps — browser and macOS only
Cost
Free for up to ten people, permanently

What to audit before anybody moves

Whether your people can work without a mobile app

This is the first question and it decides the rest. Enclessa runs in the browser and on macOS; there is no iOS or Android application. For a team on a shop floor, a building site or a delivery round, that is likely to be decisive, and it is better tested in week one than discovered in month two.

What the group is actually used for

List the distinct things happening in that single thread: the rota, the operational questions, the customer issues, the social. That list becomes the channel structure, and it is what stops the replacement from becoming one busy room again.

What is in there that should not be

Photographs of documents, customer details, health information, addresses. A work group on personal handsets is usually processing personal data with no record, no retention rule and no way to delete it, and naming that is often what gets the migration approved.

Who is in the group and who should not be

Former colleagues, contractors, somebody’s partner who was added for one event in 2023. Everybody in the group has everybody’s private mobile number, permanently.

What has to be kept

If anything in there has to be retained, it has to be exported from a personal device by the person who owns it, one conversation at a time. Decide what is genuinely worth that effort — usually very little.

How WhatsApp maps onto Enclessa

WhatsAppEnclessaWhat changes
The one big groupSeveral channels in a team, grouped into categoriesThe whole point of the move. One thread for everything is the problem, not the starting position to preserve.
A group for a specific projectA channel, archived when the project endsA channel that stops being used stops being in the way, without anybody having to leave it.
A quiet side conversationA group direct messageEnd-to-end encrypted, with no administrator override — the same confidentiality property people went to WhatsApp for.
Phone numbers as identityAccounts with email addressesNobody has to hand out a personal mobile number to join the workspace, and nobody keeps access after they leave.
Admin of the groupRoles at organisation, team and channel levelPermissions are a bitmask with allow and deny overwrites, rather than one person who happens to have created the group.
Voice notes and callsVoice messages, and video calls started in the channelCalls have screen sharing, a lobby and host controls. There is no telephone number and no PSTN calling.
Broadcast listsA channel, with mentionsMentions reach a person, a role, a custom group or the whole channel.

What comes across

  • Nothing automatically. This migration is entirely manual, and mercifully small.
  • Anything a person deliberately re-posts: a rota, a canonical instruction, a document.
  • Files, if somebody uploads them again — scanned for malware and indexed for search.
  • The habit, if you are deliberate about splitting one group into several channels.

What does not come across

  • Message history. It is on personal devices and WhatsApp exports it one conversation at a time.
  • Media, unless somebody uploads it again.
  • Contacts and phone numbers, which is largely the point.
  • Voice and video call history.
  • Anything from WhatsApp Business: catalogues, labels, automated replies or the Business API.

Running the migration, step by step

  1. Test the browser and macOS clients with the people who will use them

    Enclessa has no mobile apps. Before anything else, put it in front of the people who currently work from their phones and find out whether the browser on their device is good enough for what they actually do. If it is not, stop here.

  2. Write down what the group is used for

    List the distinct uses in that single thread. This list is the channel structure, and doing it before creating anything is what prevents the replacement from collapsing back into one room where everything is mixed together.

  3. Create the workspace and invite people by email

    Set up the organisation and its first team, and invite people to accounts rather than collecting phone numbers. The Free plan covers up to ten people permanently, with no payment card and no expiry, so a small team can do this without a purchase decision.

  4. Build the channels, and keep private things private

    One channel per use, grouped into categories. Conversations that should not be in front of everybody become group direct messages, which are end-to-end encrypted with no administrator override — the property people were relying on WhatsApp for, without the personal-device problem.

  5. Save the little that is worth saving

    WhatsApp can export a single conversation as a text file, with or without media, from within that conversation on the device it is on. It is a personal action rather than an administrative one. Pick the few things worth keeping, post them into the right channel, and leave the rest.

  6. Run both for two weeks, then close the group

    Keep the group open while people learn where things go, and answer every question in the new channel even when it was asked in the old group. Then announce a date, say it in both places, and close the group — one that stays open never empties.

  7. Use the leaving process you now have

    When somebody leaves, deactivate the account and access ends across every channel at once. The organisation keeps its record, and nobody is relying on a former colleague to delete a thread from their own phone.

Getting your data out of WhatsApp

There is no administrative export, because there is no administrator. WhatsApp offers a per-conversation export from inside that conversation, performed by a person on their own device, producing a text file with the option to include media. There is also a separate request for a copy of your own account information in the application’s settings. Both are personal actions on personal devices, which is precisely the governance problem the migration exists to solve.

  • The export is per conversation, from within it, on the device it lives on.
  • It produces a text file, optionally with media attached; the exact limits depend on the conversation’s size and the platform.
  • It is done by the individual, not by the organisation. Nobody can do it centrally, and nobody can compel it.
  • The separate account-information request in settings is about your own account, not about a group’s history.
  • Check both on one device before planning around either. The applications differ between iOS and Android and change over time.

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 plan

What Enclessa will not do for this migration

  • There is no importer, and given where the data lives there is no realistic route to one.
  • There are no mobile apps. Enclessa runs in the browser and on macOS, and this is the single most likely reason a WhatsApp migration fails.
  • There is no telephone number, no SMS and no PSTN calling. Enclessa replaces the group, not the phone.
  • Group channels are not end-to-end encrypted. Direct messages and group direct messages are.
  • On the Free plan, search covers the last ninety days. Older messages remain, but searching all of them is a paid plan.
  • There is no WhatsApp Business equivalent: no catalogue, no labels, no automated replies and no customer-messaging API.

Related

Questions

Migrating from WhatsApp: questions

Can I import a WhatsApp group into Enclessa?

No. There is no importer, and the history lives on personal devices rather than anywhere an organisation controls. WhatsApp exports a single conversation at a time, from within that conversation, as a text file.

Does Enclessa have a mobile app?

No. Enclessa runs in the browser and on macOS, and there are no iOS or Android applications. For a team replacing a phone-first messenger this is the first thing to test and the most likely reason not to move.

Is Enclessa as private as WhatsApp?

Direct messages and group direct messages are end-to-end encrypted using MLS per RFC 9420, with no administrator override. Group channels are deliberately server-readable, because that is what makes search, retention and export work — so the answer depends on which room you are in, and the room always says which it is.

What does it cost to move a small team off WhatsApp?

Nothing for up to ten people. The Free plan is permanent rather than a trial, needs no payment card, and includes channels, threads, encrypted direct messages, video calls and search over the last ninety days.

Why move off WhatsApp at all?

Because the organisation has no copy of its own record, cannot end somebody’s access to the history when they leave, and usually has no answer about the personal data sitting in the thread. Those are governance problems rather than feature problems, and they do not improve with time.

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.