Artifact GuideEU MDR

EU MDR Legacy Device Transition

Regulation (EU) 2023/607 amended MDR Article 120 so certain MDD and AIMDD legacy devices can keep being placed on the market or put into service only when the transition conditions are met.

Use this page to check certificate status, class-based transition dates, QMS and notified-body milestones, significant-change limits, surveillance duties, and the evidence file a reviewer should expect.

Author
Sorena AI
Published
May 9, 2026
Updated
May 26, 2026
Sections
5

Structured answer sets in this page tree.

Primary sources
3

Cited legal and guidance references.

Publication metadata
Sorena AI
Published May 9, 2026
Updated May 26, 2026
Overview

Legacy-device transition under the EU MDR is not a broad grace period. The Article 120 extension depends on a device-by-device record showing the earlier directive basis, certificate or declaration status, continued AIMDD or MDD compliance, no significant design or intended-purpose change, no unacceptable health or safety risk, MDR QMS readiness, a timely notified-body application, and a written agreement where required.

Section 1

Transition Conditions To Verify First

Start with the exact device and certificate history. Regulation (EU) 2023/607 extended Article 120 for devices covered by valid AIMDD or MDD certificates and for certain former class I MDD devices that now require notified-body involvement under the MDR, but the extension is conditional.

For certified devices, Article 120(3a) points to 31 December 2027 for class III devices and class IIb implantable devices other than the listed low-risk implantable exceptions. It points to 31 December 2028 for other class IIb devices, class IIa devices, and class I devices placed on the market in sterile condition or with a measuring function. Article 120(3b) also uses 31 December 2028 for qualifying former class I MDD devices whose MDD declaration of conformity was drawn up before 26 May 2021 and whose MDR conformity route now needs a notified body.

The date is usable only if Article 120(3c) is satisfied: continued AIMDD or MDD compliance, no significant change in design or intended purpose, no unacceptable risk, an MDR Article 10(9) quality management system by 26 May 2024, a formal conformity-assessment application by 26 May 2024, and a written agreement with the notified body by 26 September 2024.

  • Create a device list that ties each legacy device to its AIMDD or MDD certificate, declaration of conformity, risk class, intended purpose, and substitute-device strategy if any.
  • For certificates that expired before 20 March 2023, record whether the pre-expiry written agreement route, an Article 59 derogation, or an Article 97 conformity-assessment requirement supports continued validity.
  • Do not treat the transition date as available if the manufacturer has no MDR QMS, no timely application, no written agreement where required, or a change record that alters design or intended purpose in a significant way.
Recommended next step

Turn the legacy transition file into reviewable evidence

Use the transition checklist to assemble certificate history, Article 120 eligibility, QMS proof, notified-body agreements, change-control decisions, PMS, vigilance, and clinical evidence in one reviewable record.

Section 2

Certificate Validity, Applications, And Surveillance

A legacy certificate is not enough by itself. The file should show that the certificate was issued under Directive 90/385/EEC or Directive 93/42/EEC from 25 May 2017, was still valid on 26 May 2021, and was not withdrawn afterwards, or that an expired-before-20-March-2023 certificate fits one of the Article 120(2) rescue routes.

After the Article 120(3c) deadlines, the practical center of gravity moves to the MDR notified body. Article 120(3e) keeps the issuing notified body responsible for appropriate surveillance until the manufacturer has agreed surveillance with an MDR-designated notified body; by 26 September 2024 the notified body that signed the written agreement is responsible for surveillance for devices covered by that agreement.

The surveillance transfer should be documented rather than assumed. Keep the old certificate, the formal application, the written agreement, the device scope covered by the agreement, surveillance-transfer arrangements, and any confirmation letters or written notified-body decisions together in the transition file.

  • Match certificate scope to actual model names, variants, Basic UDI-DI or device identifiers where available, intended purpose, and the device intended to substitute the legacy device if the application uses a substitute route.
  • Keep evidence that the notified body can add submitted information to its files; a read-only platform link is weak evidence if it does not allow the notified body to retain the relevant documents.
  • Track notified-body written decisions separately from certificates, because non-significant administrative corrections or additions do not create a new MDD or AIMDD certificate.
Section 3

Significant-Change Limits During Transition

The transition file needs a change-control gate. Article 120(3c) requires no significant change in design or intended purpose. MDCG 2020-3 Rev.1 explains that this assessment is case-specific and concerns legacy devices using the amended Article 120 transition.

Changes to intended purpose, patient or user population, clinical use, design or performance specifications, software, materials, substances, sterilisation method, or packaging design affecting sterilisation need explicit significance review. A change can also be significant when it creates new risks, negatively affects existing risks, changes control mechanisms, changes operating principles, changes energy sources, or changes alarms.

Administrative changes and some QMS or manufacturing-site changes may be non-significant when they do not affect design or intended purpose and the certification conditions remain maintained, but they still belong in the change notification process agreed with the notified body. When in doubt, the manufacturer should ask the notified body and keep the answer with the certificate package.

  • Use a change assessment form with fields for intended purpose, clinical claims, design/performance specifications, software, materials, sterilisation, risk controls, usability or clinical data impact, and notified-body notification result.
  • For non-significant changes, keep the rationale, supporting design or risk evidence, notified-body confirmation where applicable, and a statement that the certificate itself was not amended or supplemented.
  • For significant changes, treat the changed device as outside the legacy transition path and plan MDR conformity assessment before placing that changed device on the market.
Section 4

MDR Duties That Still Apply

Legacy status does not freeze the device under the old directives for every obligation. Article 120(3d) applies MDR requirements for post-market surveillance, market surveillance, vigilance, registration of economic operators, and device registration to Article 120(3a) and 120(3b) devices in place of the corresponding AIMDD or MDD requirements.

The transition evidence should therefore connect Article 120 eligibility to live MDR operating controls: PMS plan and report routines, PMCF decisions where relevant, complaint and incident intake, vigilance evaluation, field safety corrective action handling, registration data, QMS procedures, and management review of unresolved transition gaps.

For clinical evidence, legacy-device status does not mean old clinical files are automatically sufficient for MDR certification. MDCG 2020-6 treats clinical evaluation as a lifecycle activity and expects PMS and PMCF data to feed the clinical evaluation for legacy devices.

  • Keep a PMS-to-clinical-evaluation trace showing how complaints, incidents, PMCF, literature, registries, and benefit-risk conclusions are reviewed for the legacy device.
  • Maintain vigilance and field safety records with the same device identity used in the certificate, technical documentation, PMS plan, and registration data.
  • Use the QMS file to prove the 26 May 2024 Article 10(9) condition and to show transition governance, change control, supplier controls, complaint handling, CAPA, and management responsibility.
Section 5

Practical Evidence Pack

A useful transition pack should let a regulatory, quality, procurement, or authority reviewer see why the device can still be supplied and what work remains for MDR certification. Keep it short enough to review, but complete enough to prove each Article 120 condition without relying on project memory.

Separate the legal eligibility record from operational evidence. The eligibility record answers whether the transition is available; the operational evidence proves PMS, vigilance, registration, QMS, surveillance, and change-control obligations are still running.

  • Eligibility record: device identity, directive certificate or declaration, certificate validity path, class-based transition date, Article 120(3c) condition checklist, and substitute-device mapping if used.
  • Notified-body record: formal application, written agreement, surveillance-transfer arrangement, certificate scope mapping, confirmation letters, written decisions, open nonconformities, and agreed milestones.
  • Change-control record: all design, intended-purpose, software, material, sterilisation, supplier, QMS, labelling, and clinical-claim changes with significance rationale and notified-body handling.
  • Operational record: Article 10(9) QMS evidence, PMS plan and outputs, PMCF rationale or plan, vigilance reports, complaints and CAPA, registration data, technical documentation gap plan, and management-review actions.
Primary sources

References and citations

eur-lex.europa.eu
Referenced sections
  • Binding MDR source for Article 10(9) QMS context, PMS, vigilance, registration, technical documentation, and conformity-assessment obligations referenced by the transition amendments.
"quality management system"
Related guides

Explore more topics

Custom-made medical devices under the EU MDR | EU MDR FAQ
Concise EU MDR FAQ on custom-made device definition, mass-produced exclusions, Annex XIII statements, documentation, conformity assessment, PMS, vigilance, and records to retain.
EU MDR Annex II and III Technical Documentation
Build an MDR technical documentation index for Annex II device files and Annex III post-market surveillance evidence, including GSPR, risk, clinical, PMS, UDI, and EUDAMED records.
EU MDR Annex VIII Classification Guide
Classify EU MDR medical devices under Annex VIII using intended purpose, duration, invasiveness, active device and software rules, and conformity assessment impact.
EU MDR Annex XVI products without a medical purpose
source-linked EU MDR guide for Annex XVI products: listed product groups, common specifications, clinical evidence, notified-body route, UDI, EUDAMED, PMS, and vigilance evidence before launch.
EU MDR Applicability Test
Test whether a product, accessory, software function, or Annex XVI product falls under the EU Medical Device Regulation, and record the evidence for the next classification step.
EU MDR change assessment workflow
Assess EU MDR device, design, software, intended purpose, QMS, clinical, PMS, UDI, classification, and notified-body impacts before releasing a medical device change.
EU MDR Checklist for Medical Device Compliance
Practical EU MDR checklist covering qualification, classification, conformity assessment, technical documentation, GSPR, clinical evidence, UDI, EUDAMED, PMS, vigilance, QMS, and legacy transition evidence.
EU MDR classification workflow
A concrete EU MDR classification workflow for intended purpose, device or accessory qualification, Annex VIII rule selection, Rule 11 software review, class outcome, and notified body impact.
EU MDR Clinical Evaluation Overview
EU MDR clinical evaluation overview covering Article 61, Annex XIV, clinical data sources, equivalence, PMCF, CER evidence, notified body review, GSPR, and benefit-risk support.
EU MDR Clinical Evaluation Report Template
A source-linked EU MDR clinical evaluation report template covering intended purpose, GSPR linkage, clinical data appraisal, equivalence limits, PMCF, conclusions, and reviewer signoff.
EU MDR clinical evidence guide
source-linked EU MDR guide to clinical evaluation, clinical investigations, equivalence, PMCF, GSPR support, technical documentation, and notified-body review.
EU MDR compliance obligations
EU MDR compliance guide for device qualification, classification, conformity assessment, QMS, technical documentation, UDI, EUDAMED, PMS, vigilance, and legacy transition controls.
EU MDR conformity route workflow
source-linked EU MDR workflow for classifying a device, choosing the conformity assessment route, preparing technical and QMS evidence, and reaching certificate, DoC, UDI, EUDAMED, and CE outputs.
EU MDR deadlines and compliance calendar
Grounded EU MDR calendar for application, legacy-device transition, UDI, EUDAMED, and recurring QMS, technical documentation, clinical, PMS, vigilance, certificate, and change reviews.
EU MDR Device Classification Guide
Classify an EU MDR medical device by intended purpose, Annex VIII duration, invasiveness, active-device and software rules, then document the conformity route impact.
EU MDR EUDAMED and UDI registration
source-linked MDR guide to Basic UDI-DI, UDI-DI, EUDAMED device registration, actor roles, labels, technical documentation, and UDI data governance.
EU MDR FAQ: qualification, evidence, UDI, and transition
Concise EU MDR FAQ covering device qualification, software classification, accessories, custom-made devices, clinical evidence, UDI, EUDAMED, notified bodies, significant changes, and legacy transition.
EU MDR notified body route selection
Choose an EU MDR conformity assessment route by device class, Article 52 option, notified body designation scope, QMS readiness, technical documentation, clinical evidence, and certificate evidence.
EU MDR penalties and enforcement risk
source-linked EU MDR penalties and enforcement-risk guide covering Article 113, Member State penalty rules, market restrictions, recalls, certificate consequences, and evidence.
EU MDR PMS and Vigilance Guide
EU MDR guide to post-market surveillance, PMCF updates, PMS reports, PSURs, serious incident reporting, FSCA/FSN handling, trend reporting, and evidence records.
EU MDR PMS and vigilance records
source-linked EU MDR guide to PMS plans, PMS reports, PSURs, PMCF updates, serious incident and FSCA reporting, trend reporting, and EUDAMED evidence handling.
EU MDR PMS Plan Template for Medical Devices
A source-linked EU MDR post-market surveillance plan template covering device scope, PMS data sources, PMCF linkage, vigilance, trend reporting, PMSR or PSUR outputs, roles, cadence, and evidence records.
EU MDR QMS and technical file evidence map
Map EU MDR Article 10 QMS duties to Annex II and Annex III technical documentation, PMS, vigilance, UDI records, and notified-body review evidence.
EU MDR QMS requirements under Article 10
EU MDR QMS guide for Article 10 manufacturer controls covering regulatory strategy, design, risk, clinical evaluation, PMS, vigilance, UDI, suppliers, CAPA, and conformity records.
EU MDR qualification and borderline products
EU MDR qualification guide for medical purpose claims, accessories, software, Annex XVI products, and borderline routes to classification and conformity assessment.
EU MDR qualification workflow
A concrete EU MDR workflow for deciding whether a product is a medical device, accessory, Annex XVI product, IVD interface, medicinal-product interface, or non-MDR product before classification and conformity assessment.
EU MDR requirements checklist
Concrete EU MDR requirements for medical-device scope, classification, GSPR, conformity assessment, technical documentation, QMS, clinical evidence, UDI, EUDAMED, PMS, vigilance, and economic-operator records.
EU MDR Rule 11 software classification
Classify MDR medical device software under Rule 11 using intended purpose, diagnosis or therapy decision impact, physiological monitoring, conformity route, clinical evidence, and software-change records.
EU MDR significant changes FAQ: legacy-device transition and notified-body review
FAQ on MDR significant changes for legacy devices, including intended-purpose, design, software, material, sterilisation, clinical, QMS, notified-body, and evidence impacts.
EU MDR Transition Timelines: practical guide
EU Medical Device Regulation guide to Transition Timelines with scope decisions, owner actions, evidence records, source-linked citations, and practical next steps.
EU MDR UDI and EUDAMED registration guide
EU MDR guide to Basic UDI-DI, UDI-DI, UDI carriers, EUDAMED actor and device registration, change impacts, and evidence governance.
EU MDR vigilance reporting workflow
Concrete EU MDR vigilance workflow for incident intake, serious incident assessment, FSCA and FSN handling, trend reporting, EUDAMED caveats, CAPA, PMS, clinical evaluation updates, and records.
How should Basic UDI-DI and UDI-DI be assigned under the EU MDR? | EU MDR FAQ
EU MDR FAQ explaining what Basic UDI-DI and UDI-DI identify, how they connect to UDI carriers, EUDAMED records, change triggers, and retained evidence.
MDR vs AI Act for medical-device software
Compare MDR software qualification, classification, clinical evidence, QMS, PMS, UDI, EUDAMED, and notified-body evidence boundaries against cautiously scoped AI Act overlap.
MDR vs GPSR: medical-device boundary checks
Compare MDR medical-device scope with general product-safety fallback questions for borderline, non-medical, and Annex XVI products.
MDR vs IVDR: medical devices and IVDs compared
Compare EU MDR and IVDR scope, classification, conformity routes, technical documentation, clinical or performance evidence, UDI, EUDAMED, PMS, and vigilance.
MDR vs Product Liability Directive evidence comparison
Compare EU MDR market-access evidence with Product Liability Directive exposure without treating compliance records as a liability outcome.
What should an EU MDR PMCF plan and report cover? | EU MDR FAQ
Under the EU MDR, PMCF is part of PMS and clinical evaluation. See what the plan, activities, report, updates, and retained evidence should cover.
What should manufacturers do when an EU MDR classification changes? | EU MDR FAQ
Concise EU MDR FAQ on classification changes, intended purpose, software, notified-body route impact, certificates, technical documentation, and retained evidence.
When can clinical equivalence be used under the EU MDR?
EU MDR FAQ on clinical equivalence, including technical, biological, and clinical characteristics, access to equivalent-device data, class III and implantable-device limits, clinical evaluation, PMCF, and retained evidence.
When do software or products make medical purpose claims under the EU MDR? | EU MDR FAQ
EU MDR FAQ on medical purpose claims, intended purpose evidence, software qualification, Annex XVI contrasts, and records to keep.
When is a PSUR required under the EU MDR and what should it contain? | EU MDR FAQ
EU MDR FAQ on PSUR scope, content, update cadence, PMS and PMCF links, notified-body handling, EUDAMED submission, and evidence to retain.
When is an accessory regulated under the EU MDR? | EU MDR FAQ
EU MDR FAQ on when an article is a medical device accessory, how intended purpose affects classification, and what evidence to keep.
When is software regulated as SaMD under the EU MDR? | EU MDR FAQ
Concise EU MDR FAQ on software qualification, intended medical purpose, Rule 11 classification, modules, clinical evidence, change assessment, UDI, and EUDAMED.
Which devices need an SSCP under the EU MDR and what should it include? | EU MDR FAQ
EU MDR FAQ on when an SSCP is required, who prepares, validates, uploads, and updates it, and what evidence should support the summary.
Which EUDAMED modules matter under the EU MDR? | EU MDR FAQ
EU MDR FAQ mapping EUDAMED modules to actor registration, UDI/device data, certificates, clinical investigations, vigilance/PMS, market surveillance, and practical records.