DPP BUYER GUIDES
Digital Product Passport Migration: A Practical Exit Plan
Digital product passport migration means moving the data and operating responsibilities needed to keep passports usable. Downloading a spreadsheet is only part of that job. Before signing with a provider, use this exit plan to identify what must move, rehearse the transfer and protect the labels already attached to products.
Define what a successful provider change means
ESPR Article 10(1)(d) calls for interoperable, transferable DPP data without vendor lock-in. Article 10(4) addresses a back-up copy through a DPP service provider. Those requirements do not prove that a particular export or switching service works. Check the rules for your product and ask for practical evidence.
Our suggested success criteria are straightforward: the intended records arrive, their meaning survives, existing labels reach the correct destination and access remains appropriate. Write those outcomes into your project plan before discussing the transfer format.
This guide proposes a procurement and rehearsal method. It is not legal advice about an individual contract or an official migration standard. Examples are fictional, and the checklist does not certify either the outgoing or incoming provider.
References: EU ESPR — Regulation (EU) 2024/1781, Articles 9–11
| Dependency | Ask to receive or control | Acceptance question |
|---|---|---|
| Product identity | Identifiers and source-key mappings | Do all intended products arrive without duplicates? |
| Data meaning | Field definitions, units and schema versions | Do values keep their units and definitions? |
| Evidence and history | Files, references and relevant change records | Can the new team trace a correction to its source? |
| Routing | Domain, resolver and redirect responsibilities | Does an existing label reach the intended record? |
| Access policy | Role rules and organisation mappings | Do allowed and denied access tests still pass? |
| Operations | Cutover, rollback and support responsibilities | Can the receiving team run the rehearsal? |
Request a usable export package
Ask for a documented package before the notice period begins. It should describe its format, version, record scope and export time. Include definitions for units, allowed values and relationships. Request an inventory of files with checksums so the receiving team can detect missing or changed bytes.
For example, a fictional furniture company receives a CSV containing the value “12” for service life. The export lacks a unit and the definition used by the old system. The new provider cannot safely interpret it. Add a field dictionary and preserve the original definition rather than guessing.
Check documents as well as rows. A file export may contain links that only work while the old account is active. Request permitted copies of the underlying evidence or a documented way to retain access. Confirm licensing and confidentiality restrictions with the information owner.
List anything the provider cannot export and why. Distinguish a product feature you will replace from information you need to retain. Resolve gaps explicitly; do not treat an unexplained omission as a successful transfer.
Protect the route from existing labels
GS1’s DPP guidance separates product identification from discovery and data sharing. Use that distinction when mapping an exit: the printed identifier, the service that resolves it and the destination holding the information may have different owners. A data export alone does not transfer control of all three.
Consider a fictional tool brand whose labels point to a provider-controlled address. The company moves its records, but the old address stops working after cancellation. Ask how those existing requests will be served, who can change their destination and how long the arrangement lasts.
Before cutover, collect physical samples or exact label links from the agreed product set. Include older batches and variants. Reuse those same samples after the switch. Keep domain and routing rights in the exit agreement, with a named person able to exercise them.
Do not replace live routes during a sales demonstration. Rehearse in a controlled environment and agree the production switch separately. Ask the receiving provider to show how it checks that a route has not been mapped to a different product.
References: GS1 standards enabling DPP — v2.2
Run an independent import and reconciliation
Have the receiving team import the package without relying on an active session in the old platform. Compare record counts by status and explain any difference. Check a sample that includes a corrected value, a restricted document, an old product and a relationship between records.
Open the evidence files and inspect the imported values against the source package. A matching checksum verifies the copied bytes, not the meaning of a field or the correctness of a claim. Include a business reviewer who understands the product data.
Recreate access policy deliberately. Recheck which organisations and people are entitled to each role; do not carry across old passwords, tokens or unexplained grants. Test the public view and each relevant restricted view before exposing the new destination.
For digital product passport migration, keep a discrepancy log with an owner and a resolution for every blocked item. Sign off the reconciled result, rather than a screenshot of a completed progress bar.
Plan cutover and rollback together
Choose a transfer window and decide how updates will be handled during it. You can pause approved changes or capture and replay the final changes, but the team must know which approach it is using. Record the last included revision and the first revision owned by the new system.
Define rollback triggers before starting. A wrong-product destination or a restricted file becoming public should prompt an immediate review. Agree the following responsibilities before the transfer window.
If updates continue after cutover, a rollback must account for them. Simply returning traffic to an older copy could hide recent corrections. Ask both providers to demonstrate how they reconcile those changes, and keep the old environment available for the agreed recovery period.
- Name the operator who changes the live route and records when it changed.
- Name a separate reviewer who checks the destination and access results.
- Give the incident owner a clear way to stop the change or begin rollback.
Separate planned exit from backup recovery
CEN CWA 18186:2025 discusses long-term access and backup takeover in sections 5.15 and 5.16. It is a workshop agreement based on CircThread experience, not an official European Standard. Use its design questions as context; verify applicable retention periods from current product rules rather than adopting one blanket period.
A planned switch assumes cooperation and time. An outage or business closure may provide neither. Ask who can activate the backup, which records it includes and how readers reach it. Run that scenario separately from the migration rehearsal.
Bring the export inventory, restore results and routing plan into your provider review. Digital product passport migration becomes a testable service when each dependency has an owner and a demonstrated handover. Use the provider-selection guide to compare those answers before committing.
References: CEN CWA 18186:2025 — CircThread design guidance, sections 5.13–5.17
Sources and review context
Sources were reviewed for this editorial guide on 4 November 2026. Provider descriptions are attributed public statements. This guide does not report hands-on software testing or certify regulatory compliance. Check the current original source when a detail affects your decision.
How DPP Atlas reviews evidence