Distinguish Changing Devices From Changing Accounts First
Changing devices on one platform, renaming, changing clients, and switching platforms are different changes. Explain more than 'I changed phones.' Give previous and current platforms and full in-game identifiers, keeping ordinary records of prior project ownership. Do not expose passwords as proof or expect all resources transferred solely because names look similar.
Why Important Permissions Should Wait
Claims, balances, and plugin data may use different identifiers, and actual mapping and linking are unspecified. Pause transfers and authorization until identity is checked to reduce mistaken recipients. Ordinary visits and questions may continue. After maintenance clarification, verify each affected data item rather than treat 'Linked successfully' as a substitute for every result check.
When Balances or Skins Differ
Record the current platform, identifier, and display before interpreting differences as theft. Skins and resource ownership are separate data and may need separate handling. Explain what changed and when it was last normal. Confirm key identity before trading; matching appearances are not sufficient recipient identification.
Confirmation Checklist After Migration
Check accessible former buildings, correctly mapped claim permissions, items others still hold, and unsettled trades. Check only actual relevant features; unspecified email linking, account synchronization, and automatic merging are not mandatory steps. Leave one clear result note so collaborators know your current identifier.