<!-- Moving From SkaDate, PG Dating Pro or WordPress Plugins | https://whitelabeldating.com/switch/from-self-hosted-script/ | Run by High Intent Media, which also runs Dating Partners and DatingAPI. -->

# Moving from a self-hosted dating script

> On a self-hosted script such as SkaDate, Chameleon, WP Dating or Dating Pro, or a custom build, you own the database, so profiles, photos and messages can usually be exported. Card details move processor to processor, if at all. Map every old URL to one 301 redirect, and keep app listings in your own account.

We run Dating Partners and DatingAPI. Websites usually move to Dating Partners, and apps with their own members, including custom builds, usually move to DatingAPI. Both are run by the same group as this site. This guide covers SkaDate, Chameleon, WP Dating, Dating Pro and custom builds; vendor details come from their own pages, checked on 16 October 2026.

## When does moving off a self-hosted script make sense?

Moving makes sense when running the platform takes more of your time than growing the brand. Common signs: you spend your week on server updates, payment problems and moderation; your site feels empty because it has no shared member pool; or new rules have landed on you. Ofcom says UK online safety duties apply even to providers based outside the UK, starting with an illegal content risk assessment, and on a script those duties are yours alone.

## What should you check before moving off your script?

Check your recurring contracts, not the script licence. Most script licences are one-off purchases, so there is no notice period. The costs that keep running are services around the script:

| Item | Example from vendor pages | What to do |
|---|---|---|
| Hosting | SkaDate hosting $29 a month; Dating Pro hosting $12 a month after three months | Note renewal dates; keep it until the move is finished |
| Support plans | SkaDate Prime $99 a month; WP Dating support $49 a month after the free period | Cancel once the new platform is live |
| Payment processor | Your own merchant account | Read its notice terms and ask about card data transfer |
| Other vendors | ID checks, SMS, email, CDN | List each one with its notice period |

Also list every custom feature and plugin you use, and decide which ones actually matter to members.

## What can you export from a self-hosted script?

You can usually export everything in your own database, because on a self-hosted script you are the data controller. That normally includes profiles, photos, messages, likes, blocks, reports and subscription records. Before exporting, clean the data: delete dummy or fake profiles (WP Dating bundles dummy profiles, and Chameleon sells a pack of 1,000), remove duplicates, and decide what to do with long-inactive accounts. Then ask your new platform for its import format and send a small sample first.

## What usually cannot move from a self-hosted script?

Card details, store subscriptions and some passwords are the usual problems. Card numbers sit with your payment processor, not in your database. Stripe, for example, asks you to request the data from your previous processor and never to send card details yourself, and says the transfer can take a few days or several weeks. Subscriptions bought through Apple or Google stay with the app listing, not your database. Passwords are stored in scrambled form, and if the new platform cannot read your script's format, members will need to reset them.

## How do you run your script and the new platform side by side?

Keep the script live until the new platform is tested, then cut over on a set date. Build the new platform on a staging address, import a test copy of your data and check sign-up, login, payment, messaging and search. Freeze changes on the old site a few days before the move. On the day, take a final export, import it, point the domain at the new platform and turn on redirects. Keep a full backup of the old database offline afterwards.

## How do you move members in stages?

Move members with personal emails in batches, starting with your recent paying members. Tell them who you are, why the site is changing, what happens to their data and what they need to do: usually set a password and re-enter payment details. The ICO says people must get clear information about what you do with their personal data, so update your privacy notice before the first email. Send batches a few days apart and fix problems before the next one. See [GDPR for dating sites](/guides/gdpr-dating-sites/).

## How do you keep your search rankings?

Keep your rankings by redirecting every old URL directly to its new equivalent with one permanent 301 redirect. Scripts and WordPress plugins use their own URL patterns for profiles, search and blog pages, so build a full map from Search Console and a crawl. Watch for chains: a WordPress site that already redirects to https or www can end up with two or three hops, so point each old URL straight at its final address. Google recommends permanent server-side redirects, no chains, and keeping redirects as long as possible, ideally at least a year.

## What happens to your apps?

If your apps are in your own developer account, you keep the listings and ship the new version as an update. SkaDate's Gold package, for example, includes app source code and help submitting to the stores, so the listing is often already in your account. Check where yours is. DatingAPI rebuilds existing apps and you keep your store listings, brand and revenue.

If a developer or agency published the apps in their account, ask them to transfer the listing. Apple says the app keeps its ratings and reviews, but apps with auto-renewable subscriptions need an app-specific shared secret. Google Play says "users, download statistics, ratings and reviews" transfer, but orders made before the transfer stay with the original account.

## Where should you move to from a self-hosted script?

Websites usually move to Dating Partners, and apps with their own members usually move to DatingAPI; both are run by the same group as this site.

- **[Dating Partners](/dating-sites/)** suits a website: $0 setup, no monthly fee, 50% of all revenue from each member you bring, for life, members from day one on the shared network, and member checks run by the platform. Ask how your existing members would be brought across.
- **[DatingAPI](/dating-apps/)** suits apps with an established member base, including custom builds. It rebuilds your app, runs matching, chat, safety, ID checks and payments, and charges a monthly fee per active and paying member with no revenue share. There is a 90-day run-off if you later leave.

Still deciding whether to move at all? Read [white label vs self-hosted](/compare/white-label-vs-self-hosted/).

## What is a realistic timetable?

A realistic timetable is a few weeks for a website and about three months for an app.

1. **Weeks 1 to 2:** list contracts, features and data; clean the database. Dating Partners decides on applications within 48 hours, and DatingAPI offers a free cost review in about a week, under NDA.
2. **Build and test:** import a sample and test end to end. DatingAPI puts the build at 6 to 10 weeks after sign-off.
3. **Cutover day:** final export, domain switch and 301 redirects.
4. **After cutover:** member emails in batches; cancel hosting and support plans once nothing depends on them.

This is general information, not legal advice. Take advice on your data protection position before moving member data.

## Common questions

### Do I need permission from my script vendor to leave?

Usually not. Most script licences are one-off purchases, and Chameleon describes its licence as permanent with no annual or monthly fees. You only need to cancel recurring services such as hosting and support.

### Should I bring dummy profiles across?

No. Delete any dummy or fake profiles before you export. Members pay to meet real people, and a platform with ID checks will not accept them.

### Can I keep my script running as a backup after the move?

Keep a read-only copy and a full database backup for a while, but take it offline. Two live sites with the same members confuse people and split your search rankings.

### What if my custom build has features a platform does not offer?

List them before you choose. Some may be worth keeping, and a platform that rebuilds your app can tell you what it can match; others may be unused and fine to drop.
