BuddyNext - community engine for WordPress

Migrate

Moving an existing community.

Migrating is not a button, and anyone who tells you otherwise has not moved a real community. There are two different problems here. If you are on BuddyPress or BuddyBoss, your members are the part that does not move at all, because BuddyNext runs on the WordPress accounts you already have, and a free importer brings the history across. If you are on Mighty Networks, our team moves it for you through its API. If you are on another hosted platform, you export, rebuild and invite, or you ask our team to do it for you.

Path one: a WordPress source

BuddyPress and BuddyBoss: the importer path.

Both are WordPress plugins, so your members already have WordPress accounts and the old community's data sits in your own database. BuddyNext Importer is a free companion plugin that reads those tables and writes into BuddyNext, then reports exactly what arrived against what the source held. The docs cover it in full, and each guide below is written for someone who has already decided.

Rehearse on a staging copy first: an import cannot be undone from inside the plugin, only by restoring a backup. Running BuddyPress or BuddyBoss alongside BuddyNext on a live site is not supported, so deactivate the old plugin when BuddyNext goes live. The full walkthrough is in the migration docs.

On the WordPress path

What carries over on both.

Every WordPress login
BuddyNext runs on top of standard WordPress accounts, so members keep the same username, email, password and role. Nobody re-registers.
Roles and capabilities
Admins stay admins and editors stay editors. BuddyNext respects the roles already on the site.
Your regular WordPress content
Posts, pages and the media library are untouched. This is a community layer changing, not the site underneath it.

The specifics differ by platform. Each guide lists exactly what its importer moves and what it does not, and those pages are the source of truth over this one. None of this applies to hosted platforms, which have no WordPress accounts behind them.

Before you commit

Four things worth checking on a staging copy.

None of these are blockers. They are the things that turn a short migration into a long one when nobody looked first.

Your theme
A theme built tightly around one community plugin may need work. Check it on a staging copy before you touch production.
Add-ons without an equivalent
List what you actually use rather than what is installed. Some of it will map to BuddyNext core, some to a companion app, and some will have no equivalent yet.
Custom code
Anything written against another plugin's functions or hooks needs review. The REST API and hooks are documented, so porting is mechanical, but it is not automatic.
The size of your history
A long activity history takes longer to import than a short one. Worth knowing before you pick a maintenance window.

BuddyNext replaces the community layer, not a whole suite. Forums, media, courses, jobs and listings are separate apps in the same family, so check your add-on list against that page rather than assuming a like-for-like swap.

Path two: a hosted platform

Mighty Networks, Circle, Skool and Discourse: moved for you, or export, rebuild, invite.

Their data lives on someone else's servers rather than in a WordPress database, and there are no WordPress accounts to carry over. Mighty Networks is moved by our team through its API. For Circle, Skool and Discourse, you export what the platform allows, build the new structure on a staging copy, and bring members across with a bulk CSV invite, or ask our team to help.

What the free plugin gives you for the move

Bulk invites by CSV
An email and an optional first name per row, up to 500 rows per upload, with resend and revoke. It lives on the Invites tab under Members.
Space invite links
Links that expire after a day, a week, a month or never, with an optional cap on uses, which suit a post in the community you are leaving.
Auto-join at signup
Each new member lands in your welcome space and, if you choose, the spaces for their member type, so the new site is not empty on day one.
A member export of your own
The Members screen exports ID, login, email, display name, registration date and suspension status, so the next move is easier than this one.
Membership plans on Pro
Paying members subscribe again on a Pro plan, because a subscription cannot be taken over. Pro plans take Stripe or PayPal and coupons, so a founding discount is a coupon you create. When our team migrates a Mighty Networks community, members are seated on the matching plan from your payment records instead.

Longer write-ups for a few of these sit in the guides: Skool, Circle, Mighty Networks and Facebook groups.

Rather not do it yourself

We can run the move with you.

For a hosted platform, the team behind BuddyNext can do the migration for you: the exports, the rebuild on a staging copy, the invitations and the cut-over date. Tell us where your community lives today, roughly how many members and spaces it has, and whether members pay. We reply within one to two business days and tell you what is realistic for your community before anything starts.

Questions

What people ask before moving.

Will my members have to sign up again?

No. BuddyNext runs on standard WordPress user accounts, so every member keeps the same username, email, password and role. That is true of both moves, and it is the single biggest worry people arrive with.

Can I run BuddyNext alongside my current community plugin while I test?

Test on a staging copy rather than running two community layers on one production site. Two plugins competing for the same screens and the same member data is a poor test of either, and a staging copy costs you an afternoon instead of a rollback.

What happens to my theme?

Regular WordPress themes are fine. A theme designed tightly around one community plugin is the case to check first, because it may be styling screens that no longer exist. BuddyX and Reign are built for BuddyNext if you would rather not solve that yourself.

How long does a migration take?

The import itself is usually short. The planning around it is the real cost: auditing which add-ons you use, checking custom code, and deciding what you are not carrying across. Budget for the audit, not for the button.

Does BuddyNext replace everything my current setup does?

It replaces the community layer: feed, spaces, members, messaging and moderation. Forums, media, courses, jobs and listings are separate apps in the same family rather than parts of one plugin, so check the integrations page against your list before you assume a like-for-like swap.

Is there an importer for Circle, Skool, Mighty Networks or Discourse?

Not a self-serve one. The free BuddyNext Importer reads BuddyPress and BuddyBoss, which are WordPress plugins, and nothing else. For Mighty Networks, our team runs the migration for you through its API. For Circle, Skool or Discourse you export what the platform allows, invite members to new accounts and rebuild the content worth keeping, or ask us to help.

Can your team do the migration for me?

Yes. For Mighty Networks it is a done-for-you migration through its API. For other hosted platforms we plan it with you. Send the details through the contact page: where the community lives, roughly how many members and spaces, and whether members pay. We reply within one to two business days.

Try it before you move anything.

The free core installs on a staging copy in a few minutes, which is the cheapest way to answer most of the questions above. Coming from a hosted platform and short on time? Ask us to run the move.

Keep reading

What customers say on Trustpilot

WBComDesigns is amazing!

WBComDesigns is amazing. The WP plugins and themes are of top notch quality with lots of features and updated very frequently. Supports are very responsive and helpful. I use Reign with TutorLMS, and the experience is surprisingly smooth. The recently launched BuddyNext Pro and MediaShield Pro are…

Hoang PhanVN