ISO 27701:2025 Transition Paths

· 5 min read · Lyudmil Arkov

The ISO 27701:2025 transition is a project choice, not a new privacy law. ISO/IEC 27701:2025 was published on 14 October 2025. ISO withdrew the 2019 edition. The 2025 text is its own management system standard. You can certify it without holding an ISO 27001 certificate, and you can still integrate it with an ISMS. The background is in ISO 27701:2025 without ISO 27001. This page is the transition itself.

What the ISO 27701:2025 transition replaces

The 2019 edition was an extension. It sat on ISO 27001 and ISO 27002, and the certificate said so. The 2025 edition restructured the controller and processor controls and gave the PIMS its own requirements. If your statement of applicability still uses the 2019 annex letters, it is describing a withdrawn text. We are not going to repeat those letters here. Buy the 2025 standard and map from the document your certification body will audit.

A 2019 certificate does not flip itself. It stays valid only on the terms your certification body and its accreditation body still accept.

The date people quote

UKAS, the UK accreditation body, published a transition bulletin on 18 August 2026. It tells accredited certification bodies to have transitioned all certified clients by 31 October 2028. It also points those bodies at ISO/IEC 27706:2025, which is the requirements standard for the bodies that audit a PIMS, not a standard for your organization to certify against.

That date is UKAS’s date. It is not printed in ISO/IEC 27701, and it is not a rule from every accreditation body. If your certificate was issued under another accreditation body, ask that body. Do not plan a Bulgarian, German, or American audit on a UK bulletin alone, and do not cite a date you found on a consultant’s page that does not match the bulletin.

Ask your certification body three things in writing: the last date it will audit the 2019 edition, whether the transition audit is a full audit or a reduced one, and which evidence it wants for controller and processor roles.

Integrate, or keep the PIMS separate?

You already run ISO 27001. Don’t run the PIMS as a second management system. The overlap that is actually useful is access control, cryptography, logging, suppliers, and incident handling. The gaps a PIMS still has to close are purpose limitation, the rights process, retention that ends in deletion, and the role split between controller and processor. One internal audit programme and one management review can cover both systems if the scope names the personal-data processing. That is the calmer path for most clients we see.

You don’t have ISO 27001, and the request in front of you is a privacy certificate. You can implement ISO 27701:2025 on its own. “Standalone” means the ISO 27001 certificate is not a ticket you must buy first. It does not mean the PIMS can ignore confidentiality, integrity, and availability of the personal data. You will still select security controls. You just won’t be maintaining a second certificate unless you need it.

You hold neither certificate, and a client asked for “27701 or equivalent.” Find out what they will accept before you pick. Some questionnaires still describe the 2019 extension. Send them the ISO page that says the 2025 edition can be used alone, and then decide whether they actually wanted an ISMS.

A transition that an auditor can follow

  1. Freeze the scope. List the processing, and mark controller or processor for each activity. A SaaS company is often both.

  2. Choose integrated or standalone, and write that choice into the scope statement.

  3. Gap the 2025 text against what you already do. Don’t gap it against a 2019 summary.

  4. If you hold a 2019 certificate, book the transition with the body that issued it. Switching bodies mid-transition is allowed, and it is slower than people expect.

  5. Keep one set of records. A privacy binder the security team never sees fails the first audit that asks for both.

  6. Retire the old annex references in contracts and in the statement of applicability once the body has moved you. Leaving both editions in the customer pack creates the next nonconformity.

This is an implementation note, not legal advice. A certificate is evidence of a management system. It is not a finding that the GDPR is met. Article 32 still asks for appropriate measures. It does not define them as ISO 27701.

ISO 27018:2025 is a different document: guidelines for a public-cloud PII processor, not a standalone PIMS. ISO 31700-1:2023 is high-level requirements for privacy by design of consumer products and services. Neither one is the transition path for a 2019 PIMS certificate.

How 27kay can help

We run the ISMS and the PIMS as one conversation. We’ll tell you if the standalone PIMS is enough, and we’ll tell you if the client who asked for 27701 actually wanted 27001.

For a person learning the 2025 edition, we help with enrollment through our PECB partnership. A course certificate is an individual’s credential. It is not your organization’s ISO 27701 certificate.

Let’s talk - bring the certificate you hold now, and the question the client actually asked.