What PokéBank compatibility means in practice
PokéBank compatibility determines which Pokémon titles, console firmware, and operating systems can communicate with the bank service for transfers and storage. Designed to move Pokémon between games, compatibility depends on generation, title version, and active services such as Pokémon HOME and Nintendo Switch Online. When compatibility is misaligned, transfers fail, data can appear locked, and events may become unavailable. This guide explains game-by-game support, platform requirements, and practical steps to confirm compatibility before initiating any transfer, ensuring reliable moves and long-term account use.
PokéBank and core system requirements
At a foundational level, PokéBank compatibility depends on supported operating systems, up-to-date application versions, and an active Nintendo Switch Online membership (for cloud saves and Home interaction). Stable internet, sufficient console storage, and correctly linked Nintendo Accounts are prerequisites that affect success rates and troubleshooting clarity.
Platform and account essentials
- Nintendo Switch running system firmware updated to the latest official build
- Nintendo 3DS family system firmware brought to the latest version
- Active Nintendo Switch Online membership where required
- Up-to-date PokéBank, Pokémon HOME, and affected game patches applied
- Nintendo Account correctly linked and authenticated on each device
Compatibility by Pokémon title and generation
Each main-series title supports a defined set of generations, and PokéBank compatibility varies by whether a game can both send to and receive from the bank. Transfer rules differ between core series, side games, and event distributions, so confirming bidirectional support reduces errors and blocked opportunities.
Key compatibility details by game
| Game | PokéBank Compatible | Transfer Direction Supported | Notes and Requirements |
|---|---|---|---|
| Pokémon Bank (3DS) | Yes | Legacy exports to Sun/Moon/USUM/Let’s Go | Requires 3DS firmware and active services; no direct Gen VIII↔Gen VII in Bank alone |
| Pokémon Sun/Moon/Ultra Sun/Ultra Moon | Yes (via Bank) | Bank → USUM and USUM → Bank | Needs patch availability and HOME for some distributions |
| Pokémon: Let’s Go, Pikachu! & Eevee! | Yes (limited) | Bank → GO; GO → Bank (capped species) | Only select Pokémon can exit; event rules apply |
| Pokémon Sword/Shield | Yes (through HOME) | HOME → Sword/Shield and vice versa | Depends on Pokémon HOME integration; DLC may expand pool |
| Pokémon Brilliant Diamond/Shining Pearl | Yes (via HOME) | HOME → BDSP and BDSP → HOME | Limited to available BDSP species; event distribution follows HOME rules |
| Pokémon Legends: Arceus | Yes (via HOME) | HOME → Legends: Arceus | Restricted species list applies; transfer impacts research tasks |
| Pokémon Scarlet/Violet | Yes (via HOME) | HOME → SV and linked future titles | Current endpoint in HOME chain; species and form availability vary by event rules |
| Pokémon HOME (Switch/Mobile) | Yes | Acts as central relay between titles and Bank |
Event, form, and version-specific restrictions
Even when PokéBank compatibility is marked as supported, specific distributions, event legality, and form rules can block moves. Cosmog line events, Mythical distributions, and version exclusives often enforce additional checks such as OT limitations, fixed met locations, and permitted moves. Always verify event legality for destination generations before committing transfers, because incompatibility at the event or legality layer can cause rejections or soft locks.
Troubleshooting common compatibility issues
When transfers fail, many issues trace to outdated software, interrupted links, or mismatched expectations about which species and forms are allowed. Systematic checks—patch verification, HOME party legality, account linkage, and region alignment—resolve most problems without external tools. If a transfer stalls, pause, confirm prerequisites, consult HOME and title status screens, and, when needed, use official support channels with logs rather than repeated attempts that risk partial states.
Long-term planning with PokéBank compatibility
Because services and supported titles can change, treating PokéBank compatibility as part of ongoing preservation planning helps future-proof transfers. Track HOME roadmap updates, monitor official patches, and schedule compatibility checks before major title launches or account changes. Maintaining current backups, recording transfer histories per title, and aligning event schedules with known compatibility windows reduce risk and support continuity across generations.