Skip to main content
CookieLintDocs
Reference

Migrate from another CMP

Suggested cutover order. Run the public scanner on both deploys, compare, then swap.

Cutover steps

Suggested order when replacing an existing CMP:

  1. Add the CookieLint snippet to a staging deploy. Leave the existing CMP in place.
  2. Run the public scanner (or the Chrome extension) on both deploys. Compare pre-consent and post-reject behaviour.
  3. Map the old categories to ours in the banner editor: NECESSARY, PREFERENCES, ANALYTICS, MARKETING.
  4. Promote staging to production. Remove the old CMP snippet in the same deploy to avoid two banners racing on the same page.
  5. Run the scanner once more on production to confirm nothing leaked through.

Historical receipts

Historical consent receipts from other CMPs are not imported. Old receipts stay with the old vendor; receipts captured after cutover live in CookieLint's audit log.

PrevTroubleshooting