Moving a creator, gaming, or web3 identity is more than changing a username. This reusable digital identity migration checklist helps you map dependencies, protect account access, preserve community trust, and confirm that every old profile points people to the right destination.
Overview
A digital identity is the collection of handles, profile pages, bios, links, domains, avatars, wallet connections, verification signals, and community expectations associated with you or your project. When one part changes, the other parts may need to change with it.
A migration can involve moving to a new social platform, changing a creator name, transferring a community to a new domain, replacing a gaming avatar, connecting a different wallet, or relaunching a web3 profile. The goal is not to make every property identical. The goal is to make the relationship between them clear and secure.
Begin with a dependency map. List each identity asset, where it lives, who controls it, what it links to, and what must happen before it can be changed. Separate public information from sensitive recovery data. Never place seed phrases, private keys, backup codes, or other secrets in a migration document.
| Identity element | Before migration | After migration | Verification task |
|---|---|---|---|
| Handle and display name | Record the current spelling and variations | Reserve or confirm the new name | Search for conflicts and impersonation risks |
| Bio and profile links | Save the current copy and destinations | Replace links with the approved home base | Open every link while logged out |
| Domain | Record registrar and DNS access | Point it to the new destination or landing page | Test redirects, HTTPS, and canonical URLs |
| Wallet address | Document the public address and services using it | Connect or announce the replacement only when ready | Confirm the address through an independent channel |
| Avatar assets | Inventory source files, licenses, and crops | Upload approved versions in required formats | Check ownership, permissions, and visual consistency |
| Recovery and verification | Review sign-in methods and recovery contacts | Update them before closing or abandoning accounts | Complete a test sign-in without exposing secrets |
Checklist by scenario
Moving social media accounts or changing a handle
- Choose a primary identity: your website, domain, or most trusted active profile.
- Check the platform's current rules for renaming, redirects, verification, account exports, and account deletion. Treat these rules as changeable inputs.
- Reserve the intended handle before announcing the change, where the platform permits it.
- Capture the old bio, profile image, banner, pinned post, contact address, and important links.
- Update the new profile with a familiar avatar, a clear explanation, and one authoritative destination.
- Keep the old account visible when possible. Pin a migration notice rather than deleting it immediately.
- Ask trusted community members to test the new profile and report broken links or confusing search results.
Rebranding a creator, gaming, or community persona
- Define what is changing: name, visual identity, audience promise, content topic, or all four.
- Create an asset inventory for avatars, banners, emotes, thumbnails, logos, usernames, domain names, and downloadable files.
- Confirm that you can use each avatar and graphic on the intended social, gaming, and web3 profiles. The Digital Avatar Licensing Guide can help organize these checks.
- Prepare a before-and-after explanation in plain language. Tell people what remains the same and what they should update.
- Publish the announcement from established channels before changing every property, so followers have context.
- Use consistent profile images and descriptions during the transition, then replace them in a planned sequence.
- Monitor replies, community servers, search results, and old links for confusion or impersonation.
Changing a web3 wallet or wallet-linked profile
- Decide whether the change affects sign-in, public reputation, collectibles, payments, ownership, or only the profile connection.
- Record the public addresses involved, but keep private keys and recovery phrases offline and private.
- Review each connected service and determine whether it supports changing the connected wallet, transferring ownership, or exporting data.
- Use the service's official interface and verify the domain before signing a transaction or message.
- Update the profile bio, ENS name or other decentralized name, social links, and community announcements together.
- Explain what the old address represents and what the new address should be used for. Avoid implying that an address is safe or official without a verification process.
- Review wallet permissions and connected applications after the transition. For related preparation, see the Web3 Profile Security checklist and the guide to onchain reputation for creators.
Moving to a new domain or home base
- Publish the new site before changing your most visible profiles.
- Redirect old pages to the closest relevant new page rather than sending every visitor to an unrelated homepage.
- Update profile links, email signatures, link-in-bio pages, newsletters, community documentation, and pinned announcements.
- Retain control of the old domain and important accounts for a reasonable transition period when possible.
- Test redirects in a private browser window and from mobile devices. Check for loops, expired certificates, and outdated destination links.
What to double-check
Handles and name availability: A handle may be unavailable, reserved, case-sensitive, or subject to a platform's rename limitations. Record exact spellings and avoid relying on a visual similarity as proof of identity. A consistent naming plan is easier to maintain when you first review your username, handle, and domain strategy.
Links and redirects: Test links while signed out, because a link that works for an administrator may fail for visitors. Check shortened URLs, QR codes, embedded links, and old campaign pages as well as profile bios.
Wallet details: Confirm public addresses through a known, independent channel. Treat unexpected requests to “verify” ownership, migrate assets, or reconnect a wallet as a security warning. A wallet transition is also a useful time to review the principles in the privacy-first digital identity guide.
Verification: Do not assume a badge, creator label, domain connection, or wallet signature will carry over. Check the current requirements directly in the relevant product. If verification is important to trust, explain how followers can identify the official profile without asking them to share credentials or sign unfamiliar transactions.
Recovery: Before abandoning an old account, update its recovery email, phone number, authenticator, backup codes, and trusted devices. Remove former collaborators where appropriate. Keep an emergency contact plan separate from public migration notes.
Community continuity: Give moderators, collaborators, and regular members the same short explanation. Provide one official destination and a date for the transition. If the identity is privacy-sensitive, share only what the audience needs to distinguish the real profile from an impersonator.
Common mistakes
- Changing everything at once: A simultaneous rename, avatar change, domain move, and wallet switch makes errors hard to isolate. Use staged changes and keep a written change log.
- Deleting the old profile too early: An old profile may still be the first result people find. Keep a clear notice and link where platform rules allow.
- Using an unverified announcement link: Post migration instructions from an established profile and repeat the destination on your primary domain or another trusted channel.
- Confusing a new wallet with a new reputation: A new address may not carry historical context, memberships, or records. Explain the change without overstating continuity.
- Reusing sensitive recovery information: Migration documents should contain ownership responsibilities and public identifiers, never secrets.
- Ignoring avatar rights: A profile image may be visually available but not licensed for every use. Keep source files, permissions, and attribution requirements with the asset inventory.
- Failing to tell collaborators: Editors, moderators, sponsors, and community managers may continue linking to the old identity unless they receive the new profile map.
When to revisit
Run this checklist before a rebrand, username change, platform move, wallet transition, domain launch, avatar replacement, or community relaunch. Also review it before seasonal planning cycles, when a collaborator leaves, or when a new sign-in or profile tool becomes part of your workflow.
Platform export options, rename rules, verification requirements, connection flows, redirect behavior, and account-deletion policies can change. Recheck those details every six months and after a major product update rather than treating an old migration plan as permanent.
For a practical final pass, open your identity inventory and mark each item as confirmed, needs action, or not applicable. Then:
- Confirm the primary destination and publish it on the profiles you control.
- Test every public link, redirect, avatar, and pinned announcement.
- Verify wallet addresses and sign-in methods using official interfaces.
- Ask someone who does not manage the accounts to follow the journey as a visitor.
- Record unresolved issues, owners, and a review date.
- After the migration, conduct a short identity audit and monitor for impersonation or outdated links.
A careful migration does not require every platform to look identical. It requires each public touchpoint to tell the same basic story: who you are, where the official home is, how the community can verify it, and what has changed.