X Communities Migration: A WordPress Self-Hosted Playbook for the 21-Day Window

If you administer an X Community with more than a few hundred active members, you have until May 30, 2026 to find a new home. X is shutting the feature down. The official replacement is XChat group chats, capped at 500 to 1,000 members with no threading, no roles, no search, and no archive. For any serious community this is not a migration path. It is a forced exit. This post is the technical playbook our agency uses when we move community admins from a SaaS or platform-feature install to a self-hosted WordPress setup, walked through with timelines, risks, and a cost breakdown for the next 21 days.

The phone calls and emails started on April 23, 2026. Wbcom Designs has been migrating community owners off platform-feature communities for years. The shutdown announcement just made the next 21 days the busiest migration window we have ever seen. We are publishing the playbook openly because the community admins who need it most do not have time to figure it out from scratch.

If you are running a community where the answer to “where will the conversation be in three years” matters, this is for you. Read it through, then either run the playbook yourself or reach out to us and we will set it up for you in 5 business days.

What X is shutting down and why the timing matters

X Head of Product Nikita Bier announced the Communities sunset on April 23. The original cutoff was May 6. After admin pushback, the deadline extended to May 30. Bier’s reasoning was blunt: Communities were 0.4% of X usage but 80% of spam reports, financial scams, and malware. The team was spending half of some weeks on Communities while the rest of the platform suffered.

The replacement, XChat group chats, was announced in the same breath. These will be public, joinable links shareable on the timeline, capped at 500 members initially with a target of 1,000. There is no per-channel moderation, no thread structure, no roles beyond admin and member, no search across the chat, and no export. XChat is being built as a chat product that will eventually ship as a standalone app. It is not a community product.

For an admin running a 50,000-member community, the math is brutal. The cap forces the membership into 50 fragmented chats. The lack of moderation tooling pushes the spam fight onto the admin. The lack of an archive means three years of accumulated value disappears at midnight on May 30. The standalone-app requirement means another conversion step before members reach the conversation.

The 21 days are the full migration window. By May 30 the existing X Community is gone. Whatever you have not migrated by then is lost.

Why we always recommend WordPress for serious community owners

The migration question is not “WordPress or one of the SaaS alternatives.” It is “rented infrastructure or owned infrastructure.” Every SaaS option in the category (Discord, Circle, Skool, Mighty Networks) carries the same structural risk that just played out on X Communities: the platform owner can shut down, raise prices beyond your budget, or pivot the product direction at any time. You have no leverage in any of those scenarios.

WordPress with a self-hosted community plugin is the only option in the category where the data, the membership, and the platform direction are yours. The tradeoff is the setup. SaaS is faster to start; self-hosted is cheaper, more controllable, and immune to forced migrations after the first one.

Our agency has migrated communities from BuddyPress, BuddyBoss, Discourse, Circle, Skool, and now X Communities to a self-hosted WordPress + plugin setup. The pattern is the same every time. The first 5 to 10 days are technical setup. The next 7 to 10 days are content seeding and member migration. By day 21 the community is operating on infrastructure the owner controls, with month-over-month costs that do not scale with member count.

The plugin we ship for this is Jetonomy. The free version handles forums, Q&A mode, idea boards with voting, six trust levels, and 48 REST endpoints. Pro layers on AI moderation, real-time reactions, private messaging, polls, badges, analytics, webhooks, and 8 more modular extensions. We use it on our own properties, and we use it as the default migration target for client work.

The 21-day migration playbook

This is the exact sequence our team runs for clients. Adjust the time allocations based on community size and how complete your X Community archive is.

Days 1 to 3: Decide your target stack and procure hosting

The decision tree is short:

• Community under 1,000 active members, no paid membership, simple discussion-led use case: WordPress + Jetonomy free, hosted on Cloudways or SiteGround starter tiers ($25 to $50 per month).
• Community 1,000 to 25,000 members, may add paid memberships or premium content later: WordPress + Jetonomy Pro, hosted on Cloudways DigitalOcean 2GB or Kinsta starter ($50 to $100 per month).
• Community 25,000+ members or enterprise context: WordPress + Jetonomy Pro on a dedicated VPS (Cloudways DigitalOcean 4GB+, Kinsta business, or self-managed). $150 to $400 per month at this size.

Hosting recommendation matters because the community plugin scales with the database and PHP runtime. A managed WordPress host with separate object cache (Redis or Memcached) is the difference between a community that loads in 800ms and one that takes 3 seconds.

Procurement: spin up the host, point a subdomain (community.yoursite.com or similar) at it, install WordPress. About 2 hours of work for someone who has done it before, half a day for someone learning. Our team does this in 30 minutes for clients on day 1.

Days 4 to 6: Install and configure Jetonomy

Install Jetonomy free from the WordPress plugin repository. The 5-minute setup wizard creates the default forum structure: Categories, Topics, Posts.

The configuration choices that matter:

Trust levels. Six levels by default. Day-zero members are limited (cannot post links, cannot send DMs); long-tenure members get moderation rights. This is what prevents the spam problem that killed X Communities. Set the trust thresholds based on community pace; for most groups, the defaults work.

Categories and tags. Mirror the structure of your X Community as closely as possible. If your X Community had channels, those become categories. If it had topics, those become tags. The mental model your members have built should not change just because the platform did.

Q&A mode. Toggle this on for any category where members ask questions and want curated answers. Q&A categories surface accepted answers above the rest of the thread, which is how Stack Overflow runs. Most community admins want at least one Q&A category.

Idea boards. Idea boards are a separate content type from forum posts. Members vote on suggestions; admins set status (planned, in progress, shipped). If your X Community had a “feature request” or “what should we build” channel, an idea board is the natural home.

Theme matching. Jetonomy is theme-adaptive; it reads your active theme’s colors and typography. Pick a clean WordPress theme (Astra, Kadence, GeneratePress, or our Reign) and the community will match the site brand.

This entire configuration is 60 to 90 minutes. Our agency has it down to about 30 minutes for typical client setups.

Days 7 to 12: Seed the new community with your X archive

X provides no export of Community content. This is the painful part. The choices are:

• Manual screenshot pull. Open the X Community, scroll through the top 50 to 100 threads, screenshot each, paste the content into the new forum as posts with original author attribution. 2 to 3 full work days for a meaningful seed. Lossy but workable.
• Browser automation scrape. Run a Playwright script against the X Community page, pull thread titles and bodies, format as forum-ready content. Faster but X actively rate-limits and now serves a deprecation notice. Most third-party tools that did this stopped working in early May.
• Selective curation. Pick the 25 highest-value threads (the ones members reference, the ones that made the community valuable) and recreate those as flagship forum posts. Skip everything else. This is what we recommend in most cases.

The reason to seed at all: an empty forum on day-one is what drops the migration conversion rate from 25% to 5%. Members walk into the new home, see no activity, and leave. A forum with 25 to 50 high-value threads on launch day feels populated, which keeps the migrated members engaged through their first week.

Allocate three full days to seeding. It is the work nobody wants to do and the work that makes the migration succeed.

Days 13 to 18: Run the member migration

The mechanics in order:

Pin a transition post in the X Community. Title it something like “Important: Community moving to a new home before May 30.” Include the new URL, a one-paragraph explanation, and a deadline. Update this pin every few days as the deadline approaches.

Pin a welcome post on the new forum. Address X migrants directly. Mention the seeding work you did so they know there is content waiting. Link to the trust level explanation so new members understand the model.

Direct-message the top 50 members. This is the highest-conversion step. Send a personal note to your most engaged X Community members explaining the move and asking them to register on the new forum first. These are the people who will create the activity that retains everyone else.

Cross-post on your main X account. Not from inside the Community itself; from your main feed. The Community-only post reaches members who are already there. The main-feed post reaches the broader audience including people who may have wanted to join but never did.

Email any members you have email for. If your community had a newsletter signup, paid membership tier, or Patreon adjacent product, you have email addresses. Send a transition email. Email-based conversion is consistently higher than X-only.

The conversion-rate range we see on these migrations is 10 to 25% from “X Community member” to “active forum member in the first 30 days.” With strong seeding, personal outreach, and email, the upper end is achievable. Without those, expect the lower end.

Days 19 to 21: Final archive and X cleanup

X gives you no native archive, so do this manually:

• Pull final screenshots of the top 25 threads with timestamps and member names visible. Store these in your forum as a “Community archive: pre-migration” hidden category for posterity.
• Update the pinned X post to its final state: “We are now operating at [new URL]. The X Community will be gone on May 30. See you there.”
• DM any high-value member who has not yet joined the new forum. The 24-hour window before shutdown is your last chance.

After May 30, the X Community is gone. Whatever value remained in the archive is gone too. The members you migrated are now your community.

Cost breakdown for the 21-day migration

This is what we quote enterprise clients for the agency-managed version, plus the DIY equivalent for comparison.

DIY (you run the migration)

Line item	Cost
WordPress hosting (Cloudways DigitalOcean 2GB or equivalent), 1 month	$30 to $60
Domain or subdomain	$0 (existing) to $15
Jetonomy free license	$0
Optional: Jetonomy Pro for AI moderation, messaging, advanced features	$79 to $149 per year
Theme (free options work fine; Reign is $79 if you want a community-tuned theme)	$0 to $79
Your time: 30 to 50 hours over 21 days	n/a
Total cash outlay	$30 to $300

Agency-managed (we run it for you)

Line item	Cost
Hosting setup, WordPress install, plugin configuration	included
Theme matching to your brand	included
Up to 50 high-value thread seeding from X archive	included
Migration plan and pinned-post template	included
Member outreach email template (if you have member email)	included
7-day post-launch support	included
Communities under 5,000 members	$2,500 flat
Communities 5,000 to 25,000 members	$4,500 flat
Communities 25,000+ members or enterprise context	starts at $7,500, custom-quoted

The agency-managed pricing reflects the work done and the time saved. For a community owner whose hourly value is anywhere above $50, the math favors the agency option even at the smallest tier. The DIY route works for hobbyist-scale communities where the owner has time and wants to learn the stack.

What we do that DIY does not

When we run a migration, the deliverables differ from a DIY setup in a few specific ways that matter at scale:

Hosting tuning. WordPress can run a 50,000-member community comfortably, but only on properly configured hosting. We tune object cache, set up CDN exclusions for the forum URLs, and configure database optimization. DIY setups often work fine until the community hits 10,000 members and then start slowing down; our setups do not.

Custom REST integrations. Jetonomy’s 48 REST endpoints (more in Pro) let the community talk to your CRM, your email platform, your mobile app. We wire these up as part of the migration. DIY setups typically do not get to this until much later.

Theme matching pixel-perfect to your existing brand. We do this with our BuddyX Pro theme or with a custom child theme on whatever you already use. The community looks like a native part of your site, not a bolted-on forum.

Seeding with author attribution and timestamps. Our seeding process preserves the original author names and approximate posting dates from the X archive. DIY seeding typically loses this metadata. The difference matters because members recognize their own old posts and the community feels continuous instead of starting from zero.

Post-launch monitoring. For the first 7 days after launch we monitor the community for spam waves, register-abuse attempts, and theme bugs. Day-one is the highest-risk window for any new community; we address issues before the community owner sees them.

These details are why our enterprise client renewal rate runs above 90%. The migration is not just “stand up WordPress and install a plugin.” It is “stand up a community that operates at scale from day one and does not need a second migration in 18 months.”

What this looks like for an agency or in-house team running the migration

If you have technical staff and want to run the migration yourself, the playbook above is the recipe. The places teams typically get stuck:

Underestimating the seeding work. Day 7 to 12 is the part most teams skip or rush. The community owners who skip seeding regret it; the ones who allocate three full days to it have the best member retention.

Skipping trust-level configuration. Default trust levels work, but every community has a few categories that need stricter or looser thresholds. Configure these on day 4 to 6, not after the first spam wave.

Letting the theme look generic. Jetonomy is theme-adaptive but only as good as the theme it inherits from. A default Astra install looks like a default Astra install. Spend an hour matching the theme to your existing brand colors and typography. Members notice.

Not running the email outreach. The single highest-conversion channel is email-to-member. Teams that send the email get 25% conversion. Teams that rely only on X cross-posting get 8 to 12%. The email is the difference.

Forgetting the WAF rules. If your new WordPress install is on Cloudflare, the default Bot Management settings often block parts of the WP REST API. We learned this the hard way migrating our own properties last week. Disable aibotsprotection if you have it on, and add a custom WAF rule for any server-to-server traffic the community needs.

These are the five places we see DIY migrations slow down. None are showstoppers; all are time-consuming. Build them into your day-by-day plan from the start.

Common questions in the first 24 hours after the announcement

These are the questions that came in the first day after the X Communities shutdown was announced:

Is the May 30 deadline negotiable? No. Members can still post in the Community until May 30; after that the Community is read-only briefly, then gone.

Can I export my X Community archive? Not officially. X has not provided an export tool. The screenshot pull is the only reliable method. Some browser-automation scrapers exist; expect them to be rate-limited.

Will my X members get notified about the shutdown? Members get an in-app notification within the X Community itself. They do not get a push notification or email. If you want your members to know, you need to tell them yourself.

What about my paid X Community memberships? X is refunding active subscriptions. If your community had paid tiers via X, those subscribers will need to re-subscribe on whatever you migrate to.

Can I run a hybrid: X Community + new forum for a while? You have until May 30. After that, X Community is gone. The hybrid option does not exist past the deadline.

Should I migrate to XChat group chats and keep using X? Only if your community is under 500 members and entirely synchronous chat. For anything else, XChat is not a viable destination. Migrate to a real community platform.

Is WordPress overkill for a small community? Not at the costs we quoted. A 500-member community on WordPress + Jetonomy free runs $30 per month including hosting. The alternative SaaS at the same scale runs $90 to $250 per month. WordPress is cheaper at every size past month one.

How to start

If you are running this yourself: read this post twice, allocate the 21 days on your calendar, and start with day 1. The hosting decision and Jetonomy install can be done today; everything else fits in the next three weeks.

If you want us to run it: send us a note with the rough size of your X Community, your target launch date, and any hosting preferences. We will quote within 24 hours and start the same day on confirmed engagements. Communities under 5,000 members get scoped at $2,500 flat with a 5-business-day delivery; larger communities get custom quotes that match the seeding depth and integration work.

If you want to evaluate the tooling first: download Jetonomy free and stand up a test community. The free version is enough to validate the choice; you do not need Pro for the migration itself, only for AI moderation and the advanced extensions once the community is operating.

The thing not to do is wait. May 30 is fixed. The earlier you move, the more members migrate with you. The later you move, the more members you lose to attrition between announcement and shutdown. Communities that started moving on April 24 have been retaining 60%+ of active members. Communities that wait until May 25 will retain a fraction of that.

We have done this enough times to know the playbook works. The X Communities shutdown is just the latest reason to run it.