Asgaros Forum Import

Move your existing Asgaros Forum community into Jetonomy - forums, topics, replies, and user profiles - using the built-in Asgaros importer.

New to migration? Read the Migration overview first - it explains how to read the import screen (stat previews, status badges, the progress tracker) and the backup rule that applies to every import.

What You Will Learn

• What the Asgaros importer brings over and what it leaves behind
• How Asgaros forum hierarchy maps onto Jetonomy spaces
• How to start and monitor the import
• What to verify after the import

What Gets Imported

Asgaros Data	Imported As	Notes
Forums	Jetonomy Spaces	Forum name and description preserved
Sub-forums	Jetonomy Sub-spaces	Parent/child forum hierarchy is preserved
Topics	Jetonomy Posts	Topic title + first post content preserved
Replies (posts)	Jetonomy Replies	Imported as flat replies on the post
User accounts	Linked to existing WP users	Matched by WP user ID
Sticky topics	Pinned posts	Preserved
Closed topics	Closed posts	Preserved
Unapproved topics	Pending posts	Topics not approved in Asgaros import as pending
Inline images and attached files (1.8.0+)	WordPress media library + Jetonomy attachments	Downloaded from Asgaros and re-registered as attachments; images stay inline, other files show as a download link

Not imported:

• Asgaros topic tags
• Asgaros user reputation / points
• Asgaros likes / reactions
• Asgaros moderator assignments (assign Space Moderator roles manually after import)
• Asgaros subscriptions (replaced by Jetonomy follow/subscribe)
• Custom Asgaros meta fields (use the jetonomy_importers filter to extend)

Attachments (1.8.0+): If a file cannot be recovered - for example it is already missing from disk - the import still completes and tells you how many files it could not bring over (“N files could not be recovered and were left linked in the original post text”). That is a warning to check a handful of posts by hand, not a failed import. See the Migration overview for details.

Asgaros Data Structure Differences

Forum hierarchy - Asgaros keeps your forums and sub-forums in a single nested list. The importer creates one Jetonomy category (“Imported from Asgaros”) and one space per Asgaros forum, importing parent forums before their children so your sub-forums come across as Jetonomy sub-spaces.

Post structure - In Asgaros, a topic’s opening message and all its replies are stored together. The importer promotes the opening message as the Jetonomy post body and imports the remaining messages as replies.

For developers: Asgaros stores forums in one table with a parent_forum column (hence the parent-before-child import order), and stores the opening post plus all replies together in the forum_posts table.

Pre-Import Checklist

1. Back up your database. The importer reads but never modifies Asgaros tables, but a backup protects against any edge cases.
2. Activate Jetonomy and complete the setup wizard.
3. Asgaros Forum can be active or deactivated - the importer reads its tables straight from the database. Import before deleting it.
4. Disable page caching if active, to avoid stale data during the import.

Tip: For large Asgaros communities, run the import via WP-CLI to avoid browser timeouts.

Preview Before You Import

Always take a full database backup before you run the Asgaros import - that is your way to undo if you want to start over. There is no preview mode for Asgaros: only the bbPress importer supports a true --dry-run that counts records without writing them. The Asgaros importer always writes data, so a backup (not a dry run) is your safety net.

Heads up: The wp jetonomy import asgaros command refuses the --dry-run flag and stops with an error, because the Asgaros importer cannot preview. Nothing is imported when this happens.

Running the Import

1. Go to Jetonomy → Import in your WordPress admin.
2. Select Asgaros Forum as the source.
3. Click Import from Asgaros Forum.

The importer works in batches (forums, topics, replies, then profiles) and the progress bar advances as it goes. If it is interrupted, return to Jetonomy → Import and click Resume Import to continue from where it stopped, or Start Over to begin again. Either way, anything already imported is skipped, not duplicated.

Estimated Import Times

Community Size	Topics + Replies	Estimated Time
Small	Under 10,000	2 - 5 minutes
Medium	10,000 - 100,000	10 - 40 minutes
Large	100,000 - 500,000	1 - 4 hours
Very large	500,000+	Use WP-CLI

Running via WP-CLI

Run this from your server’s command line (SSH); on most managed hosts you point it at the WordPress install with --path. The valid source value is asgaros (lowercase) - if you mistype it, the command lists the sources it recognizes.

wp --path="/path/to/wordpress" jetonomy import asgaros

WP-CLI is the recommended way to import larger Asgaros databases - it is not subject to browser timeouts and prints an Imported / Skipped / Errors summary when finished.

Note: The --dry-run flag is refused for Asgaros (the command stops with an error). Take a backup first instead.

Post-Import Checklist

After the import completes:

• Visit your community home and confirm spaces match your old Asgaros forums
• Confirm that sub-forums appear as sub-spaces under their parent
• Open several posts from different spaces and verify content is intact
• Assign Space Moderator roles to your former forum moderators (moderator assignments are not imported)
• Go to Jetonomy → Dashboard → Quick Actions and click Flush Rules (the Asgaros importer does not flush them automatically, so this step is needed if new spaces return a 404)
• Consider deactivating Asgaros after confirming the import - it is no longer needed

Re-running an Import

Once Asgaros has been imported, its card on Jetonomy → Import changes to a Previously Imported badge showing the date and record count of the last import, and the Start button becomes Re-Import.

A re-run skips everything already imported and brings over only what is new, including new topics and replies in forums you imported earlier. The result tells you how many items were already imported and skipped. Content imported by an earlier Jetonomy version is recognised on the first re-run too. See Running an Import Again for the migration pattern and its limits.

What’s Next?

Now that your community is live, configure who can read it and how members earn trust.

General Settings →