We run Dating Partners and DatingAPI, and both are run by the same group as this site. If you leave WordPress, a website can move to Dating Partners, and an app with its own members can move to DatingAPI. This page covers WordPress dating sites built on a dedicated dating plugin such as WP Dating or Rencontre, or on a BuddyPress community with a dating theme such as Sweet Date or Gwangi, often with Paid Memberships Pro for payments. Vendor details come from their own pages, read on 21 November 2026. For moving off any script in general, see moving from a self-hosted script.
Where does a WordPress dating site keep its member data?
A WordPress dating site keeps its member data in your own MySQL database, split between WordPress's core tables and the tables each plugin adds. WordPress says the wp_users table stores the information about each account, and wp_usermeta holds extra details per account. The wp_ prefix is the default and can be changed, so check wp-config.php for yours.
| Part of the site | Where its data sits | What to know when you export |
|---|---|---|
| WordPress core | wp_users (logins, emails, password hashes) and wp_usermeta (extra details) | Every member has a row here, whatever plugin you use |
| BuddyPress profiles (used by Sweet Date and Gwangi) | bp_xprofile_groups, bp_xprofile_fields and bp_xprofile_data | Profile answers sit in one table, linked to field names in another |
| BuddyPress messages | bp_messages_messages, bp_messages_recipients, bp_messages_meta and bp_messages_notices | Conversations need both the message and recipient tables |
| WP Dating | Its own member base; it says it is not compatible with BuddyPress | Table list not published; ask them |
| Rencontre | Its own records, linked to WordPress accounts | Lists member import and export as CSV files, including photos |
| Paid Memberships Pro | pmpro_memberships_users, pmpro_membership_orders and pmpro_subscriptions | Records the gateway and subscription IDs; orders hold the last four card digits, not card numbers |
| Photos | Image files on your server | Copy the files as well as the database |
SeventhQueen, which sells Sweet Date, says in its item comments that the theme's matching is built on BuddyPress profile fields, and Themosaurus describes Gwangi as a BuddyPress community theme. So on those sites, the profile answers you need are in the bp_xprofile tables. Our dating site database schema guide explains how these pieces usually fit together.
What can you export from a WordPress dating site?
You can export everything, because the database and files are on your own hosting. Take a full database export with phpMyAdmin or your host's backup tool, and a copy of the uploads folder. WordPress's built-in Tools, Export screen is not the right tool: it creates an XML file designed for moving posts, pages, comments and similar content between WordPress sites. Plugin tables such as profile answers, messages and memberships need the full database export.
Clean the data before you send it anywhere:
- Delete dummy profiles. WP Dating's FAQ says its 500 and 1,000 demo profiles are randomly generated to "make it look active to new visitors", and that admin replies can be sent on behalf of dummy profiles. The CMA tells dating businesses not to create their own profiles to communicate with customers without making it clear and prominent that they are provider generated. Remove them all, and any messages they sent.
- Remove test and duplicate accounts, and decide what to do with long-inactive ones.
- Keep safety records: reports, blocks and banned accounts, so known bad actors do not return.
Then ask the new platform for its import format and send a small sample first.
What happens to passwords and subscriptions?
Passwords can move only if the new platform can check WordPress password hashes, and subscriptions must be cancelled at your payment gateway. WordPress stores passwords as a hash in wp_users.user_pass. Since version 6.8 it uses bcrypt, with hashes starting $wp$2y$; older passwords stay in the previous phpass format until the member next logs in. A database will often hold both, so ask the new platform whether it can read both formats or will ask members to reset.
Card numbers are not in your WordPress database. Paid Memberships Pro records which gateway took each payment and the subscription ID, but the recurring payment itself runs at the gateway, such as Stripe or PayPal. If the new platform uses a different processor, Stripe for example says processors can take from a few days to several months to produce a card export, never to send card details yourself, and that subscriptions cannot be imported and must be recreated. Cancel each old subscription at the gateway once the member's new one is active, or members will be billed twice. On Dating Partners, which runs its own payments, members re-enter their card details when they next pay.
What should you ask for in writing before you move?
Ask each supplier in writing for the facts that set your dates and your risks.
- Your dating plugin vendor: the list of tables it uses, any export tool, and whose developer account holds any branded app. WP Dating's terms say its licence covers one domain and is not transferable without its written approval, which matters only if you sell the old site.
- Your theme vendor: whether the theme stores anything outside BuddyPress or WordPress tables.
- Your host: your renewal date, how to take a final full backup, and when your data is deleted after you cancel.
- Your payment gateway: whether card data can be released to a new processor, the fee and the timescale, and how to cancel subscriptions in bulk.
- Chat, video and email add-ons: whether they hold message data on their own servers, and their notice periods.
- The new platform: its import format, how it treats passwords, photos and subscriptions, and a written timetable.
How do you protect your search rankings when leaving WordPress?
Map every indexed URL to its new equivalent and redirect each with one permanent 301 redirect on the day you switch. WordPress sites often rank for blog posts and guides as well as the dating pages, so decide first whether that content moves or stays. Watch for redirect chains: a WordPress site that already redirects to https or to www can end up with two or three hops, so point each old URL straight at its final address. Google recommends server-side permanent redirects, no chains, and keeping redirects "for as long as possible, generally at least 1 year."
What happens to apps built for a WordPress dating site?
Check whose store listing your members are using before you plan anything. WP Dating's FAQ says its VIP plus apps package includes "the general WP Dating app under the WP Dating name", so members on that app are on a listing you do not own and cannot move. Its personalisation package publishes an Android app under your brand on Google Play, and WP Dating says it helps create the developer account; confirm that the account is in your name. If you own the listing, a new platform can ship its version as an update.
DatingAPI rebuilds existing apps on its platform under your own store listing. It is meant for apps that already have members, not for a first launch.
What is a realistic timetable for leaving a WordPress dating plugin?
A realistic timetable is four to eight weeks for a website, and about three months or more for an app. The slowest parts are usually untangling plugin tables and the payment gateway.
| Stage | Website | App | Notes |
|---|---|---|---|
| Inventory and questions | Weeks 1 to 2 | Weeks 1 to 2 | List plugins, tables, suppliers and app listings |
| Choose the new platform | Dating Partners decides on applications within 48 hours | DatingAPI cost review takes about a week, under NDA | Both run by our group |
| Clean data and test import | Weeks 2 to 4 | Pilot in TestFlight about two weeks after you send materials, then four weeks of testing | Delete dummy profiles; check passwords and photos |
| Build | Within the test period | 6 to 10 weeks after sign-off | DatingAPI rehearses the move twice |
| Cutover | One day, with registrations paused on WordPress | App update; old system kept running for 60 days | Final export, domain switch, 301 redirects |
| Member emails and subscriptions | Weeks after cutover, in batches | Alongside the update | Cancel old subscriptions as new ones start |
| Wind down WordPress | When nothing depends on it | After the 60 days | Keep an offline backup; cancel plugin support |
| Redirects | At least a year | At least a year | Do not remove them early |
Before the first member email, update your privacy notice. The ICO lists what it must cover, including who you are, why you use the data, who receives it and how long you keep it; see GDPR for dating sites. Our WordPress dating plugins guide covers when WordPress is still the right choice.
Websites usually move to Dating Partners: no setup fee, 50% of all revenue from each member you bring for the life of that member, and a shared member network from day one. Apps with their own members usually move to DatingAPI. Compare both with other options on our dating software page.
This is general information, not legal advice. Take advice on your data protection position before you move member data.
Questions
Can I keep my WordPress blog when I move the dating part?
Yes, if the new platform lets you run content on the same domain or a subdomain. Keeping the blog on WordPress and moving only the members area keeps the content's URLs and rankings intact. Ask the new platform how it handles content pages.
Does WordPress's built-in export move my members?
Not in a form a dating platform can use. The Tools, Export screen creates an XML file designed for moving posts, pages and similar content between WordPress sites. Profile answers, messages and memberships held in plugin tables need a full database export.
Do I need permission from the plugin vendor to leave?
Usually not. Plugin and theme licences are one-off or yearly purchases for your own site, and the member data sits in your own database. Cancel renewals and support plans once nothing depends on them.
What if my site uses several plugins for profiles, chat and payments?
List each one and the tables it created before you export. Chat, video and payment add-ons often keep their own records, and some, such as hosted chat services, keep data on the supplier's servers rather than yours.
Sources
- Learn WordPress: The WordPress database, checked 21 November 2026
- WordPress: Tools Export screen, checked 21 November 2026
- Make WordPress Core: WordPress 6.8 will use bcrypt for password hashing, checked 21 November 2026
- Wbcom Designs: Where does BuddyPress store member info, checked 21 November 2026
- BuddyPress Trac: messages component loader (changeset 9182), checked 21 November 2026
- Paid Memberships Pro: Database structure, checked 21 November 2026
- WP Dating: Frequently asked questions, checked 21 November 2026
- WP Dating: Pricing, checked 21 November 2026
- WP Dating: Terms and conditions, checked 21 November 2026
- WordPress.org plugin directory: Rencontre, Dating Site, checked 21 November 2026
- ThemeForest: Sweet Date, item comments by SeventhQueen, checked 21 November 2026
- Themosaurus: Gwangi theme, checked 21 November 2026
- CMA: Online dating and consumer law, advice for business, checked 21 November 2026
- Stripe: Import payment data to Stripe, checked 21 November 2026
- Google Search Central: Site moves with URL changes, checked 21 November 2026
- ICO: What privacy information should we provide?, checked 21 November 2026
- Dating Partners partner terms, checked 21 November 2026
- DatingAPI, checked 21 November 2026
What changed
- : First published.