Moving from the plugin

Before you start

The plugin and Cookiemark should never run on the same page, because visitors would see two banners. So you prepare everything in Cookiemark first, and swap the plugin for the script in one step at the end.

Visitors will be asked again after the move. The plugin stored the choice in a cookie called bfcc_consent, and Cookiemark uses cookiemark_consent. Cookiemark does not read the old cookie, so every visitor chooses once more.

Step 1: export from the plugin

In WordPress, open CookieConsent, then Setup, and press Export settings. You get a JSON file.

While you are in the plugin, also export its consent log as a CSV file. The log stays in your WordPress database and does not move to Cookiemark. Keep the export for as long as you need it as proof.

Step 2: import into Cookiemark

Add the site in Cookiemark, under Sites, Add site.
Open the site, then Settings, then Import from the WordPress plugin.
Pick the export file, or paste its contents, and press Import as a draft.

The import lands in the draft, so nothing is live yet. Check the design on the Design tab before you publish.

What comes along

The layout, position, colours, sizes, corners, icon, animation and the button to reopen.
Custom CSS. Class names that start with bfcc- become cmk-.
A Google Font becomes the same family from Bunny Fonts, which serves it from the EU without cookies.
The categories you offer, the consent version, how long the choice lasts, and the cookie domain.
Google Consent Mode, the mapping of categories to signals, the container ID, the data layer name and the form events.
The services you switched off, your own blocking rules and the region settings.
The Cookiebot event names and the Cookiebot API setting.

The plugin's basic mode becomes basic Consent Mode in Cookiemark, and anything else becomes advanced. The plugin started in advanced mode, so check this setting if you never changed it.

What stays behind

Your texts. The import does not change them. Copy any wording you rewrote in the plugin into the Texts tab.
Your cookie list. Run a scan and add the cookies it suggests, or add them from a service.
The consent log. It stays in WordPress, as described in step 1.

After the import, Cookiemark lists the plugin settings that work differently here. These are the ones you may see:

Blocking was off in the plugin. Cookiemark always blocks known services before consent, and you switch single services off under Cookies.
Hiding the banner for logged-in WordPress roles is not possible with the script alone.
The consent log was off in the plugin. Cookiemark always keeps it, as proof of consent.
The plugin hashed or left out IP addresses. Cookiemark always stores a shortened address, never the full one.
Tag Manager set the Consent Mode defaults through the plugin's template. Import the Cookiemark template in its place, as described in Google Tag Manager.
The banner was switched off in the plugin. In Cookiemark it shows once you publish.

Step 3: publish and swap

Press Publish in Cookiemark.
In WordPress, deactivate CookieConsent and add the Cookiemark line, one straight after the other. Install the script shows where the line goes.
Clear the page cache of your caching plugin, your host and your CDN.
Open the site in a private window and check that one banner shows, the Cookiemark one.

Step 4: update your markup and code

Some of the plugin's names keep working. Others need a new name.

In the plugin	In Cookiemark
`data-cookieconsent="statistics"`	Keeps working. `data-cookiemark` is the new name.
A link to `#bfcc-open-preferences`	Keeps working. `#cookiemark-preferences` is the new name.
`data-bfcc-action`, `data-bfcc-allow`	Rename to `data-cookiemark-action` and `data-cmk-allow`.
`data-bfcc-consent-id` and the other fields	Rename to `data-cookiemark-consent-id` and so on.
`window.BFCC`	Rename to `window.Cookiemark`. The methods and properties have the same names.
Events such as `bfcc:change`	Rename to `cookiemark:change`.
`window.bfccListeners`	Rename to `window.cookiemarkListeners`.
Shortcodes, the declaration block and the PHP helpers	Not available. Cookiemark runs in the browser, not in WordPress.

Tag Manager triggers

The data layer events have new names, so update the triggers in your container on the same day you swap.

Plugin event or variable	Cookiemark event or variable
`bfcc_consent_ready`, `bfcc_consent_update`	`cookiemark_consent_ready`, `cookiemark_consent_update`
`bfcc_consent_statistics` and the other categories	`cookiemark_consent_statistics` and so on
`bfcc_consent`, `bfcc_consent_state`, `bfcc_consent_id`	`cookiemark_consent`, `cookiemark_consent_state`, `cookiemark_consent_id`
`bfcc_form_sent` and the other form events	`cookiemark_form_sent` and so on

If your container uses Cookiebot's event names through the plugin, they keep working once the import has switched them on.

Safari

The plugin set the consent cookie from your server, so Safari kept the choice for the full period. The Cookiemark script sets it in the browser, and Safari keeps that for seven days. To keep the old behaviour, add a small endpoint on your own site, as described in Safari and the seven-day limit.