Short answer

Regulation (EU) 2023/607 extended the MDR transition for legacy devices: they may be placed on the market until 31 December 2027 (class III and most class IIb implantables) or 31 December 2028 (other class IIb, class IIa, class I sterile or measuring, and up-classified MDD class I devices), with the class set under the MDR rules, which for software usually means Rule 11. The extension only applies to devices that met its conditions, including an application to an MDR Notified Body by 26 May 2024 and a signed agreement by 26 September 2024, and only while there is no significant change in design or intended purpose (MDCG 2020-3 Rev.1). MDD documentation has to be substantially rebuilt for the MDR.

Where the transition stands in October 2026

Regulation (EU) 2023/607 amended Article 120 MDR in March 2023 and extended the transitional period for legacy devices: devices covered by a valid MDD or AIMDD certificate, and class I devices whose MDD declaration of conformity was drawn up before 26 May 2021 and which need a Notified Body under the MDR — a common situation for software, which Rule 11 often places in a higher class than the MDD did. Legacy devices may continue to be placed on the market until:

  • 31 December 2027 — all class III devices and class IIb implantable devices (with exceptions for certain well-established implants such as sutures, staples and screws);
  • 31 December 2028 — other class IIb devices, class IIa devices, class I devices placed on the market sterile or with a measuring function, and up-classified MDD class I devices (Article 120(3b)).

Which date applies follows the device's class under the MDR classification rules, not the class on the MDD certificate (Commission Q&A on Regulation (EU) 2023/607). For software that moves up a class under Rule 11, check this carefully.

The extension was never automatic. Under Article 120(3c) it applies only if the device continues to comply with the MDD, there are no significant changes in its design and intended purpose, it does not present an unacceptable risk, and the manufacturer had an MDR quality management system in place by 26 May 2024, had lodged a formal application with a Notified Body by 26 May 2024, and had signed a written agreement with that Notified Body by 26 September 2024. Since 26 September 2024 at the latest, the Notified Body that signed the MDR agreement is responsible for the appropriate surveillance of the legacy device.

What this means now. All application and agreement deadlines have passed. If your legacy device met them, your task is to complete MDR certification before the applicable end date without breaking any condition — in particular, without making a significant change. If it did not, the transitional period for that device has already ended: it can only be placed on the market again once it holds an MDR certificate. Speak to your competent authority if you are in that situation. No further extension has been adopted, so plan on the current dates.

Time matters even within the extension. In the Commission's Notified Body survey (data as of 28 February 2026), the time from signed written agreement to certificate for MDR QMS-plus-product certificates was most often 13–18 months (51% of responding Notified Bodies), 19–24 months for 31%, and more than 24 months for 10%. A file that arrives at the Notified Body incomplete, or that needs major rework, uses up that margin quickly.

Legacy devices are also already subject to parts of the MDR: post-market surveillance, market surveillance, vigilance, and registration of economic operators and devices apply under Article 120(3d) — including PSURs for legacy class IIa, IIb and III devices and a post-market surveillance report for legacy class I devices, based on the MDD class (MDCG 2021-25 Rev.1).

What MDR transition actually means — the honest version

Many companies approach MDD-to-MDR transition expecting to do a documentation update — add a few sections, reformat some files, and submit to an NB. This expectation is wrong and leads to very expensive surprises when NBs return their files with lists of major non-conformities.

MDR transition is a full recertification project. The technical documentation structure is different, the clinical evidence requirements are considerably higher, the post-market obligations are broader, and the QMS requirements have expanded. For most SaMD, the honest truth is that you are building a new MDR technical file that may incorporate some content from the old MDD documentation.

The MDD-to-MDR transition checklist for software

Technical Documentation (Annex II)

  • Rewrite device description to include intended purpose, intended users, patient population, contraindications, and clinical context in the specificity MDR requires — and re-check the class under Rule 11
  • Update software documentation section: IEC 62304 compliance evidence (software classification, architecture, V&V evidence, SOUP list) — MDR expects significantly more detail than MDD
  • Rebuild the GSPR checklist from EU MDR Annex I — mapping to MDR GSPRs, not MDD Essential Requirements. For each GSPR, document how conformity is demonstrated and which standard/document is the evidence
  • Update risk management file to ISO 14971:2019 — including the benefit-risk terminology and the requirement to demonstrate acceptable residual risk after controls
  • Update usability engineering documentation to the current IEC 62366-1
  • Add cybersecurity documentation — the MDR sets explicit IT-security requirements (Annex I §17.2, §17.4, §18.8) that the MDD did not spell out; MDCG 2019-16 Rev.1 is the guidance
  • Update labelling and Instructions for Use to EU MDR Annex I Section 23 requirements

Clinical Evaluation (Article 61, Annex XIV)

  • Write a Clinical Evaluation Plan (CEP) meeting Annex XIV Part A — the MDR makes it an explicit requirement; for software, follow MDCG 2020-1
  • Conduct a systematic literature search with documented methodology — not just a summary of supporting papers
  • Evaluate clinical data for your specific software against your intended use — performance claims must be substantiated
  • Produce a full CER following the MDCG 2020-1 approach, with a benefit-risk conclusion
  • Write a Post-Market Clinical Follow-up (PMCF) plan to Annex XIV Part B — or justify in the PMS plan why PMCF is not applicable
  • Set up the PSUR process — under the MDR, class IIa PSURs are updated when necessary and at least every two years, class IIb and III PSURs at least annually (Article 86)

Quality Management System

  • Keep the QMS that had to meet Article 10(9) by 26 May 2024 aligned with MDR post-market obligations (Articles 83–86) — including the specific data to be collected, analysis frequency, and reporting thresholds
  • Implement complaint handling and vigilance reporting procedures aligned with MDR Article 87 and MDCG 2023-3
  • Add PSUR preparation process to QMS
  • Update your EUDAMED registration process — the first four EUDAMED modules have been mandatory since 28 May 2026, with transition arrangements for devices already on the market (see separate guide)
  • Review Authorised Representative agreement for MDR compliance

Notified Body Engagement

  • Confirm that your MDR Notified Body's designation scope covers your software (check the NANDO database)
  • Agree a realistic plan with the Notified Body for completing the conformity assessment before your end date, including time for answering findings
  • Do not change Notified Body casually: switching after 26 September 2024 keeps the transitional period only if the old agreement is terminated and a new written agreement is signed at the same time, under conditions set out in the Commission Q&A — and not when it is a reaction to a refusal
  • Prepare for an MDR conformity assessment under Annex IX (QMS + technical documentation assessment) or, for class IIa and IIb, the alternatives involving Annex XI

Significant changes — the hidden transition risk

Article 120(3c)(b) allows the transitional period only while there are no significant changes in the design and intended purpose of the legacy device. MDCG 2020-3 Rev.1 (May 2023, aligned to Regulation (EU) 2023/607) explains how to assess this. If you make a significant change before your MDR certificate is in place, the device can no longer be placed on the market under the transitional provisions — it needs an MDR certificate first, not by the 2027/2028 end date.

For software, MDCG 2020-3 Rev.1 (Chart C) treats as significant, for example: a new or majorly modified architecture or database structure, a change of an algorithm that may alter diagnosis or therapy, a new or major change of operating system or component, a new channel of interoperability, replacing required user input with a closed-loop algorithm, a new medical feature, and any extension of the intended purpose — new indications, new user or patient populations, or new ways of clinical application. Bug fixes that bring the device back to its original specification and security updates are generally not significant, provided the benefit-risk ratio is not adversely affected; neither is a limitation of the intended purpose. This creates a difficult dilemma for software companies: you cannot stop developing your product, but certain changes end the transitional period early.

The solution is rigorous change control during the transition period. Every change must be assessed against MDCG 2020-3 Rev.1 before implementation, documented, and notified to the Notified Body under your agreed procedure; in case of doubt, ask the Notified Body. This is not optional — it is a QMS obligation that your internal audit process should be checking. If you want help planning the remaining work against your end date, see our EU MDR consulting; for the realistic duration of each phase, see our EU MDR timeline guide for software.

Official sources & references