In this lesson
After this lesson you can:
- Decide whether what you want is a transfer or an initial certification.
- Prepare the certification history a receiving body will ask for, and spot the gaps in it first.
- Time a transfer so it does not collide with recertification or an open finding.
Read first: What accreditation is and choosing a certification body
Yes, and it is a defined process.
Most people who ask this question expect the answer to be awkward. They assume that changing certification body means abandoning a certificate, running Stage 1 and Stage 2 again, and losing the time and money already spent. That assumption keeps a lot of organisations with auditors they are unhappy with.
It is wrong. The accreditation system anticipated this, because a market where certificates could not move would hand every certification body permanent captive customers. So there is a mandatory document for it, maintained by the International Accreditation Forum, and accredited bodies deal with transfers as ordinary work.
The caveats are real and they are narrower than the fear. They are about what you are transferring, who you are transferring to, and when.
What IAF MD 2 establishes.
IAF MD 2, in its current 2023 edition, is titled Transfer of Accredited Certification of Management Systems. It sets minimum criteria for moving an existing accredited management system certificate from one certification body to another, and those criteria also reach a certificate that has already been transferred once and is moving again. It hooks into the certification-body standard: the earlier edition was mandatory for applying clause 9.1.3 of ISO/IEC 17021-1.
Three things it establishes that matter directly to you:
- The accepting body must be accredited for the standard your certificate covers. Not accredited generally. Accredited for ISO/IEC 27001, which you can check in the accreditation body’s directory.
- The accepting body must satisfy itself that the issuing body was accredited. It runs the same verification on your current certificate that a careful buyer would, which is why an unaccredited certificate fails at the first step.
- There is a review of your existing certification before anyone takes it on. The receiving body establishes where you actually are: scope, cycle position, outstanding findings, and whether the required internal activities have happened.
When there is nothing to transfer.
This is the most common disappointment, and it is worth getting to quickly because it changes the whole plan.
If your certificate is unaccredited, transfer is not available. The mechanism governs accredited certification, and an accredited receiving body is required to confirm that the issuer was accredited. It cannot, because the issuer was not. What you are actually doing is an initial certification with an accredited body, including Stage 1 and Stage 2.
That is not a wasted position. If a real ISMS sits behind the certificate you hold, most of what an accredited audit looks for already exists and you are starting well ahead of a company with nothing. Accredited and unaccredited certification covers how to tell which you hold and what to do about it, including the part people find hardest, which is stopping the old certificate circulating while the real one is in progress.
Two other situations where there may be nothing valid to move: a certificate that has expired, and one whose surveillance audits were missed, because surveillance is what keeps a certificate alive. How a certificate can end sets out how that happens.
Reasons that hold up.
Transfers go more smoothly when you can state the reason plainly, because the receiving body will ask and a vague answer invites a closer look at your history.
Reasons that are straightforward and common:
- Auditor continuity. You have had a different lead auditor every visit and each one re-litigates the previous one’s conclusions.
- Sector competence. Your auditor does not understand your architecture and audits are spent on explanation.
- Scheduling. The body cannot get an auditor to you when your cycle requires it.
- You are adding another standard and want one body across both, with combined audits.
- Your buyers keep asking about a body they do not recognise, and recognition has commercial value to you.
- Service quality. Reports arrive late, findings are unclear, nobody answers.
One reason that is weaker than it looks is price. Audit duration follows the same published method whichever accredited body applies it, so a much cheaper quote usually reflects different inputs rather than a better deal, and the transfer itself has a cost. How audit days are calculated explains why accredited quotes converge.
The sequence.
Step 1
Confirm you hold an accredited certificate
Transfer under IAF MD 2 applies to accredited certification. Find the accreditation mark, confirm the issuing body is listed in an accreditation body’s directory with ISO/IEC 27001 in its accredited scope, and verify the certificate in the issuer’s register. If any of those fails, what you are planning is not a transfer.
IAF MD 2:2023 and the accreditation body’s directory
Step 2
Choose a receiving body that is accredited for this standard
The accepting body must itself be accredited for the standard the certificate covers, and it must satisfy itself that the issuing body was accredited for it too. So the receiving body has its own checks to run on your current certificate, and they are the same checks you should already have run.
IAF MD 2:2023, eligibility of the accepting body
Step 3
Assemble your certification history
Expect to provide the current certificate and scope statement, recent audit reports, the status of any nonconformities raised and how they were closed, and your internal audit and management review records. The receiving body is reconstructing where you are in the cycle, and gaps in that record are what slow a transfer down.
IAF MD 2:2023, review of certification documentation
Step 4
Let the receiving body review and decide
It reviews what you supplied, identifies anything outstanding, and determines what it needs before it can take the certificate on. Ask at this point exactly what that will involve for you, because it is the step where the detail varies by body and by what your history looks like.
IAF MD 2:2023, the transfer review
Step 5
Agree the cycle, then tell the people who rely on the certificate
Get the certificate number, the issue date, the expiry date and the surveillance schedule in writing before you announce anything. Then update your trust page, your questionnaire answers and anywhere the old certificate number appears, because stale certificate numbers in vendor files cause their own problems.
ISO/IEC 17021-1, certification documents
Step three is where transfers slow down, and it is the step entirely within your control. A receiving body is reconstructing your cycle position from documents. If you cannot produce recent audit reports, nonconformity records with evidence of closure, and your own internal audit and management review records, the review stalls while you chase a body you have just told you are leaving.
The remedy is a habit rather than a project. Keep your own copies of every audit report and every finding as they arrive. It costs nothing, it is good practice independent of any transfer, and it removes most of the leverage your current body would otherwise have.
Timing, and three traps.
Transfer from a settled position. That single sentence prevents most of the problems people have with this process.
| Your situation | Verdict | Why |
|---|---|---|
| An open nonconformity is unresolved | Close it first | A receiving body reviews your certification status and will find it. |
| The certificate expires in a few weeks | Poor timing | Recertification and transfer at once compresses everything. |
| A surveillance audit is overdue | Resolve first | A lapsed cycle may leave nothing valid to move. |
| You are mid-scope-change | Finish or defer | Transfer the certificate you have, then change scope. |
| The current body will not release records | Escalate | Non-cooperation is a known issue with published guidance. |
| Settled cycle, no open findings, months to expiry | Good timing | This is the window to use. |
The three traps worth naming explicitly, because each has caught organisations we have worked with:
Transferring to escape a finding. It does not work, and it is the most understandable mistake on this list. A major nonconformity feels like a reason to leave, and the receiving body’s review is specifically designed to establish the status of your findings. You arrive with the problem attached and your motive on display. Close it first.
Leaving it until recertification is due. Transfer and recertification are both processes with their own requirements, and stacking them compresses everything into the period when you have least room. Start the conversation with months in hand.
Announcing before the certificate exists. Do not update your trust page or tell customers until you hold the new certificate with its number, dates and surveillance schedule in writing. Then update everywhere the old number appears, because a stale certificate number in a customer’s vendor file produces a failed verification and a conversation you do not want.
What to ask the receiving body.
Put these in your first email. The answers tell you both how the transfer will go and how the body operates.
- Which accreditation body holds your ISO/IEC 27001 accreditation, and what is the number?
- Is that accreditation current under ISO/IEC 27006-1:2024?
- What will you need from us to review our existing certification, as a list?
- After that review, what will the transfer involve for us, and over what period?
- What will the certificate’s expiry date and surveillance schedule be once transferred?
- What are the audit days and fees for the remaining visits in the cycle?
- Who would be our lead auditor, and what have they audited in our sector?
- What would cause you to decline the transfer?
Question eight is the useful one. A body that can describe the circumstances in which it would say no is a body applying criteria. One that says it never declines is telling you something else.
What this page does not tell you, and why.
You will have noticed that we have not told you whether a transfer requires an audit visit, whether your expiry date carries across unchanged, or how long the whole thing takes.
That is deliberate. IAF MD 2 is published by the IAF and hosted by accreditation bodies, and we have read and cited it for what it establishes. The operational detail of how a particular transfer runs depends on the receiving body’s own accredited procedure and on what your certification history looks like, and we could not verify a single general rule that would be true for every reader.
Sites that give you a confident timetable for this are usually describing one certification body’s process as though it were the standard. We would rather tell you which questions produce your actual answer, which is what the section above does. The document itself is linked in the sources if you want to read the criteria directly.
Thinking about moving?
Tell us why, and send us your certificate and the last audit report. We will tell you whether you hold something transferable, what the receiving body will ask for, what you are missing, and whether your timing works. We coordinate audits with accredited bodies and have no stake in which one you pick.
Key takeaways.
- Moving an accredited ISO 27001 certificate between accredited bodies is a defined process with minimum criteria in IAF MD 2, current edition 2023. You do not start from scratch.
- The receiving body must be accredited for ISO/IEC 27001 and must satisfy itself that the issuing body was accredited as well.
- An unaccredited certificate cannot be transferred, because there is no accredited status to move. That route is an initial certification.
- The receiving body reviews your existing certification: scope, cycle position, findings status, internal audit and management review. Gaps in that record are what stall a transfer.
- Keep your own copies of audit reports and nonconformity records as they arrive. It is good practice anyway and it removes your current body’s leverage.
- Transfer from a settled position. No open nonconformity, no overdue surveillance, months rather than weeks before expiry.
- Transferring to escape a finding does not work, because establishing findings status is exactly what the review does.
- Announce nothing until you hold the new certificate, then update every place the old number is recorded.
Quick check.
Which document sets the minimum criteria for transferring an accredited management system certificate?
- ISO/IEC 27001 Annex A
- IAF MD 2
- ISO/IEC 27006-1 Annex C
- The certification body’s own contract
Check the answer
B. IAF MD 2, current edition 2023, is the IAF mandatory document titled Transfer of Accredited Certification of Management Systems. The certification body’s contract governs your commercial relationship with it and cannot override the accreditation requirement. IAF MD 2:2023
A company holds an unaccredited ISO 27001 certificate and wants to move to an accredited body. What is it doing?
- A transfer under IAF MD 2
- An initial certification
- A recertification
- A scope extension
Check the answer
B. There is no accredited status to transfer. An accredited body must satisfy itself that the issuing body was accredited, which cannot be satisfied here, so the route is initial certification with Stage 1 and Stage 2. Accredited and unaccredited certification
Spot the mistake. A company unhappy with its auditor starts a transfer six weeks before its certificate expires, with one major nonconformity still open.
Check the answer
Both the timing and the open finding work against it.. The receiving body reviews findings status as part of taking the certificate on, so an open major is the first thing it will surface. Stacking that onto a recertification deadline compresses everything into the worst possible window. Close the finding, transfer from a settled position, and leave months rather than weeks. Clause 10.2, nonconformity and corrective action
Sources.
- IAF MD 2, transfer of accredited certification of management systemsInternational Accreditation Forum, Issue 2 Version 2, 14 June 2023, replacing the 2017 editionUsed here: That transfer is a defined process with minimum criteria, that the accepting body must be accredited for the standard, and that it must confirm the issuing body was accredited
- IAF MD 2, the 2017 editionInternational Accreditation Forum, hosted by an accreditation bodyUsed here: That the document is mandatory for applying clause 9.1.3 of ISO/IEC 17021-1, which is the hook into the certification-body standard
- UKAS technical bulletin on IAF MD 2United Kingdom Accreditation ServiceUsed here: That non-cooperation in a transfer is a recognised problem with published guidance behind it
- ISO/IEC 17021-1, requirements for bodies providing audit and certification of management systemsISO catalogue entry 61651Used here: The certification cycle and certification documents that a transfer has to reconstruct
Changes since publication
This page does not state whether a transfer requires an audit visit, whether your expiry date carries across, or how long a transfer takes. Those depend on the receiving body’s accredited procedure and on your certification history, and no general rule could be verified. The questions in the section above are how to get your own answer, and IAF MD 2 is linked for the criteria themselves.
Last checked against the IAF’s published mandatory document on transfer, UKAS guidance, and ISO’s catalogue entry for ISO/IEC 17021-1 on 9 November 2026.