If an email or message asks you to upgrade your name, don't use its link. Check your name on app.ens.domains.
A name can't upgrade to ENSv2 for a few usual reasons: a wrapped name has certain permissions revoked, a subname's parent hasn't upgraded, or a name has records the upgrade can't carry. Most wrapped names upgrade as they are, with no need to unwrap.
Why don't I see the upgrade banner?
You may have no names to upgrade. To check:
Connect the wallet that owns the name in the ENS App.
Open your dashboard and select the V1 filter.
If V1 shows no names, that wallet only holds ENSv2 names. There is nothing to upgrade.
A name registered since ENSv2 launched on 27 October is an ENSv2 name from the start, so it never needs an upgrade.
If V1 lists names that won't upgrade, see the reasons below.
Wrapped names with a revoked permission
A wrapped name has permission switches called fuses. Burning a fuse revokes a permission for good. A wrapped name can't upgrade if Cannot Transfer is burnt, or if Cannot Approve is burnt while the name has a live approval. The old ENS App called these "Cannot send this name" and "Cannot change renewal manager" (pictures below).
Cannot Transfer: the name can't be transferred.
Cannot Approve: the approved "subname renewal manager" can't be updated.
 |  |
Check your wrapped name's fuses
Open your name in ENS Explorer and select Fuses in the sidebar. Find Cannot Transfer and Cannot Approve in the table. A fuse is burnt when its Burnt column shows True.
If neither fuse is burnt, check the cases below. If none fit, contact support with the name.
Records the upgrade can't carry
The ENS App may show one of these messages, with what to do:
yourname.eth has a legacy content record that this upgrade cannot preserve: update it to a content hash record, then upgrade. Or deselect the name and upgrade the rest.
yourname.eth has primary-name records or DNS history that this upgrade cannot preserve: deselect the name to keep its records. It stays on ENSv1, still working.
A name in its grace period
A name in its grace period (the window after it expires) can upgrade. The upgrade page lists it on its own, under a heading such as 1 NAME IN GRACE PERIOD, unticked: tick it to include it. The ENS App renews the name first, paid in stablecoins (USDC), then upgrades it, so your wallet also asks you to approve that payment. If your wallet doesn't hold enough USDC, the page says Your wallet needs more USDC to renew these names.
Why won't my subname upgrade?
A subname (for example sub.name.eth, whose parent is name.eth) can't upgrade ahead of its parent. Unless the ENS App says otherwise, it can only come across inside the parent's upgrade. What to do depends on what the ENS App says.
This subname must be included through its parent name. It cannot be copied on its own: the parent's owner upgrades the parent, and the subname comes across with it if the ENS App can bring it.
The parent name … must be upgraded before this subname: the parent has given up control of this subname, so it takes its own upgrade. Upgrade the parent first, then the wallet that holds the subname upgrades it.
its parent name, or one above it, was upgraded without it: contact support with the name.
Subname copying is not available in this session, shown on a name that has subnames: the ENS App can't bring its subnames yet. Keep the name on ENSv1 for now; its subnames keep working.
These subnames can't be preserved yet: one cause is a subname with subnames of its own (for example
shop.sub.name.eth, belowsub.name.eth). The ENS App can't bring those across yet, so the name you're upgrading (herename.eth) stays on ENSv1 and its subnames keep working. To upgrade now, delete the subnames below that subname in ENS Explorer (see Create a subname (ENS Explorer)), then try again. A deleted subname stops working, so first check nobody relies on it. If one can't be deleted, or the name has more than 200 subnames, keep the name on ENSv1 and contact support.The permanent case: the parent gave up control of the subname ("Give up ownership"), and then the subname's own permissions were revoked. Once "Cannot send this name" is revoked, or "Cannot change renewal manager" is revoked while a subname renewal manager is set, the subname can't upgrade. It stays on ENSv1, still working.
This subname's parent or registry is not supported for upgrading yet. The subname stays on ENSv1, still working.
Other upgrade problems
A subname shows a code in [square brackets]
Only a hashed form of this subname's name was ever saved onchain, so the upgrade can't recreate it. Nothing is wrong with your name.
Up to 5 of these under one name, none with subnames of its own: the name can still upgrade. Tick I understand these subnames will stop working after the upgrade. and select Continue migration. They then stop working and can't be upgraded later. To keep them, keep the name on ENSv1.
More than 5 of these, or one with subnames of its own: the name can't be upgraded yet. Keep it on ENSv1 and contact support.
A subname's complete name could not be verified: keep the name on ENSv1 and contact support.
My upgrade stopped partway
Open your dashboard: the You're almost there! card below My Names shows your progress. If it keeps failing, contact support with the name and the error you see.
I can't find my name
Every name you own shows in ENS Explorer, upgraded or not, and in the ENS App too: on your dashboard, names you haven't upgraded sit under the V1 filter. If a name doesn't show in the ENS App, search for it in ENS Explorer. If it isn't there either, contact support with the name.
Common questions
Can I undo a revoked permission so my name can upgrade?
No. A burnt fuse can't be unburnt, so a name blocked for either reason stays on ENSv1, still working. You can manage it in ENS Explorer.
Can I upgrade if I've lost my Manager wallet?
Yes. The owner wallet starts the upgrade, so the Manager wallet doesn't need to approve anything. To see which wallet is the owner, open the name in ENS Explorer, where Ownership in the sidebar shows Owner and Manager. See What happened to the Manager role?
What happens to a wrapped name's permissions when it upgrades?
A locked wrapped name that can upgrade carries its burnt fuses across to ENSv2 as roles.