Note: The ENS App and ENS Explorer are both currently on Sepolia testnet. Behaviour and available features may change before mainnet.
Most wrapped names migrate to ENSv2 without any special handling. The permissions you set on the old system carry across — they just stop being called fuses and start being called roles.
Fuses become roles
On ENSv1, locking a name down meant burning a fuse: a one-way switch that permanently removed an ability. ENSv2 does the same job with roles, which are permissions held by an address and can be granted or revoked.
Migration translates between the two. A fuse you burned becomes the matching role left unheld, so the restriction survives the move. Nothing you locked comes unlocked.
What looks different afterwards
The Fuses tab is replaced by a Roles tab. Instead of a list of abilities you've burned, you see a table of who holds which permission.
Permissions are no longer one-way. On ENSv2 you can revoke a role and, if you hold the matching admin role, grant it again. Fuses could never be restored.
Your name's token ID changes, and will change again whenever roles change. See Change owner & transfer a name.
Locked subnames
If your name has subnames that were locked on ENSv1, they need somewhere to keep those restrictions. Migration gives the name a wrapper registry — a subregistry that preserves the old locking behaviour — and the subnames move into it. You don't set this up; it happens as part of the migration.
Names that can't migrate
A small number of wrapped names are blocked, usually because a permission was burned that stops the name being moved at all. If your name won't migrate, see Why can't I migrate my wrapped name or subname? — it covers both the fixable and the permanent cases.
Common questions
Do I lose the protections I burned fuses for?
No. They convert to the equivalent role restriction and carry across.
Can I unlock a name after migrating that I'd locked on ENSv1?
No. A restriction that was permanent on ENSv1 stays permanent after migration — converting it to a role doesn't reopen it.
Do I need to migrate my subnames separately?
Migrate the parent first. A subname can't move ahead of its parent.
Does my name need unwrapping first?
No. Wrapped names migrate as they are.