A digital persona is more than a profile photo or username: it can include linked accounts, authentication methods, verification records, content, permissions, and trusted contacts. This reusable runbook explains how to recover or migrate that identity without losing access, weakening security, or exposing unnecessary personal data.
Overview
Digital persona recovery and account migration are related but different tasks. Recovery restores control after a lost device, forgotten credential, locked account, or suspected compromise. Migration moves an existing online identity to a new provider, domain, workspace, device, authentication system, or operating model. Both require more than changing a password.
A useful continuity plan treats the persona as a collection of connected assets:
- Accounts and identifiers: usernames, email addresses, domains, profile URLs, and organization memberships.
- Authentication: passwords, passkeys, security keys, authenticator apps, backup codes, recovery email addresses, and phone numbers.
- Trust records: identity verification, signed documents, certificates, credentials, account history, and administrator approvals.
- Content and configuration: profile data, messages, contacts, avatar files, permissions, integrations, and consent records.
- Sessions and devices: browsers, mobile devices, API tokens, OAuth connections, and active sessions.
Before taking action, decide whether the work is routine migration, emergency recovery, or employee or contractor offboarding. The same inventory is useful in each case, but the order of operations changes. During a suspected compromise, preserve evidence and secure access first. During a planned migration, export and validate data before disabling the old environment.
For a broader risk review, use the digital identity threat modeling checklist. If the persona is being created for a team or application, the secure cloud persona onboarding guide can help establish controls before migration begins.
Checklist by scenario
Planned account or provider migration
- Define the destination. Record the new provider, workspace, domain, administrator, expected cutover date, and rollback plan. Confirm which data and functions must remain available.
- Build an account inventory. List the primary account, aliases, linked social profiles, messaging identities, cloud storage, payment or billing contacts, developer integrations, and services that use the account for sign-in.
- Export before changing settings. Request available exports for profile information, contacts, messages, files, audit records, and configuration. Treat an export as a copy, not proof that every feature or permission will transfer.
- Record dependencies. Identify websites, applications, webhooks, OAuth clients, DNS records, email forwarding rules, signing certificates, and API credentials that depend on the old identity.
- Prepare the new authentication path. Add the replacement email or administrator, enroll more than one approved recovery method, and test sign-in from a controlled device before cutover.
- Transfer verification carefully. Revalidate the identity with the destination provider when required. Do not assume that a verified status, badge, credential, or signed-document history automatically carries over.
- Compare the result. Check profile fields, public visibility, avatar or brand assets, access roles, consent records, integrations, and recovery contacts against the original inventory.
- Revoke the old path last. Keep the old account available for the agreed transition period, then remove sessions, tokens, forwarding rules, and administrator access that are no longer needed.
Lost device, locked account, or forgotten credentials
- Use the provider's official recovery process from a known device or trusted network. Avoid links delivered through unsolicited messages.
- Secure the email account that receives recovery messages. If that mailbox is also at risk, recover it before attempting connected services.
- Use saved backup codes, a registered security key, a passkey on another approved device, or an established recovery contact where available.
- After access returns, change the primary credential, review recovery details, and remove unfamiliar devices, applications, sessions, and forwarding rules.
- Check for changes to profile data, payment details, messaging rules, avatar assets, and connected applications. Save evidence of suspicious activity before deleting it.
The companion digital identity recovery plan provides a focused checklist for backup codes, trusted contacts, and restoration steps.
Suspected compromise or impersonation
- Preserve relevant evidence: timestamps, messages, login alerts, profile URLs, screenshots, headers, and transaction records.
- Secure the primary email and identity provider before changing every connected account. An attacker who retains mailbox access may reset the changes.
- Rotate passwords and tokens from a clean device. Prioritize administrator accounts, financial services, domain controls, developer systems, and accounts that can reset others.
- Revoke active sessions, OAuth grants, API keys, and recovery methods that cannot be verified.
- Notify affected contacts through a separate trusted channel and report fake profiles or fraudulent messages to the relevant platform.
For a fuller response sequence, see the digital impersonation response plan. If identity data appears in tokens or signed files, avoid pasting sensitive material into an untrusted online utility; the JWT decoder and hash generator safety guide explains a safer inspection workflow.
Employee, contractor, or team-member offboarding
- Confirm the person's role, approved end time, legal or contractual retention requirements, and business owner for each asset.
- Transfer ownership of files, domains, profiles, signing accounts, repositories, automation, and shared mailboxes before disabling the user.
- Disable sign-in, revoke sessions and tokens, remove recovery methods, rotate shared secrets, and review delegated access.
- Preserve necessary consent records, audit logs, signed documents, and communications without retaining personal data that the organization no longer needs.
- Test that the successor can perform essential functions without using the departing person's private credentials or personal recovery channel.
What to double-check
Authentication and recovery
Confirm that at least two recovery routes are usable and controlled by the right person or team. Test them without triggering a destructive reset. Check whether passkeys, security keys, authenticator devices, and backup codes are documented, labeled, and stored separately from the account they protect. For organizational rollouts, review the passkey compatibility and recovery checklist.
Data, privacy, and consent
Separate data that must be migrated from data that is merely convenient to keep. Review public profile fields, hidden metadata, contact lists, location information, message history, avatar source files, and voice or likeness permissions. A new provider may use different visibility defaults, retention settings, or sharing controls. Recheck them instead of copying the old configuration blindly.
Trust and verification
Document which claims were verified, by whom, and for what purpose. A profile label is not equivalent to a cryptographic signature, and a copied image is not proof of identity. When moving signed documents or certificates, preserve the original file and verification context. The guide on verifying digital signatures covers certificates, trust, and tampering checks.
Technical dependencies
Test sign-in, email delivery, profile links, API calls, webhooks, domain routing, document signing, and administrator escalation. If the persona uses verifiable credentials or a digital wallet, record the issuer, holder, recovery process, and revocation expectations before changing systems. See verifiable credentials versus digital identity wallets for the distinction.
Common mistakes
- Changing the email first and investigating later: This can break recovery notifications, forwarding, and service dependencies. Inventory the system before changing its anchor identity.
- Assuming an export is complete: Exports may omit permissions, active sessions, private messages, integrations, or verification history. Compare the export with a human-readable inventory.
- Keeping credentials in a shared document: Store secrets in an appropriate password manager or secrets system, with access and ownership defined.
- Leaving the old account active indefinitely: A transition account that no longer has an owner becomes a future attack and privacy risk.
- Revoking everything before testing the replacement: Validate the destination, recovery route, and critical workflows first. Keep a documented rollback window when practical.
- Copying identity assets without rights review: Avatar files, voice models, signatures, and brand elements may have consent or licensing conditions. The AI avatar content rights checklist is useful when a virtual persona is part of the migration.
- Using real secrets in debugging tools: Redact tokens, personal identifiers, private keys, and recovery codes before inspection or support requests. For developer workflows, consult the JWT, hashes, and signed documents guide.
When to revisit
Review this runbook before a seasonal planning cycle, provider change, domain transfer, device replacement, major authentication update, team reorganization, or new avatar and messaging workflow. Revisit it immediately after a suspected compromise, failed recovery attempt, unexpected verification request, or change in data-retention requirements.
At least twice a year, run a small continuity test. Confirm that the named owner still has access, recovery contacts are current, backup codes can be located, exports can be opened, and a second authorized person understands the restoration sequence. Do not wait for an incident to discover that a recovery email belongs to a former employee or that an API token has no documented owner.
Finish each review with three records: an updated asset inventory, a list of changes and unresolved risks, and the date and owner of the next test. That simple habit turns digital identity recovery from an emergency improvisation into a repeatable cloud persona continuity plan.