How to Migrate From Circle to Your Own WordPress Site

You can move a Circle community to a site you own, but you do it by export, invitation and rebuild, because there is no Circle importer. Pull every export Circle offers, build the new community on staging, invite members from a CSV, and run both side by side until your regulars have moved.

This guide covers that path using BuddyNext, a WordPress community plugin. We build it, so we have tried to be fair to Circle, which is a polished product.

Can you migrate from Circle to your own site?

Yes. Circle gives you more to work with than some hosted platforms, and that helps. But nothing here is automatic.

The free BuddyNext Importer reads BuddyPress and BuddyBoss communities straight from the database. It does not read Circle. Our migration hub covers those two moves. For Circle the work is an invitation plus a rebuild.

Nothing you do on the new site deletes your Circle community. It stays as it is until you close it. The real risk isn’t losing data. It is losing people by moving badly, so most of this plan protects them.

Should you leave Circle?

First, where Circle genuinely wins. Be honest about these before you spend a month on a move.

• Hosted polish and zero maintenance. No servers, no plugins, no updates. Circle runs it all and it looks good out of the box.
• Batteries included. Community, courses, live streams and events, payments and automations are all native.
• A mature branded app for iOS and Android on its higher tier. BuddyNext has an installable web app today, and native apps are in development with no date.
• A fast start for a non-technical creator. Sign up, brand it, invite, and you’re live the same afternoon.
• Payments wired in from the start, so charging for access is a few clicks.

What a move buys is ownership. Your members, posts and messages sit in your own WordPress database, so no vendor can reprice or re-tier the ground under you. BuddyNext charges no per-member fee and takes no cut of what members pay you. Your costs are hosting, an optional Pro licence and your payment processor’s fee, which you’d pay on any platform. Circle’s own help and pricing pages show what it charges, so read your current plan there.

If the all-in-one bundle is what you value, say so to yourself before you move. If you’d rather own the stack, read on. Our BuddyNext vs Circle comparison goes through the differences, and the Circle alternative page covers the cost side.

Step 1: Export everything Circle allows

Circle’s help centre describes several exports, and they cover different things. Pull each one that applies to you before you touch the new site. Check what your own plan allows, since some admin features sit on higher plans.

Member CSVs per space or space group. On a space’s Members tab an admin can use Download CSV, and the file is emailed to the admin address. It carries name, email, role, joined date and last active date. Space groups work the same way.

The member list from Manage audience. That page lists members with filters such as tag, role, space access, paywall subscription and join date. Circle also documents a member CSV export, so look for the export option there and confirm which filters it respects.

A full community data export. Only admins can request it, by emailing Circle support. It arrives as CSV files covering members, spaces, posts, comments and events. Request this first, since it is the slowest item. Then download the files you can get yourself while you wait.

Paywall subscriptions and transactions. Circle documents a separate export of subscription and transaction data. If you charge for access, this is the record of who pays and when.

Event attendees. The attendee list downloads as a CSV. It includes only people who confirmed they were going, not people who were invited and never replied.

Then open every file once and check it. The posts file is the most useful thing you’ll get for rebuilding, because it holds the text of every post with its author and date.

What the exports leave out

The posts and comments files don’t include uploaded media. Images and files need saving separately. Do the same for course videos, documents and anything members attached.

Keep your own copies of lesson files from the source, not links to them on Circle. If you made a video in an editor, keep the original. Re-uploading from your own files is much easier than rescuing a copy from a platform you’ve left.

Step 2: Decide what moves, merges or retires

Don’t copy a community you’ve outgrown. List every space and group in Circle, and decide one of three things for each: move it, merge it into another, or retire it.

Write the list down and keep it. A few questions help.

• Which spaces have had real conversation in the last three months?
• Which are quiet because they were a good idea that never took off?
• Which paywalled spaces make the money?
• Which automations, workflows and integrations depend on a specific space?

Most communities find that a few well-run rooms work better than a long list of dormant ones. A move is a fair moment to prune.

Step 3: Build the new site on staging

Build on a staging copy, or a fresh WordPress install, not on your live site.

You’ll need WordPress 6.9 or newer, PHP 8.1 or newer, MySQL 5.7 or MariaDB 10.3, and pretty permalinks. A PHP memory limit of 512 MB is recommended once the full family of plugins is active. Install and activate the free BuddyNext plugin. It creates the community pages and prepares its storage on activation, and the free version needs no licence key.

Add BuddyNext Pro if you charge for access. Its licence key gates updates only and never locks features.

Then settle three basics before you invite anyone.

1. Registration mode. Choose Invite Only if your Circle community is paid or private, so your invitations are the only way in. Otherwise Open works.
2. Email delivery. Send a test invitation to yourself and confirm it reaches the inbox. Use a proper mail-sending service.
3. Sign-in options. Social login with Google, Facebook, GitHub, Discord or Apple is optional. Set up each provider you want. It saves people a password on the first visit.

Step 4: Map Circle to BuddyNext

Circle organizes a community into spaces and space groups. BuddyNext uses spaces too, so the vocabulary is familiar. Here is how the pieces line up.

• Spaces become spaces. Each has its own feed, members, rules and moderators.
• Space groups become categories, or a parent space with sub-spaces. Sub-spaces go two levels deep.
• Visibility. Every space is Open, Private or Secret. A secret space stays out of search and out of the directory.
• Paywalled spaces become Pro membership plans. A plan can open one space or several, and a space can be opened by several plans.
• Course content becomes Learnomy courses. Learnomy is a separate course plugin, and the bridge to BuddyNext is in BuddyNext Pro.
• Events become Eventonomy events. Again, the bridge is in BuddyNext Pro. BuddyNext doesn’t host live video, so keep the tool you use for live sessions and put its link in the event.
• Automations. BuddyNext Pro accepts signed requests from Make, Zapier and n8n to grant, extend or cancel a plan, and it can send outbound webhooks. Rebuilding a long chain is real work, so list yours now.

The mapping is the easy part. The harder part is the feel. Circle bundles live rooms, workflows and a branded app in one place, and BuddyNext spreads the same jobs across plugins you choose. That freedom costs setup time.

Step 5: Rebuild the posts that matter

Your old posts won’t import. The posts export is for reference, not for loading in.

Choose the evergreen ones: onboarding posts, the answers people keep asking for, and the rules. Post them as announcements or discussion threads. Pin the welcome post in the first space, and link to the others from your welcome message.

Where you want answers to stay findable, Jetonomy gives a space a Discussions tab. It’s a separate forum plugin from the same team, with a free bridge. Use it for the Q&A that a feed buries.

A developer can script a bulk load of an archive through the BuddyNext REST API if it truly matters. That is custom work, not a feature, and most communities don’t need it.

Step 6: Set up payments and plans

If Circle charges members, you’ll need a plan for each paywall. Plans are a BuddyNext Pro feature.

1. Create a plan for each Circle paywall, with its price, billing schedule and optional trial.
2. Connect Stripe or PayPal. BuddyNext charges the same amount whichever gateway a member uses.
3. Attach each plan to the spaces it opens.
4. Make a coupon if you want to give people who move early a founding discount.

You can create plans and grant access by hand before any gateway is connected. That is a gentle way to run a few founding members through while you check the structure.

Test the full flow as a stranger. Sign up, subscribe with a test payment, confirm the gated space opens, then cancel and confirm access closes cleanly. Pro is $149 a year or $399 once for a single site; see the pricing page.

Step 7: Invite members from a CSV

Now bring your people across. Invitations are in the free plugin, under BuddyNext, Members, Directory, Invites.

Prepare a CSV where each line is email or email,first_name. The Circle member CSV already has name and email, so a small edit gets you there. Choose Send bulk invitations, pick the file and send.

The rules that matter:

• Up to 500 rows per upload. Split longer lists into batches.
• An address with a pending invite is skipped, so re-uploading never double-invites.
• Each link is tied to its email address.
• Invitations expire after 7 days by default. You can resend or revoke.
• The Invites tab shows Pending, Accepted, Expired and Bounced, each filterable.

Other ways in, for people you can’t email: a space invite link, which can expire after a day, a week, a month or never and can have a use cap; and auto-join, so a new member lands in your welcome space and any other space you choose.

Send in waves, starting with a small group of active members who will tell you what breaks. Then announce the date and invite everyone else in batches, so the first week is calm and your email service doesn’t throttle the mail.

Step 8: Run both side by side

Don’t switch off Circle on the day you launch.

• Stay on your current Circle plan until the new site is where members answer each other. Check what a downgrade or cancellation changes for admins and exports before you do it.
• Put the new link at the top of the old community and in your Circle emails, and give the date the old one stops.
• After launch, answer questions only in the new place. Redirect people politely rather than answering twice.
• Hold paid members until last. Each payer subscribes on the new site, or you record a payment they’ve already made with the Add order form in BuddyNext Pro. Agree the old billing end date with each one so nobody pays twice.
• Switch Circle to read-only, or archive it, on the date you gave, once your active members have moved.

What tends to go wrong

A few problems come up again and again in a move like this, and all of them are avoidable.

• Inviting everyone on day one. The first batch finds every rough edge. Let a small group find them, not your whole audience.
• Forgetting the media. The text export is complete enough to feel finished, and then someone asks where the images went. Save uploads before you close anything.
• Letting two homes run forever. A date and a reason keep the move from stalling. Without them, half the community stays put and the other half wonders where everyone went.
• Double billing. A member who pays on both sides for a month feels cheated. Agree each payer’s end date before you ask them to subscribe again.
• Skipping the phone test. Most members will sign up on a phone. If the invitation email or the sign-up form is awkward there, you’ll hear about it in a week.

What you get instead, and which tier it is

A short map of what the new site includes.

• Free. A feed with polls, spaces, profiles with custom fields, a directory with member types, notifications, hashtags, reports, a moderation queue and a REST API.
• Free, with companions. Direct messages run on WPMediaVerse, and discussion forums on Jetonomy. Group conversations need WPMediaVerse Pro.
• BuddyNext Pro. Memberships with monthly or annual billing, coupons, invoices, gated spaces, broadcast email and drip sequences, scheduled posts, analytics, member labels and live updates through a Pusher-compatible server.

A realistic timeline

Treat this as a shape, not a promise. A small community moves faster than one with a large course library.

A launch checklist

• The data export has arrived and every file has been opened.
• Uploaded media and course videos are saved from your own sources.
• The new site runs on live hosting, with a backup you’ve restored once.
• Spaces exist with the right privacy type on each.
• Every paywall has a plan, and a test purchase works.
• A first CSV batch has gone out and been tested on a phone.
• The date and the new link are on Circle, pinned.
• Someone owns moderation on the new site.

Work out the cost with your own numbers

No figure here stands in for yours. Add up what Circle charges you in a year, including any transaction fee on payments. Then add hosting, the BuddyNext Pro licence if you need payments, and your payment processor’s fee, which you pay on any platform. Put your own time on the other side of the sum.

Where to go from here

The live demo is a seeded BuddyNext community with owner access, open for four hours, and it asks for an email. The self-hosted community platform guide covers the upkeep side. If you’re leaving Skool too, read the Skool migration guide, and see free vs Pro for what each step needs.