Keeping Consent Records Intact When You Change Platforms
Moving stores, banner tools, or tag managers can strand your consent history. What records to export, what to keep, and how to prove continuity after a migration.
Your consent records are evidence: who was shown what, which version of the notice, and what each visitor chose. Migrations put that evidence at risk, because records live inside the banner tool you are leaving, in formats the new tool may not import and nobody thought to export.
Teams discover the gap months later, during a complaint or a review, when the honest answer becomes that choices made last year are no longer retrievable. A little migration planning prevents that answer.
Export before you touch anything
Before switching tools or platforms, export the full consent log the current vendor holds: timestamps, choice states, notice version, and region where available. Store it in a format you control, with a note of what each field means, since vendor specific codes are meaningless without a key.
Check retention in your current contract too. Some vendors delete logs shortly after cancellation. The export deadline is therefore before you give notice, not after the new banner goes live.
Map versions across the change
Consent is only interpretable against the notice that produced it. Keep copies of the banner text, privacy information, and cookie list as they existed under the old setup, with dates, and record the date the new versions took over.
When a question arrives about a choice made before migration, you should be able to produce the record and the wording it responded to. That pair is the whole point of keeping records, and migration is exactly when pairs get separated.
Decide how existing choices carry over
Shoppers who already chose should not be silently reset without thought. Many migrations re ask everyone, which is defensible and sometimes cleanest, but it should be a decision, recorded with a reason, not an accident of the new tool defaulting to no stored state.
If you can import prior choices, validate the import on a sample before launch. A mapping error that flips declined to accepted is the single worst migration outcome, and it is invisible unless someone checks records against choices by hand.
Run the new setup like a launch
Treat the new consent tool as a fresh implementation: test script blocking before choice, test each region's notice, confirm the banner records choices in the new log correctly, and verify your old export is archived and readable.
Add a calendar note to review record keeping after the first month on the new tool. Early configuration drift is common, and catching a logging gap at one month is a nuisance while catching it at one year is a problem.
Related reading
If this topic is useful, these earlier guides go deeper on connected questions: Testing Consent Banners on Mobile Without Missing the Usual Faults, Consent Records: How Long to Keep Them and Why, and The Best Cookiebot Alternatives for Growing Sites.
Frequently asked questions
What consent records should we keep?
Keep the timestamp of each choice, the choices made, the version of the notice shown, and region or language where relevant, plus copies of the notice and cookie information for each version. Together they let you show what a visitor agreed to and when.
Can we import old consent choices into a new tool?
Often yes, if the old tool exports usable data and the new one accepts imports. Validate a sample carefully after import. If import is not reliable, re asking visitors is a reasonable alternative, as long as it is a deliberate, documented decision.
When should we export records during a migration?
Before you cancel or alter the old service. Some vendors purge logs soon after contracts end. Export early, store the files under your own control, and keep a key explaining the fields and codes used.
Why keep old banner wording after we switch?
Because a consent record only makes sense alongside the notice the visitor actually saw. If wording is discarded, old records lose their meaning. Archiving each version with its dates preserves the full picture.