Transfer an LEI to Another Provider: Process and Timing
· Robert
To transfer an LEI, ask the new issuer or its Registration Agent to arrange the move: your LEI code stays the same, and the old issuer should not charge a porting fee. The GLEIF service-level targets allow 4 LOU business days for the sending issuer and 3 LOU business days for the receiving issuer, but they are not a guaranteed total completion time.
Key points before you transfer an LEI
- Transfer the existing LEI rather than applying for another one. The code and its original issuer prefix remain unchanged.
- Make the request through the provider that will maintain the record after the transfer. The request must be authorised by someone empowered to act for the entity.
- The managing issuer changes. You can check the record and its registration status in GLEIF LEI Search.
- Distinguish the transfer request from any renewal service or renewal term offered by the new provider.
The LEI ROC – Progress report: The Global LEI System and regulatory uses of the LEI (2018) sets out the exclusivity principle: an entity that has obtained an LEI cannot obtain another one. It also confirms that an entity may move maintenance of its LEI between operators without changing the identifier.
Why move an LEI to another provider?
An entity may consider changing provider because it wants to review renewal pricing, consolidate the administration of group LEIs or use a different service. Those are reasons to compare providers, not reasons to obtain a new identifier. Start by checking which issuer currently manages the record and when its next renewal is shown as due.
GLEIF LEI Search provides a free public lookup showing the registration status, next renewal date and managing issuer. If the status is unfamiliar, the LEI lookup and record status guide provides related reading. A decision about whether to move the record should be based on the entity’s own service and renewal needs.
What stays the same, and what changes?
LEI portability moves responsibility for maintaining an existing record. It does not replace the LEI. The LEI ROC – Additional Guidance on Portability (2014) says that even the prefix associated with the original issuer stays in the code, and that the prefix has no national meaning.
| Record element | Effect of a transfer |
|---|---|
| LEI code | Stays the same; the entity does not acquire another LEI. |
| Original issuer prefix | Stays in the LEI code, even when a different issuer maintains the record. |
| ManagingLOU | Identifies the issuer responsible for the record and changes when management moves to the receiving issuer. |
| Reference data | The receiving issuer validates the data during the transfer process. |
ManagingLOU is the LEI data field for the issuer responsible for the record, as defined in GLEIF – Level 1 data: LEI-CDF 3.1 format. Do not treat a changed managing issuer as evidence that the legal entity has been assigned a different code.
Step-by-step: how the transfer request works
- Look up the existing record. Check its LEI, managing issuer, registration status and next renewal date in GLEIF LEI Search. Use the existing LEI when discussing the move with the new provider.
- Choose the receiving provider. Ask how it handles transfers and whether a renewal service is part of the arrangement. If you use a Registration Agent, its partner LEI issuer performs the transfer: the agent is not itself an issuer.
- Submit an authorised request. Ask the desired new issuer, or its Registration Agent, to initiate the move. LEI ROC guidance describes this as a one-stop-shop process requiring one request to the issuer that will maintain the record afterwards.
- Complete the required checks. The receiving issuer verifies that the person requesting the transfer is empowered to act for the entity and validates its reference data. Where a Registration Agent is involved, its process uses a Transfer Request Form signed by the entity’s authorised signatories.
- Check the resulting record. Look for the existing LEI under the new managing issuer in GLEIF LEI Search. If the entity decides to cancel while a transfer is in progress, ask the provider about the signed Transfer Objection Form and its cancellation process.
The GLEIF – Registration Agents Governance Framework v1.1 (2025) requires agents to present issuance, renewal and transfer as separate services and to say up front when renewal first requires a transfer to a different issuer. It also describes the Transfer Request Form and the signed Transfer Objection Form used if the entity cancels a transfer. An agent facilitates cancellation and any refund under its terms.
How long does it take, and what statuses might appear?
The GLEIF – Service Level Agreement, Appendix 06 v2.4 (2026) sets issuer targets of 4 LOU business days for the sending issuer and 3 LOU business days for the receiving issuer. These are separate service-level periods, not a promise that every request will finish after an exact combined interval. Once the LEI appears as ISSUED under the new issuer in GLEIF search, the old issuer has 1 LOU business day to unpublish its copy.
During a transfer, the LEI-CDF format defines PENDING_TRANSFER as a request being processed at the sending issuer. PENDING_ARCHIVAL means a record is about to be transferred and then reverts to a non-pending status; TRANSFERRED indicates that it has moved to a different managing issuer. Read a status together with the record’s managing issuer rather than assuming that every status describes the receiving issuer’s current record.
Transfer, renewal and the cost of moving
A transfer changes who maintains an existing LEI. Renewal is a separate service, while issuance concerns an entity that does not already have an LEI. If a provider proposes renewal through a different issuer, ask whether a transfer must happen first and what renewal term you are selecting. Do not submit a new LEI application merely to change providers.
The GLEIF – Master Agreement Appendix 05: LOU Contract Requirements requires issuer contracts to allow an entity to request transfer to its designated issuer, or to allow another issuer to request it on the entity’s behalf, with no fees assessed for the transfer request. The LEI ROC – Endorsement Note 1 (2013) likewise says the originating issuer should not charge a porting fee. That does not tell you the price of a renewal service from the new provider: review LEIFast prices and the terms offered for the service you select.
For other LEI topics, see the LEIFast blog. If you have checked the existing record and want to move its maintenance, request an LEI transfer through LEIFast using your current LEI and an authorised request.
FAQ
Does my LEI change when I transfer it?
No. The 20-character code stays the same, including its prefix. Only the managing issuer shown in the record changes.
Does the old issuer charge for a transfer?
No. GLEIF rules require issuer contracts to state that no fees are assessed for a transfer request, and the LEI ROC said the originating issuer should not charge a porting fee. You pay the new provider for the renewal term you choose.
How long does an LEI transfer take?
Under the GLEIF Service Level Agreement the sending issuer has 4 LOU business days and the receiving issuer 3 LOU business days.
Who has to start the transfer?
You make one request to the new issuer or its Registration Agent, signed by someone authorised to act for the entity. The new issuer then requests the record from the old one.