From High Intent Media, the group behind Smooch, Just Singles, Dating Partners and DatingAPI. We say where our products fit, and where they do not.Facts and sources
Talk to us
Switching guide

Moving from SkaDate

Short answer

SkaDate is self-hosted, so you hold the MySQL database and the photo folders and can export them yourself. The licence covers one website and needs no notice to leave. Keep the password salt from config.php, expect members to re-enter card details, map every old URL to one 301 redirect, and keep app listings in your own developer account.

By the White Label Dating teamLast checked 7 minute read
We run Dating Partners and DatingAPI. They appear on this page. We show where others are a better fit, and we do not use star ratings. How we compare

We run Dating Partners and DatingAPI, and both are run by the same group as this site. If you leave SkaDate, a website can move to Dating Partners, and an app with its own members can move to DatingAPI. The SkaDate terms below come from its own pricing page, licence agreement and manuals, read on 21 November 2026. Your order may differ, so check it. For moving off any script in general, see moving from a self-hosted script; this page covers what is specific to SkaDate.

What does SkaDate publish about leaving?

SkaDate publishes nothing that stops you leaving: the licence is a one-off purchase for one website, and you get the full source code. The terms that matter when you move:

TermWhat SkaDate publishesWhat it means for you
Licence scopeOne licence covers "one single website (domain/member database)"The member database is yours to run, back up and export
Source codeFull access to the script's source code on purchaseYour developer can read the tables and write an export
RefundsExcluded; none once the code is accessed or modifiedNo money back on the licence when you leave
Licence keyChecked daily against domain, IP address and installation pathCopying the site to another server locks the admin panel until the key is reissued
Licence transferAllowed if you notify SkaDate 14 days beforeRelevant if you sell the old site rather than close it
Hosting$29 a month, or $159 for 6 months and $269 for 12 monthsCheck what you prepaid before you set a date
SkaDate Prime support$99 a month after the included periodCancel once the move is finished
Data ownership and exportNot published in the licence agreement; ask themYou hold the database, so you rarely need SkaDate to export it

Still deciding whether to move at all? Our guide to SkaDate alternatives compares the options.

What can you export from SkaDate?

You can export the whole database and every uploaded file, because the site runs on your server or on SkaDate hosting with cPanel access. SkaDate's own site transfer manual describes the steps: export the MySQL database from phpMyAdmin as an SQL file, and copy all files by FTP or as an archive. SkaDate is built on the Oxwall platform, and the manual names the folders that hold uploaded content, including ow_userfiles and ow_pluginfiles. Member photos sit in those folders, not in the database.

From that export your developer, or the new platform, can usually extract:

  • Profiles: account details, profile answers, search preferences and join dates.
  • Photos: the image files plus the database rows that link each photo to its member.
  • Messages and contacts: conversations, winks, favourites and blocks, where you choose to bring them.
  • Billing records: membership levels, renewal dates and payment references (not card numbers).
  • Safety records: reports, blocks and suspended accounts, so known bad actors do not return.

Before you export, delete sample profiles, merge duplicates and decide what to do with long-inactive accounts. Then ask the new platform for its import format and send a small test file first. Remember that on SkaDate you are the data controller, so the decision to move the data, and the notice to members, are yours.

What happens to passwords and payments?

Passwords can move only if the new platform can check SkaDate's password format, and card details stay with your payment processor. SkaDate's manual warns that if the OW_PASSWORD_SALT value in ow_includes/config.php changes when a site moves, "users' passwords will become invalid." So give the new platform that salt along with the hashes, kept securely, or plan a password reset email for every member.

Card numbers never sit in your SkaDate database. If you move processors, the old processor must send card data straight to the new one. Stripe, for example, says never to send card details yourself, that processors can take from a few days to several months to produce an export, and that imports usually complete within 10 business days once it has valid data. Stripe also says it cannot import subscriptions, which must be recreated, and that you should cancel the old ones as soon as the new ones are active or members will be billed twice. If your new platform runs its own payments, as Dating Partners does, 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. SkaDate itself has little to agree, because you hold the data, but other contracts around the script do.

  • SkaDate: the renewal dates and any refund terms for prepaid hosting and Prime; how and when it deletes data from its servers after hosting ends; and whether it will help with a final full backup.
  • SkaDate, if you sell rather than close: how it handles the 14 days' notice and the licence key for the buyer.
  • Your payment processor: its notice period, whether it will release card data to the new processor, the fee and the timescale.
  • Your app developer, if not SkaDate: whose developer account holds each app, and the app source code.
  • Other suppliers: ID check, SMS, email and content delivery services, each with its notice period and data deletion terms.
  • The new platform: its import format, how it treats passwords, photos and live subscriptions, and a written timetable.

How do you protect your search rankings when leaving SkaDate?

Map every indexed SkaDate URL to its new equivalent and redirect each one with a single permanent 301 redirect on the day you switch. SkaDate uses its own URL patterns for profiles, photos, blogs and search pages, so build the list from Search Console and a full crawl, not from memory. Google recommends server-side permanent redirects, redirecting straight to the final address rather than through chains, and keeping redirects "for as long as possible, generally at least 1 year." It also warns of temporary ranking changes during a move. If you keep your domain, you do not need Google's change of address tool.

Decide early what happens to public profile pages. Many platforms do not publish member profiles to search engines, so point those URLs at the closest useful page, such as a local or niche landing page, rather than the home page.

What happens to your SkaDate apps?

If your apps sit in your own Apple and Google developer accounts, you keep the listings and ship the new version as an update. SkaDate's Gold package includes iOS and Android app source code with full setup and store submission, so check whose account the listings were published in; SkaDate's pricing page does not say. If they are in someone else's account, ask for a transfer. Apple says a transferred app keeps its reviews and ratings, and apps with auto-renewable subscriptions need an app-specific shared secret shared between the two accounts.

DatingAPI rebuilds existing apps on its platform under your own store listing, so members get the new version as a normal update. It is meant for apps that already have members, not for a first launch.

How do you tell SkaDate members about the move?

Update your privacy notice first, then email members in batches, starting with recent paying members. Explain who runs the service now, why it has changed, what happens to their data, and what they need to do, usually set a password and re-enter payment details. The ICO lists what privacy information must include, such as who you are, why you use the data, your lawful basis, who receives it and how long you keep it. If the new platform operator becomes a controller of the data, it must also tell members what categories of data it received and where they came from. See GDPR for dating sites and our dating platform migration guide.

What is a realistic timetable for leaving SkaDate?

A realistic timetable is four to eight weeks for a website, and about three months or more for an app. The steps that take longest are usually the payment processor's card export and app store work, not the SkaDate export itself.

StageWebsiteAppNotes
Inventory and questionsWeeks 1 to 2Weeks 1 to 2List contracts, features and data; send the written questions
Choose the new platformDating Partners decides on applications within 48 hoursDatingAPI cost review takes about a week, under NDABoth run by our group
Test export and importWeeks 2 to 4Pilot in TestFlight about two weeks after you send materials, then four weeks of testingSend a sample first; check photos and passwords
BuildWithin the test period6 to 10 weeks after sign-offDatingAPI rehearses the move twice
CutoverOne day, with a short freeze on the old siteApp update; old system kept running for 60 daysFinal export, domain switch, 301 redirects
Member emailsWeeks after cutover, in batchesAlongside the updateStart with recent payers
Wind down SkaDateWhen nothing depends on itAfter the 60 daysKeep an offline backup; cancel hosting and Prime
RedirectsAt least a yearAt least a yearDo not remove them early

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, which charges per active and paying member with no revenue share.

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

Questions

Do I have to give SkaDate notice before I move?

Not for the licence, which is a one-off purchase. Hosting and SkaDate Prime are paid by the month or year, so note the renewal dates and cancel them once nothing depends on them.

Can I get a refund on my SkaDate licence when I leave?

No. SkaDate's pricing page says its policies exclude refunds because software is an intangible product, and its licence agreement says there is no refund once the code has been accessed or modified.

Can I sell my SkaDate site instead of moving it?

Possibly. SkaDate's licence agreement allows a transfer of the licence if you notify SkaDate 14 days before it and give the new holder's details. Ask SkaDate in writing how it handles the licence key on a sale.

Will my SkaDate admin panel still work after I copy the site to another server?

Not without a new licence key. SkaDate's licensing manual says the key is checked daily against the domain, IP address and installation path, and the admin panel becomes inaccessible if they change and the key is not reissued.

Should I bring sample or dummy profiles across?

No. Delete them before you export. Members pay to meet real people, and the new platform's member checks and moderation will remove them anyway.

Sources

  1. SkaDate: Pricing, checked 21 November 2026
  2. SkaDate: User Licence Agreement, checked 21 November 2026
  3. SkaDate: Software licence, checked 21 November 2026
  4. SkaDate manual: Site transfer, checked 21 November 2026
  5. SkaDate manual: Licensing, checked 21 November 2026
  6. SkaDate: Hosting requirements, checked 21 November 2026
  7. Stripe: Import payment data to Stripe, checked 21 November 2026
  8. Google Search Central: Site moves with URL changes, checked 21 November 2026
  9. Apple: Overview of app transfer, checked 21 November 2026
  10. ICO: What privacy information should we provide?, checked 21 November 2026
  11. Dating Partners partner terms, checked 21 November 2026
  12. DatingAPI, checked 21 November 2026

What changed

  • : First published.

Planning a move?

Keep your brand, domain and members. We will tell you which route fits, or neither.

Talk to us about a move