Hosted forum going down? Move it to WordPress

If your forum lives on a hosted platform, you rent it. The posts, the member list and the look of the site all sit on someone else’s servers, and you can only take out what their export screens allow. For many hosted forums that is very little, so the time to find out is before the site goes down, not after.

This post is for admins of hosted boards who want a way out, or at least a safety net. It covers what you can usually get out, what to save today, and how to move to a forum you host yourself on WordPress. It is also direct about the part nobody likes: there is no one-click import for most hosted forum software, so the realistic move is a fresh start with the old board kept as an archive.

What you own on a hosted forum, and what you don’t

You own your community: the people, the culture and the habit of showing up. You do not necessarily own the database that stores their words. That gap is the whole problem.

Hosted forums differ, so check your own platform’s help pages rather than trusting a general claim. One verified example: ProBoards does not give owners a way to download or back up a whole forum. Staff replies on ProBoards’ own support forum, in its threads on downloading a backup of an entire forum and on forum backups, say as much. Members can export only their own posts and private messages, as a CSV file, from their account settings.

Read that twice. It means a board with ten thousand threads has no owner-level export. The only copy that leaves the platform is whatever individual members choose to download about themselves.

This is not about any one provider, and most hosted platforms run well for years. Hosted forums go down for ordinary reasons: a provider has a bad day, a company changes plans, an account gets suspended by mistake, a payment lapses. The point is that when it happens, your options depend on what you saved beforehand.

Sort your platform into one of three buckets

Use this to decide how urgent your situation is. Fill it in with facts from your own provider’s documentation.

• Bucket 1, full export for the owner. The platform lets the admin download all threads, posts and members. You are in good shape. Download it on a schedule and test that the file opens.
• Bucket 2, partial export. You can get some data (members, or a database dump on a paid plan) but not everything. Find out exactly what is missing and plan around the gap.
• Bucket 3, no owner export. Nothing for the admin, as with the ProBoards case above. Your plan is to preserve what you can by other means and move sooner rather than later.

If you cannot tell which bucket you are in, that is itself the answer. Ask the provider in writing, and keep the reply.

Self-hosted software you run on your own server is different again. If you run phpBB, myBB or an old vBulletin on a server you control, you have the database and the files, so your problem is software age and security, not access. That is a separate decision; the phpBB comparison covers what staying versus moving looks like there.

What to save today

Do this in one sitting, this week. None of it needs a migration decision.

1. Write down every admin login and the email on the account. If the owner account’s email is dead, recovery is harder than anything else on this list.
2. Export whatever the admin panel offers. Member lists, settings, theme or template code, custom CSS, badge and rank definitions. Save each as a file, not as a bookmark.
3. Screenshot the structure. Capture the category tree, the forum descriptions, the rules page, the welcome post and the member group setup. You will rebuild this by hand, and screenshots beat memory.
4. Keep a list of your best threads. Open your analytics or search console, sort by traffic, and note the top 50 URLs. Those threads are your most valuable content and the first ones to rescue.
5. Save the top threads as files. Print each one to PDF from the browser, or save the page. It is manual and dull, and it works on every platform, including ones with no export.
6. Ask members to export their own data. If your platform lets members download their own posts, post a short notice asking your most active people to do so. On ProBoards that is the per-member CSV mentioned above.
7. Note your domain and DNS access. Know where the domain is registered and who holds the login. If the forum runs on your own domain, you can point it somewhere else later without losing the address your members know.
8. Record your email list or contact route. If you can reach members outside the forum (a newsletter, a Discord server, a social page), write down how. It is the fastest way to tell people where you moved.

Item 5 is the unglamorous one, and it is the one that saves a community’s search traffic. A saved copy of a top thread lets you republish the answer later.

Option one: stay, and harden what you have

Moving is not always right. Staying is reasonable if your platform is stable, your board is small, and the content is not what draws people.

If you stay, do the following:

• Run the “what to save today” list above every few months, and put a reminder in your calendar.
• Keep a second admin account with a different email, so one lost inbox does not lock you out.
• Keep a pointer elsewhere. A simple page on a domain you own that says “our forum is at this address” costs almost nothing. If the board moves or vanishes, you change one link.
• Turn on whatever spam protection your host offers, and review it after every platform upgrade. If new spam arrived right after an upgrade, check whether a setting was reset.

Staying also means accepting the limit: if there is no owner export, you cannot rebuild your board’s history from a backup. Be honest with yourself about whether that risk is acceptable for the size of the community.

Option two: a forum you host yourself on WordPress

Moving to self-hosting changes who holds the data. On WordPress, the content lives in your own database on your own hosting account, and you control backups. You can export, copy, restore and move it. That is the real difference, more than any feature list.

It also costs you something. You become responsible for hosting and updates, and for backups and moderation too. A managed WordPress host reduces that work, but it does not remove it.

Jetonomy is a forum plugin for WordPress, and it is what we build. If you want to see what it does before reading on, the WordPress forum plugin page covers the overview. Everything below is limited to what the code does today.

Two things matter for your situation:

• Your community content is stored in your WordPress database, so your normal backup routine covers it.
• Member data hooks into WordPress’s built-in privacy tools. The plugin registers exporters and erasers with WordPress’s personal-data export and erasure screens, so a member’s request for their data goes through the same place as any other WordPress site.

If you are weighing this against a chat tool, our note on moving a community off Discord explains the tradeoff: chat is fast, but old answers sink and search is weak. Many admins who write that “old-school forums beat Discord for searchable knowledge” are describing exactly this.

The honest part: there is no importer for your old board

Here is what the plugin can and cannot import. The built-in importers are for three sources only: bbPress, wpForo and Asgaros Forum. Developers can register additional sources through a filter, but nothing for hosted platforms ships in the box.

So, to be plain:

• ProBoards, Forumotion, phpBB, vBulletin and myBB have no Jetonomy importer.
• Moving from any of them is a fresh start on WordPress, not a conversion. If you are on ProBoards, the ProBoards alternative page compares the two side by side.

That is not a failure of your situation. A fresh start with a read-only archive is how many boards actually move, because it forces a clean-up that old boards need anyway. It is also the only route that is fully honest about the effort involved.

The fresh-start plan, step by step

The plan keeps your old board alive and readable while the new one grows. It assumes your old board still works. If it is already offline, skip to step 3 and use the files you saved.

1. Freeze the old board. Post an announcement that the board is moving. Where your platform allows it, set categories to read-only so threads stop growing on the old side.
2. Link the archive. Keep the old address live and put a banner or pinned post at the top pointing to the new home. Your old threads keep their search value while the new forum builds its own.
3. Install WordPress and the forum plugin on a host you control. Set up SSL and backups before you invite anyone.
4. Create your spaces. Rebuild your top-level structure with fewer categories than the old board had. The space design section below helps you choose.
5. Seed the top threads by hand. Recreate your 20 to 50 best threads as fresh topics, with the question and the best answer. Credit the original author in the text and link back to the archived copy.
6. Announce the move through every channel you saved in the checklist above.
7. Create accounts or open registration. Members need an account on the new site. See the next section.
8. Run both sites for a set period, then decide when to retire the archive or leave it up permanently.

Seeding the top threads

This is manual work, and it is worth doing. A forum that opens empty feels abandoned, and the first visitors decide quickly.

For each thread you rescue:

• Write a clear title that matches how people search, not how the old board titled it.
• Put the question in the first post and the best working answer in a reply.
• Add a short line such as “Originally discussed on our old board” with a link to the archive.
• Post it from a staff account, so you do not impersonate former members.

Do not paste whole threads of chatter. Keep the question, the fix and the context. You are building an index of useful answers, not a museum.

Bringing members over

People do not follow a forum move on their own. They follow a message from someone they trust, with a clear action to take.

Your announcement should say four things: where the new forum is, why you are moving, what happens to the old board, and what the member needs to do. Keep it short and put it in every place members already look.

Then give them a path in:

• Open registration. Let members sign up on the new site. Tell them to reuse the same display name so old friends recognise each other.
• Create accounts for key people. WordPress lets you add users yourself from the Users screen. For your most active members and your moderators, creating the account in advance removes the first hurdle.
• Make the first week active. Staff should post and reply every day at the start. A new forum fills when someone is clearly home.

Member passwords do not come across from a platform you cannot export from, and you should not try to move them. New accounts with a fresh password are the clean answer.

A note on privacy: Jetonomy’s spaces can be set to private so that joining means a request or an invite. That is useful for a members-only board, but do not treat a hidden space as a security guarantee. If content must be locked down, test access as a logged-out visitor and as a regular member before you launch.

If you are coming from bbPress, wpForo or Asgaros

If your old forum was one of these three, the importer applies. Here is what it does and where it stops, checked against the code.

What it does:

• Each old forum becomes a space, and topics and replies come across.
• You can run the import from WP-CLI, for example wp jetonomy import bbpress.
• A re-run adds only what is new, so you can import once, keep the old forum open, and import again just before you switch.

What it does not do:

• No redirects. No importer contains redirect code Old URLs do not forward to new ones, so set up your own redirects on the web server or with a redirect plugin if search traffic matters.
• No tags, subscriptions or reputation. Those do not come across.
• Dry run is bbPress only. --dry-run works for bbPress. For wpForo and Asgaros the command refuses a dry run rather than quietly importing for real.

Always take a full backup first. The importers read your old tables and add records to the new ones, and the additions are not automatically undone. The migration feature page and the migration guide walk through the screens.

Design your spaces so knowledge stays findable

The reason people miss old forums is that answers stay put. Design for that from the first day, and your new board will earn search traffic instead of losing it to a chat tool.

Jetonomy has four space types: Forum, Q&A, Ideas and Show & Tell, which appears as Feed in the admin. Pick the type by the job the space does.

Space	Best for
Forum	Open talk
Q&A	Fixes and how-tos
Ideas	Requests and votes
Show & Tell	Member work

For a board that exists to hold knowledge, two of these matter most.

Q&A for problems with answers. In a Q&A space the asker can mark one reply as the accepted answer, so the working fix sits first for anyone landing from search. Accepting an answer is a Q&A feature only. The accepted answers page shows how it looks.

Forum for open conversation. Opinion threads, introductions and chatter belong in a Forum space, where there is no single right answer to elevate.

A few rules that keep a new board clean:

• Fewer spaces than you think. An old board with 40 forums usually needs 6 to 10 spaces. Merge until each one has a clear purpose.
• One purpose per space. If you cannot say in one sentence what belongs there, split it or fold it into another.
• Q&A where you used to have “Help” and “Support”. Those old categories were really question lists.
• Pick one place for each topic. Members post where they think it belongs, so make the choice obvious in the space description.

The forum, Q&A or ideas guide goes deeper on choosing, and the spaces and categories page covers the structure.

On search engines: the free plugin outputs QAPage structured data for Q&A topics and DiscussionForumPosting for forum topics. That helps search engines understand the content. It does not guarantee rankings, so treat it as groundwork and not a promise.

Be aware too that the plugin’s REST search uses MySQL full-text queries. That works well for ordinary community sizes, but if you have a huge archive, test it against your own content before you rely on it.

Spam defences that exist in the code

Boards that got hit by spam after an upgrade will want to know what the new setup does by default. These are the layers that exist, checked against the code.

• CAPTCHA. You can choose Google reCAPTCHA v3 or Cloudflare Turnstile, or leave it off. The default is off, so turn it on and add your keys.
• Trusted members skip the check. Members who reach Trust Level 2 skip CAPTCHA, so your regulars are not bothered.
• New-account rate limits. A brand-new member (Trust Level 0) is limited to 3 topics, 10 replies and 5 votes per day. Level 1 and above are exempt. That slows a spam run on a fresh account.
• Akismet. If the Akismet plugin is active with a valid key, posts and replies are checked against it. Admins and moderators are not checked.
• Member reports. Members can flag content, and moderators work through a queue of pending flags.
• Content rules (Pro). Jetonomy Pro’s Advanced Moderation extension can apply a rule action of flag, hold, block or spam to matching content.

Trust levels deserve one clear caveat. They act as a ceiling on what a member can do and never grant edit, close or pin powers to ordinary roles. Moderation powers come from roles you assign, not from a member’s post count. Our trust levels post explains the model.

No stack stops every spammer. Layer two or three of these, review what gets through, and adjust.

A launch checklist

Run this before you announce the new forum. Tick each line.

• Backups run and a test restore has worked.
• SSL is on and the site loads on a phone.
• CAPTCHA keys are entered and a test post goes through.
• Akismet is active, if you use it.
• Spaces are created, each with a one-sentence description.
• Q&A is used for problem-and-answer topics.
• 20 to 50 top threads are seeded by hand, with links to the archive.
• The old board shows a banner pointing to the new address.
• Moderators have accounts and know the report queue.
• Registration works, and a test signup completes.
• The announcement is drafted and ready for every channel.
• Redirects are set for any old URLs that matter.
• You have tested the forum as a logged-out visitor and as a new member.

What to do this week

Pick the smallest step that matches your situation.

If you are on a hosted board with no owner export, do the “what to save today” list now and write the announcement draft, even if you never send it. If you are weighing a move, install WordPress on a test host, create two or three spaces and seed ten threads by hand. If you came from bbPress, wpForo or Asgaros, back up, run the importer on a staging copy and check the result before touching the live site.

Either way, you end up with a copy of your community that you hold. That is a better position than waiting to see if the next export screen ever appears.