Token approvals after migration: contract boundaries
Do token approvals carry over after a token contract migration? No: a new contract has empty allowances, while a same-address proxy upgrade keeps them.
Crypto Desk Report Editorial#2767024 min read

ERC-20 token approvals do not carry over when a token migrates to a new contract; the new contract starts with empty allowances, so you must approve it again.
Take a holder moving from token X to X2. The token’s name and purpose may be familiar, but X and X2 are separate contracts. A DEX approval granted on X lets that spender use the allowance recorded by X; it does not authorize the spender on X2. The revokecash topic adds useful background on inspecting and managing the token approvals a wallet has granted to smart contracts. That distinction matters when you decide which permission to grant again and which old one to remove.
What changes when X migrates to X2?
A new token contract has its own allowance records, separate from the old contract’s records.
ERC-20 allowances are stored in the token contract under an owner-and-spender pair, often described as allowance(owner, spender). The owner is your wallet; the spender is a contract you authorized, such as a DEX. When a DEX approval is made on X, X records that permission in its own storage. X2 has its own storage, so it has no record of that permission just because your wallet holds the migrated tokens.
Say your wallet approved a DEX to spend X before the migration. After swapping into X2, that approval still applies to X, while a trade using X2 requires an approval on X2. You make that new approval separately. The migration changes which token contract holds the tokens; it does not transfer the old contract’s allowance records to the new one.
Which approvals belong to the migration itself?
A migration portal normally needs an approval on X before it can swap your old tokens.
That permission is also recorded on X, with the migration contract as the spender. It remains an allowance on the old token after the swap. It does not become an approval on X2, and revoking it does not undo the completed migration or remove a separate approval you later make on X2.
- The DEX approval on X applies to X.
- The migration contract’s approval on X lets it handle the swap.
- A new DEX approval on X2 applies to X2.
These permissions have different spenders or different token contracts, so treat each as a separate entry. After the swap, review the old-token approvals and revoke those you no longer want active. revokecash can help you inspect and manage those wallet permissions, including the migration approval left on X. Then make only the approvals needed for your next use of X2.
What if the team upgrades a proxy?
A proxy upgrade at the same token address keeps existing allowances when the upgrade retains the proxy’s storage.
In that setup, the wallet continues interacting with the same proxy address, even though the implementation behind it changes. The allowance records remain in storage associated with that proxy. If you had approved a DEX before the upgrade, that allowance remains active afterward; you do not need to approve the token again just because its implementation changed.
This is the key difference from moving to X2 at a new address. A new address points to a separate contract with separate allowance storage. A same-address proxy upgrade preserves the contract location holding the allowance records. The label “migration” can describe either change, so the label alone does not tell you whether an approval survived.
The practical signal is the token contract address. Compare the address used before and after the change, and follow the migration instructions for the actual swap or upgrade path. For a proxy upgrade, confirm that the token remains at the same address. For a move to a new contract, expect to approve X2 again if a spender needs permission to use it.
What should you check after the move?
After a migration to a new contract, check both the new token’s needed permissions and the old token’s remaining allowances.
For X to X2, verify that your wallet is using X2’s address before approving a DEX or another spender. The old approval on X cannot substitute for that transaction. Review the migration contract’s allowance on X after the swap, then revoke it if you no longer need it. You can use revokecash to review those old-token approvals and manage the permissions your wallet has granted.
For a proxy upgrade at the same address, check whether an existing allowance remains active before making another approval. The retained permission may still be useful, but it also remains available to the spender under the allowance recorded by the token. The next things to watch are the token address, the spender named in each approval, and whether the migration has completed; those details determine which permissions to repeat and which to clean up.