EBA taxonomy release migration
Moving from one reporting framework release to another means finding what appeared in between. Pick your current release and your target, and see which templates and how many dimensional items were introduced across the gap — 3.4 through 4.4.
DPM glossary export · 8 releases · 742 template codes · 15,816 items · introductions only
Compare two releases
Runs in your browser · nothing uploadedThe gap is exclusive of your current release and inclusive of the target: moving 3.5 → 4.2 shows everything introduced in 4.0, 4.1 and 4.2.
A release migration is a mapping exercise, not a lookup. The converter holds mappings per release and revalidates against the target taxonomy before you submit — with a free tier to start.
Create free account →The releases are not evenly sized
Knowing which gaps are large is most of the value in planning a migration window.
The baseline
434 template codes and 7,648 items carry a 3.4 start code — roughly half of everything in the glossary. This is the floor of the export rather than a release event.
The heavy content releases
4.0 introduced 2,740 items against only 14 new templates; 4.2 introduced 2,228 items against 40. Both reshaped existing templates far more than they added new ones.
The structural ones
4.1 brought 96 new template codes and 4.3 brought 71 — the two releases most likely to require new mappings rather than adjustments to existing ones.
A single item
One template and one item. A patch release in all but name, and a useful reminder that a version increment says nothing about its size.
Reviewed 21 August 2026 · source: DPM glossary export, releases 3.4 to 4.4 · Source: DPM glossary export as supplied · releases 3.4 to 4.4 · introductions only, no end-of-life data
Half a migration assessment, and it says so
It doesShow introductions
- Lists every template code first appearing in the releases across the gap.
- Counts dimensional items introduced per release.
- Names the categories that gained the most items in each release.
- Breaks the totals down release by release rather than as a single number.
- Runs offline against an embedded copy of the data.
It does notShow withdrawals
- Identify anything removed, retired or deprecated. The export has no end-of-life field.
- Tell you what changed within a template that already existed.
- Distinguish a renamed item from a new one.
- Tell you which templates your firm must file.
- Replace the EBA's release notes or the taxonomy itself.
The missing half is the dangerous half
A template you must now file is discoverable in advance and produces a visible gap. A template or dimensional item that has been withdrawn produces a file that looks complete and is rejected. This tool covers the first case only, because the data supports only the first case. If your DPM source can export end-of-life data, that is the single change that would make this a complete assessment.
Nothing you select here leaves your browser
The release data is embedded in the page and every comparison runs on your own machine. Nothing is sent to REGREP and nothing is logged.
That is deliberate. Which release you are migrating from is informative about your filing position.
About release migration
Why can't you show what was removed?
Because the glossary export carries a start release code for every item but no end release code — the field is empty on all 15,816 items, and every item is marked active. There is no way to distinguish something still in force from something retired. Rather than infer removals from absence, which would be guesswork, the tool states the limitation and covers introductions only.
Is the gap inclusive or exclusive?
Exclusive of your current release, inclusive of the target. Moving from 3.5 to 4.2 shows everything introduced in 4.0, 4.1 and 4.2, because you already have whatever 3.5 introduced and you need everything up to and including the target.
Why does 3.4 have so much?
Because it is the floor of this export rather than a release event. Anything that existed at or before 3.4 carries a 3.4 start code, so the figure is a baseline, not a measure of how much that release changed. Comparisons starting from 3.4 are meaningful; the 3.4 total itself is not.
Does a new template mean new work?
Usually, but not always, and the reverse is a bigger risk. A release with few new templates but thousands of new items — 4.0 and 4.2 both fit that pattern — reshapes templates you already file, which is harder to spot and often more work than adding a template you do not yet map.
Which release is this data from?
The glossary export supplied for this build, covering releases 3.4 through 4.4. Anything published after that export is not reflected. Check the EBA's current taxonomy and release notes before finalising a migration plan.
Do you store what I compare?
No. The data is embedded in the page and every comparison runs in your browser. Nothing is transmitted, logged or persisted.
Knowing what arrived is not knowing what left.
Create a free account and hold mappings per release, revalidated against the target taxonomy before submission.
No card required · free tier on core modules · nothing stored from this tool