Leaving X: community and archive planning

Leaving X — or any other public network — is not just a matter of closing the app. If you built a community there, leaving without a plan means losing an archive, confusing your audience and leaving a gap that impersonators can fill. Treat it like moving house, not like flipping a switch.

How to harden the account while you are still there is in the guide to using X safely. Reducing disclosure and keeping identities apart are covered in reducing social-media disclosure and separating online identities.

Archive first, then tell people, then cut the dependency

Before you delete or walk away, download the official data archive from X and keep a separate copy of links, a list of key people and posts you still cite. The official archive will not hand you everything in a readable form; private messages and some media may be incomplete.

1. On the web, open More, then Settings and privacy > Your account > Download an archive of your data.
2. Enter your password and, if asked, a two-factor code, then choose Request archive. Preparation can take hours or longer.
3. In the app, open Settings and privacy, then Your account or Account, and request the archive from the data section. If the app asks for an email or number, have that already on the account.
4. When the ready notice arrives, go back to the same settings and choose Download archive. Do not tap a link inside a suspicious message; fake “your archive is ready” mail is common.
5. Store the compressed file somewhere safe, not in a public chat and not in a widely shared sync folder. The file may contain private messages and identifying personal data. Treat it like a sensitive document in a backup you can restore.
6. Open Your archive.html in a browser after extracting the whole folder. Opening that file from inside the unextracted archive often shows a blank page.

Do not assume the official archive is complete

The archive gives you posts, the profile and much of the media, but it does not always return every private message or every file in a readable, complete form. Copy separately, in your own hands, the things you still cite — an article, a list of colleagues, stable links.

1. Move sensitive private conversations to another channel before you leave.
2. Write the short list of people who must hear the news outside X: names and an alternative contact path.
3. Save posts you still link from introductions or articles, or move them to a more stable place.
4. Do not assume that deleting the account also removes other people’s republications and screenshots.

Say more than once, over several days, where you are going

Many people will miss a single post. Tell your audience several times, over several days, and in more than one form if you can, where the next destination is: a newsletter, a website, Mastodon, Bluesky or wherever you will actually be present.

1. Prepare the destination before you announce it publicly, so the links work and a blank page is not waiting.
2. Say in the text which other accounts are yours, so impersonation is harder later.
3. Give close colleagues a contact path outside X so a lockout does not cut you off.
4. If you keep the profile up, write in the bio where your main activity has moved.
5. Limit the announcement to people who need to know if leaving should not draw fresh attention; “the louder the better” is not right for everyone.

After you leave, be ready for impersonators

When a familiar name fades from a network, fake accounts with that same name become more likely. Say so in your other introductions, and if you are still active somewhere, leave a standing line there about which accounts are official.

1. Repeat the username and the destination address on the site or newsletter, not only in one passing post.
2. Ask close colleagues to tell you quickly if they see an account that looks like you.
3. If you are not deleting the account and are only becoming less active, write that down so the gap is not an opening for an impersonator.
4. Keep the password and two-factor authentication for as long as the account exists; an abandoned account without a second factor is an easy target.

Cut the dependency in stages

Cutting every sign-in at once can make recovery harder. First build the archive and the alternative contact path, then announce, then reduce daily sign-in, and leave deletion — if you want it — until the end.

1. Close sign-ins from devices you no longer need, in the security settings.
2. Review third-party apps connected to the account and cut them.
3. If the new destination is also a social network, do not repeat the same disclosure mistakes there.

Choose the next destination by the work you will actually do

A newsletter, a site, Mastodon or Bluesky is only a destination if you will be present there. Announcing several addresses that you will not update confuses the audience more.

1. Pick one main destination and treat the others as complements, not six equal “new homes.”
2. If you set up a newsletter, send a test issue to yourself before you announce it so the confirmation link works.
3. If you are moving to another network, register the username before you announce it so an impersonator does not take that same name.
4. Keep a stable contact path — a work email or a form on the site — even if you also have a new network.

Do not click delete before you understand what it does

Some services distinguish deactivation from deletion and may leave a window in which you can come back. Those details change; before the final confirmation, read X’s own help on that same page.

1. Download and actually open the archive first.
2. See whether deletion frees the username so someone else might take it.
3. If it is an organizational account, coordinate with the people who depend on it; one admin’s personal decision should not leave a community uninformed.
4. After you delete or leave, have already closed open sessions on old devices if you can.

Treat the archive file like a sensitive document

Inside the file there may be messages, a follower list and data X has kept about you. The file is for the move, not for sending to a group.

1. Encrypt it or put it somewhere only you can reach.
2. After extraction, if you no longer need the compressed file and you have a safe copy, delete the extra copy on the desktop.
3. Do not share the download link; it is usually valid for a limited time and tied to a sign-in on the same account.

Coordinate with people who reached you there every day

If journalists, an organization or a group reached you through X, leaving without coordination means they lose the source as well. A short private message to close colleagues, separate from the public announcement, prevents a sudden cut.

1. Test the alternative contact path once for each person: email, a number, or another messenger.
2. If a group coordinated on X, say before you leave where coordination will happen next.
3. Do not keep that list only on X itself; if the account closes, the list goes with it.

Do not mix the announcement into a random news wave

If you post only once in the middle of a public crisis, many people will miss it in the noise. A few reminders on quieter days work better than one shout in the busiest hour.

1. Have a first announcement, a reminder after a day or more, and a standing note in the bio.
2. Write the destination link in full each time, not with an unknown shortener.
3. If the audience is multilingual, write at least in the language most of them read.

What the archive does not replace

An archive keeps a memory of posts; it does not move a community. People come when there is a place to talk and to see your new work. If you only download the file and never build a destination, the work is half done.

1. Get the archive even if you later stay; having it does not depend on leaving.
2. Prepare the destination before you cut daily sign-in.
3. After you settle in the new place, look once from the outside and see whether the links and the contact path are findable. If finding you from outside was hard, repeat that same announcement once more with the destination’s full address so nobody gets lost on the way to the new place.

Common mistakes

• Deleting the account before you have the archive.
• A single announcement on one afternoon and the assumption that everyone saw it.
• Announcing a destination that has no page yet.
• Putting the archive file in a group chat or a public shared drive.
• Tapping an “archive is ready” email without opening settings from the app itself.
• Assuming that sensitive private messages will remain complete and safe inside the archive.

What to do today

1. Download the archive now, even if you have not finally decided to leave.
2. Write a short list of people who must hear the news and how you will reach them another way.
3. Prepare the next destination before you announce it, so the links work.
4. Move sensitive private conversations to another channel; do not assume the archive will hold them complete.
5. If you are leaving, write clearly in your other introductions which accounts are yours and which you do not recognize. Keep the complete archive file as well somewhere separate from any open public network, restricted and fully safe, and only with you in a safe place.