Migration Overview
Migrating from an existing CMP to ConsentForge takes 1–3 hours for most setups. This guide explains what's involved and what to expect.
What gets migrated
| What | How |
|---|---|
| Vendor list | Import via CSV or manual mapping |
| Banner configuration | Recreate in the Banner Builder (10–20 min) |
| Existing consent records | Not imported — existing consent is treated as expired |
| Google Tag Manager setup | Update the ConsentForge tag (5 min) |
Consent records
GDPR does not require you to re-collect consent if your existing consent was validly obtained. However, ConsentForge cannot verify external consent records, so we recommend a Shadow Mode transition rather than a hard cutover.
Migration path
- Create your ConsentForge property and configure your banner
- Import your vendor list (CSV or from a supported CMP)
- Run Shadow Mode — both CMPs run in parallel for 1–2 weeks
- Switch over — remove the old CMP, go live with ConsentForge
Supported migration sources
| Source CMP | Import method |
|---|---|
| Cookiebot | Export JSON → import via Dashboard |
| CookieYes | Export CSV → import via Dashboard |
| Consentmanager.net | Export CSV → import via Dashboard |
| Borlabs Cookie | Export JSON → import via Dashboard |
| Any other CMP | Manual CSV import |
Timeline
| Step | Time |
|---|---|
| Account setup + property config | 30 min |
| Vendor import | 15–30 min |
| Banner configuration | 20–30 min |
| Shadow mode testing | 1–2 weeks (optional but recommended) |
| DNS/script cutover | 5 min |