<!-- How to Migrate a Dating Site to a New Platform | https://whitelabeldating.com/guides/dating-platform-migration/ | Run by High Intent Media, which also runs Dating Partners and DatingAPI. -->

# How to migrate a dating site to a new platform

> To migrate a dating site, first confirm your contract lets you take the members, then map every type of data: profiles, photos, passwords, messages, subscriptions and consent records. Rehearse the move, redirect every old URL, tell members before and after, and keep the old system running until the new one is proven. Paid subscriptions are the hardest part.

## When is it worth moving a dating site to a new platform?

It is worth moving when the platform itself is what holds the business back, and you have ruled out cheaper fixes. A migration puts paying members at risk, so the reason has to be stronger than a nicer admin screen.

Good reasons include:

- The provider is closing, has been sold, or has stopped developing the product.
- You cannot meet a legal duty on the current system, such as age checks or data requests.
- The terms have changed: a lower revenue share, new fees or slower payouts.
- You need an app, and the current platform is for websites only.
- You run your own script and can no longer afford to maintain it safely.

Weak reasons include one missing feature, a slow month, or a sales call that promised more. Ask the current provider first. Then cost the move honestly, including the members you may lose on the way.

## What data can you take with you?

Most member data can move, but each type has its own catch. List every type before you ask for a quote, because the awkward ones decide the timetable.

| Data | Can it move? | What to check |
|---|---|---|
| Profiles and preferences | Yes | Field mapping: the two systems rarely use the same questions and answer lists |
| Photos | Yes | Whether moderation status moves too, or every photo is reviewed again |
| Passwords | Sometimes | Passwords are stored as hashes. They only move if the new platform can read the old hashing method |
| Messages and matches | Sometimes | Both members in a conversation must exist on the new side. Decide how far back to go |
| Blocks and reports | Should | A member must not reappear to someone who blocked them. Treat this as a safety requirement |
| Subscriptions and card details | Hard | Card details sit with the payment processor, not with you. See the payments section below |
| Marketing consent and unsubscribes | Must | Without the consent record and the suppression list you cannot lawfully email the base |
| Page URLs | Yes | Every old URL needs a redirect |
| App store listings | Yes | Each store has a transfer process with its own conditions |

Ask the current provider for a sample export early. A file with a few hundred real records tells you more about the work than any specification.

## Who has the right to move the members?

The contract with your current provider decides whether the member database is yours to take. Some white label agreements say the provider owns the database, some say the brand does, and some split it. Our guide on [who owns the members](/guides/who-owns-the-members/) explains the common positions, and [white label dating contracts](/guides/white-label-dating-contracts/) covers exit clauses.

Data protection law then decides how you move it. The Information Commissioner's Office (ICO) says that when you use people's information for a new purpose you must update your privacy information and bring the change to their attention before you start. Where an organisation obtains personal data from another source, it must give people privacy information within a reasonable period and no later than one month, or at the first communication if that comes sooner. A new platform that becomes responsible for your members' data is in that position.

Do not confuse this with the right to data portability. That right belongs to each member. The ICO says it lets individuals receive personal data they have provided in a structured, commonly used and machine readable format, and have it sent to another controller. It does not give an operator the right to demand a bulk export.

This is general information, not legal advice. Our guide to [GDPR for dating sites](/guides/gdpr-dating-sites/) has more.

## What happens to paying members and subscriptions?

Subscriptions are the hardest thing to move, because the right to charge a card belongs to a payment account, not to a database row. There are three situations.

**Card payments on the web.** The processor holds the card details. Moving them means a transfer between processors, or asking each member to pay again on the new platform. Whether your current provider will release card data is a contract question, and the answer is rarely published. Ask in writing. If it will not, plan for the old platform to keep billing existing subscribers through a [run-off period](/glossary/#run-off-period) while new payments start on the new one.

**Apple subscriptions.** If the app moves to a different developer account, Apple says the app keeps its reviews and ratings and members continue to receive updates. Apps with auto-renewable subscriptions must use an app-specific shared secret so the new owner's servers can verify them. Apple also notes that members may need to log in again where keychain sharing is used, and that Sign in with Apple needs a transfer identifier generated for each member.

**Google Play subscriptions.** Google's help page says it transfers "all users, statistics, data, comments, ratings, subscriptions" and related information with the app. Orders created before the transfer stay in the original account, so refunds on those are handled from there. Payout and earnings reports do not transfer, so download them first.

If the app stays in your own developer account and only the system behind it changes, the store side is simpler. The new platform still has to recognise every existing subscriber on day one.

## How do you move without losing search traffic?

Redirect every old URL to its closest new page with a permanent redirect, and keep the redirects in place. Google's guidance on site moves says to use permanent server-side redirects such as 301, to map old URLs to new ones before the move, and to keep redirects for as long as possible, generally at least one year.

Google also says to expect temporary changes in ranking during a move. For small and medium sites it recommends moving all URLs at once and not one section at a time. If the domain itself changes, use the Change of Address tool in Search Console.

On a dating site, do not forget:

- Local and niche landing pages, which often bring most of the search visits.
- Login, password reset and unsubscribe links in old emails. Members click these for months.
- Tracking links used by affiliates and ad campaigns.

## Should you move everyone at once or in stages?

Move the live member base in one planned switch, after you have rehearsed it. A dating site split across two systems means members cannot see or message each other, which damages the product more than a short maintenance window.

A sound plan has four parts:

1. **Rehearse.** Run the full import into a test copy, check counts and spot-check real profiles, then do it again.
2. **Freeze.** Pick a quiet time, pause sign-ups and messaging, and take the final export.
3. **Switch and check.** Test login, messaging, payment and unsubscribe with real accounts before you reopen.
4. **Keep a way back.** Leave the old system intact until the new one has run through at least one billing cycle.

DatingAPI, our sister company run by the same group as this site, works this way for apps. It rehearses the move twice and keeps the old system running for 60 days. Dating Partners, also run by our group, is the route for dating websites. Our [switching page](/switch/) explains both, and the glossary defines [member migration](/glossary/#member-migration).

## What should you tell members, and when?

Tell members before the move, on the day, and again once it is done. Say plainly what changes for them and what stays the same.

- **Before.** The date, the reason in one sentence, any new privacy notice or terms, and who will hold their data.
- **On the day.** How to log in, whether they need a new password, and where to get help.
- **After.** That their profile, photos, messages and membership are in place, and how to report anything missing.

Add extra support cover for the first week. Send from a domain members already know, because a message about passwords from a strange address looks like a scam.

## What should you ask the new platform before you sign?

Ask these in writing, and compare the answers with your current contract.

- Have you moved a dating member base before, and from which systems?
- Which of my data types will you import, and which will you not?
- Can you read my current password hashes?
- How will existing subscribers be billed after the move?
- How many rehearsals are included, and who signs off each one?
- How long does the old system stay available?
- Who writes the member notices, and who answers support on the day?
- If I leave you later, what export do I get, in what format, and at what cost?

For comparison, DatingAPI says it gives 90 days of run-off and a full data export at no charge to an app that leaves.

## Common questions

### How long does a dating site migration take?

It depends on the size of the member base and how much is changing. As one reference point, DatingAPI, run by the same group as this site, says its build takes 6 to 10 weeks after sign-off, with two rehearsals before the real move.

### Will members have to reset their passwords?

Only if the new platform cannot read the old password hashes. Ask both sides early, because a forced reset on day one stops some members coming back.

### Can a white label provider stop me taking my members?

It depends on the contract. Some agreements give the provider ownership of the member database, and some give it to you. Read the ownership and exit clauses before you plan anything.

### Should I change the design at the same time as the platform?

Change as little as you can. If members see a new login, new layout and new prices on the same day, you cannot tell which change caused a problem.

### Do app ratings survive a move to a new developer account?

Yes on both stores. Apple says a transferred app keeps its reviews and ratings, and Google says it transfers ratings and reviews with the app.
