Migrate from
Leaving CookieYes? Here is what carries over.
On Hostless Duck, Cookie Consent & Privacy does the job of CookieYes and imports its data. What comes across and what does not is listed below, exactly as each importer's own record states it.
What carries over, and what does not
Cookie Consent & Privacy
A consent banner with categories and an equal-weight reject, a record of each choice that identifies nobody, a starting privacy notice, and one switch other modules read before they load anything optional.
From GDPR Cookie Consent (CookieYes, classic)
- Carries over
- The banner message, the wording on the accept, reject and settings buttons, and the link to your policy page when it is on your own site.
- Does not carry over
- Colours and position, the cookie list and its categories, the list of scripts it blocked (modules here follow one consent switch instead), and the show-only-in-the-EU setting.
From CookieYes (version 3 and later)
- Carries over
- The default banner's heading, wording, Accept, Reject, Customise and Save labels, the link to your policy when it is on your own site, and whether consent was asked first (GDPR) or offered as an opt-out (CCPA). Read from its banner table (wp_cky_banners): through a connection with the WebHD Migration Helper, or from phpMyAdmin.
- Does not carry over
- Other banners and other languages, its cookie list and categories table, colours and layout, and records of past choices.
From an export file: not yet verified against a live export. The file importer has only been tested on sample files we wrote from the documented format.
Through the site connection: tested 19 November 2026 on a test WordPress site with the free version of the plugin, not a customer's site.
Each import ends with a report that names anything it could not carry.
CookieYes's settings, read from the site itself
A move reads your WordPress site through a read-only connection that you approve. In a test on 19 November 2026, CookieYes's settings came across through that connection into the Cookie Consent & Privacy module. The test used the free version of the plugin on a test WordPress site, not a customer's site.
The rest of the site
CookieYes is one part of a site. Hostless Duck reads a WordPress site through a connection you approve and brings content, pictures, menus, comments and many plugin settings, and reports plainly what it could not carry.
The site check reads your public pages once and lists the theme and plugins it can see, with what Hostless Duck has for each. A plugin with no replacement yet is built for your site On The Fly. How that works
The Library Effect. Built once. Every site after rides free. A part built for one site joins the library, so every plugin on your site is in the library, in the build queue, or not yet needed. Look up the others.
$0 is the cost to build, for every site after the first. Applying the part to your site is part of the move. A site on a different version or set-up of the same plugin can read Partial: a priced gap, never a rebuild.
Also replaced by Cookie Consent & Privacy
The small print
CookieYes is another company's product, named here only to say what Hostless Duck can import from and what does the same job. Hostless Duck is not affiliated with, endorsed by or sponsored by its makers, and uses none of their code, styles or wording.
Is CookieYes the only thing your site runs on?
Give us your site's address and we read its public pages once: its theme, its plugins, and what Hostless Duck has for each. A real scan of your public pages, never a made-up result. No card.

