What Asgaros Forum is, and who it suits
Asgaros Forum is a free forum plugin for WordPress. You install it, create a few forums, and members post topics and replies using the accounts they already have. It aims to be simple, and for many sites that is the right ambition.
It suits a small or steady community: a club, a local group, a customer corner where the volume is modest. The owner wants a place to talk without learning a new system, and the members want something that looks like the rest of the site. That is a perfectly good brief, and a lighter forum meets it well.
Both plugins are forums on WordPress, so this is a closer comparison than most on this site. The question is not hosted against self-hosted. It is how much structure your conversations need.
The real difference: threads, or threads with structure
In a plain forum, every topic is a thread and every thread looks the same. That works until a pattern appears. Members start asking how-to questions, and the useful reply sits on page two of a long thread. Someone suggests a feature, and it vanishes into the same list as everything else.
Jetonomy gives each of those jobs its own space type. A Q&A space lets the asker or a moderator mark one reply as the answer. An Ideas space adds voting and a status roadmap. A Forum space stays a classic threaded forum, and Show & Tell is a short-form feed. See the guide to forum, Q&A and ideas spaces for how to pick.
Underneath, members earn trust. New accounts start with tighter limits that relax as they build a history, and there is a reputation score and a leaderboard. If you have never needed any of that, say so honestly: you probably do not need to move.
What it costs to run each
Both plugins run on the WordPress hosting you already pay for. Neither asks for a separate server, a second database or a different software stack, which is the quiet advantage they share over standalone forum software.
Asgaros is the lighter of the two on features, so there is less to configure and less to update. Jetonomy keeps its data in its own indexed database tables inside your WordPress database, and it uses an external object cache such as Redis or Memcached when your host provides one. On a small site you will not notice either.
The money side is plain. The Jetonomy core plugin is free, and Pro starts at $69 a year for one site. For the Asgaros side, check the vendor’s site for current terms. See pricing for what each tier includes.
Moving over: the Asgaros importer
This is the concrete part. Jetonomy has a built-in importer for Asgaros Forum, and it is one of only three importers in the product, alongside bbPress and wpForo. The migration and import page shows the screen, and the migration guide walks the whole process.
What comes across
- Each Asgaros forum becomes a Jetonomy space.
- Topics and replies, with their authors.
- Attachments.
- The forum hierarchy, so categories and sub-forums keep their shape.
What does not
- Redirects. The importer does not create them, so plan your own.
- Tags, subscriptions and reputation.
- Anything you customised in the old theme or in add-ons for the old forum.
Run it on a copy first
There is no dry-run mode for Asgaros. The safe route is a staging copy of the site: import there, check a sample of threads, then repeat the import on the live site in one clean pass. A second run does not create duplicates, because the importer skips what an earlier run already brought over. Take a database backup before the live run, so a bad result is a restore, not a clean-up job.
What the Asgaros importer does with each kind of content
The importer reads Asgaros Forum’s own tables, so it works as long as that data is in your database. It runs in batches with a progress bar, which keeps a large forum from timing out. The order is forums, then topics, then replies, then member profiles, then a final recount of the totals.
- Forums become spaces, and nested forums keep their parent.
- Topics arrive with their authors and original dates. Sticky and closed topics keep both states.
- Posts that were not yet approved come across as pending, so they land in the moderation queue instead of going live.
- Replies are linked to the topic they belonged to.
- Every author gets a Jetonomy profile.
If a topic or reply cannot be placed, because the forum or topic it belonged to was not imported, it is left out on purpose. The result screen counts these separately from real failures, so a gap in the numbers comes with a reason.
Uploads, and who can see what
Asgaros keeps uploaded files in its own folder rather than in the media library. The importer registers each file as a media item and links it to the imported topic or reply. That also means the files are safe if you later remove Asgaros. If a file cannot be found, the importer logs it instead of failing the whole run.
Access is the part that needs your attention. Asgaros stores who can read each forum in its user group add-on tables, and the importer does not translate those. Every imported forum arrives as a public, open space. If you ran restricted forums, make those spaces private or hidden after the import, or ask a developer to map them with a filter before the run. A private space can then use approval or invite links to let people in.
How a re-run behaves
The importer remembers every forum, topic and reply by its original Asgaros ID. Run it a second time and it recognises what is already there, reports those items as already imported, and adds only what is new. The count of already-imported items is kept apart from items skipped, so you can read the two differently.
That makes a staged launch practical. Import on staging, test, import on the live site, then run it once more just before you switch traffic across to catch recent posts. If a run is interrupted, the Import screen can resume it where it stopped, or start over.
What Asgaros does not get is a preview. The dry run is a bbPress-only option, and the command line refuses the flag for Asgaros rather than quietly importing for real. Testing means a staging copy and a sample of threads from every space.
What Jetonomy does not do for an Asgaros site
A simple forum has few moving parts, and it is worth being clear about what you would be taking on. Jetonomy is bigger, and some of that size is optional.
- No redirects from old Asgaros addresses. Map them yourself.
- No tags, subscriptions or reputation come across.
- Forum access rules are not translated, as described above.
- Several of the features people move for sit in Pro, including private messaging, reactions, polls and analytics.
- There is no live chat, voice or video.
The free plugin still covers the core: four space types, trust levels, a moderation queue, accepted answers and a REST API. You can run on that alone for as long as it fits.
Setting it up, step by step
For a small Asgaros site, the move is mostly a matter of order. Each step below is free unless it says Pro.
- Install Jetonomy on a staging copy and run the short setup wizard. It asks for a community address and a default community type, then creates your first space.
- Open the Import screen and read the notes about what will be brought across.
- Run the import and check a sample of threads.
- Fix access on any space that was restricted in Asgaros.
- Decide which spaces should be Q&A or Ideas rather than plain forums, and change the type where it helps.
- Add Pro only if a feature you need sits there, such as messaging or reactions.
A normal week, and a thirty day check
Running a small community is a few minutes at a time. Clear the moderation queue, answer or assign the questions without an accepted answer, and read the activity log if something looks off. The trust levels post explains how members earn more freedom over time, which cuts your queue as the community grows.
After the first month, check which spaces are used and merge the quiet ones. Ask members what they miss from the old forum, and decide whether it is a setting, a Pro extension or something to leave out. The guide to adding a forum to WordPress covers the structure choices in more depth.
Pro is optional, and the sensible approach is to wait. Run the free plugin for a few weeks, note what members actually ask for, and buy the extension that answers the most common request.
Data, privacy and ownership
Discussions live in Jetonomy’s own tables inside your WordPress database, and members are ordinary WordPress users. Personal data requests are handled with the export and erase tools WordPress already provides. Members can delete their own account and data. A developer can export everything over REST or WP-CLI.
The Jetonomy family on one WordPress site
Jetonomy is one of several separate, optional plugins from the same team, and they run on one WordPress site with one login. Each is installed, hosted and updated on its own, which is the trade against a hosted product that bundles everything in a single bill.
BuddyNext is the social layer: profiles, an activity feed and groups. With both active, the forum adopts BuddyNext’s look and BuddyNext owns the page header and navigation, with nothing to configure. On a BuddyNext site, BuddyNext owns messaging, so do not plan on Jetonomy messaging there. Details are on the BuddyNext partner page.
Learnomy is the LMS plugin. With Jetonomy Pro, a space can be gated by a Learnomy course or membership plan. Enrolling adds the member, expiry removes them, and their posts stay. See the Learnomy partner page.
Other pieces from the team run on the same kind of site: WP Career Board for a job board, Listora for a directory, Eventonomy for events with RSVP and capacity, WPMediaVerse for member media, and WB Gamification for points and badges. Each is a separate plugin that runs beside the forum. BuddyX Pro and Reign are themes from the same team, and Jetonomy adopts the active theme’s brand colour.
None of these is required, and the forum works fine on its own. You add a piece only when a job calls for it. The price of that choice is housekeeping: you install, host and update each plugin yourself, where a hosted platform would bundle it behind one subscription and one support desk.
Other alternatives worth a look
Asgaros is rarely the only plugin on a shortlist. Here is where each option tends to win.
- bbPress wins on sheer footprint and its tie to BuddyPress, and Jetonomy has an importer for it with dry-run support.
- wpForo wins if you want a heavily configurable classic forum with a long add-on list.
- phpBB wins when you want a separate, proven forum application and do not mind a second login.
- XenForo wins for a large, paid-for forum that justifies its own application and add-on market.
- Discourse wins when the forum is the whole product and you have the hosting or budget for it.
- Staying with Asgaros wins when nothing on this page describes a problem you actually have.
For the full range of options, see the comparison hub.
Who should stay with Asgaros Forum
Stay if your forum is working. A small community with steady posting, no need for marked answers and no plans for an ideas board gains little from a bigger plugin, and a move always costs an afternoon of checking.
Stay too if your site leans on an Asgaros add-on or a layout you have tuned by hand, since those do not travel through an importer.
Move when you see the pattern: the same questions asked again, feature requests going nowhere, moderators doing by hand what trust levels could do. Then the features overview is the place to start.