Pokémon HOME is stranding Champions teams in limbo – here’s what’s really breaking

When the service that exists to keep 25 years of caught, bred, and traded monsters safe starts stranding them in limbo, that’s more than just another launch-week bug. Right now, Pokémon HOME’s integration with Pokémon Champions is doing exactly that for some players – and it exposes how fragile the whole “forever home for your collection” promise really is.

• Pokémon sent from HOME to Pokémon Champions can fail mid-transfer, ending up flagged as “visiting” but inaccessible in both games.
• Error code 10015 is a common culprit, usually tied to HOME’s legitimacy checks and overloaded batch transfers, but not limited to obviously hacked Pokémon.
• No consistent fix exists yet: cache clears and reinstalls sometimes help, but there’s no reliable method to reclaim stuck monsters.
• The bigger issue is trust: if a backend glitch can wall off parts of your collection, HOME stops feeling like a safe, boring vault and starts feeling like another live-service risk.

HOME was supposed to be the safest part of modern Pokémon

Pokémon Champions launches as a free-to-start, competitive-focused battler on Switch, pitched as a streamlined way into VGC-style play. Early impressions have been blunt: some players are calling it “a fleshed-out beta” thanks to performance dips, a limited roster, missing staples like 6v6, and a grab bag of launch bugs.

In that context, Pokémon HOME is meant to be the stable backbone. For years, the pitch has been simple: move your monsters into Nintendo’s cloud, and they’re safe across generations. Champions tying into HOME is a big part of its value. With only around 30 slots in Champions’ own boxes, HOME essentially becomes the ranch and archive that makes the game usable for serious players.

That’s why this particular failure hits harder than a broken move interaction or a temporary ladder shutdown. Bugs in a new competitive spin-off are expected. Bugs that make you doubt whether it’s safe to park your living dex or tournament-ready teams in HOME are not.

How Pokémon are getting trapped “visiting” Champions

The basic flow, on paper, is straightforward. On Switch, you open Pokémon HOME, pick the Champions icon, and move selected Pokémon in as temporary visitors. On mobile, you can trigger a similar “Send for a Visit” option. Those Pokémon remain registered in HOME but become usable inside Champions, a neat way to get around the game’s small box limit.

In practice, a growing number of players report a darker version of that story. Transfers to Champions fail partway through, throwing a generic “an error has occurred, returning to the title screen” message or a specific error code. After that, affected Pokémon:

• Show up in HOME as “visiting another title”,
• Do not appear in Champions as usable Pokémon, and
• Can’t be moved back to HOME storage or into other linked games like Scarlet and Violet.

They’re not deleted – they still exist in HOME’s database – but they’re functionally locked away. Some players report entire teams’ worth of monsters stuck in this state. Others see only a handful of specific Pokémon get trapped while the rest of the batch moves fine.

Reports mention both the Switch and mobile versions of HOME, covering everything from in-game-bred competitive Pokémon to long-carried-over legendaries. Attempts to clear the HOME cache, reinstall the app, or re-link accounts occasionally free a few stuck creatures, but nothing is consistent enough to be called a fix. As of now, The Pokémon Company has not publicly detailed the issue or offered an official recovery path.

Error 10015, legitimacy checks, and why transfers actually fail

Under the hood, Pokémon HOME isn’t just storage; it’s also an automated referee. Every time you move a monster between games, server-side checks quietly decide whether that Pokémon is “legal” for the target format. That’s where error code 10015 comes in – and it’s at the center of many Champions transfer failures.

Community testing over the past few years has built a rough profile of 10015:

• It commonly appears when a Pokémon fails legitimacy checks – hacked stats, impossible movesets, non-native species with bad data, or clumsy genned and cloned monsters.
• It’s more likely to appear when you transfer large batches of Pokémon, especially entire boxes, increasing the chance that one bad egg poisons the whole move.
• Sometimes, it hits perfectly legitimate, self-caught Pokémon, which suggests either overly aggressive validation rules, bad data flags, or bugs in how specific species/forms are handled.

With Champions now in the mix, HOME is running those same checks when you send Pokémon “for a visit” to the new game. If anything in the batch looks suspicious to the backend – or if Champions’ own data expectations don’t align perfectly – the transfer can choke. Instead of rolling back cleanly, some Pokémon end up stuck in that “visiting” state with no valid destination.

Crucially, there’s no hard evidence yet that this only affects hacked or edited Pokémon. Yes, obviously illegitimate monsters are at higher risk, and HOME has always been designed to wall them off. But enough reports involve standard-raised, in-game-bred, or event-distributed Pokémon that it’s safe to say the net is catching more than just cheaters.

The pattern aligns with three overlapping issues rather than a single smoking gun:

• Strict or inconsistent legitimacy rules around Champions, especially with older or edge-case species.
• Batch-transfer fragility, where one problematic Pokémon can corrupt the state of an entire move.
• Insufficient rollback behavior: when a transfer fails, the system doesn’t always revert every affected Pokémon to a clean, accessible state in HOME.

That last point is the one that matters most. Bugs in a brand-new game are expected. Bugs in the service that holds your entire collection, without robust rollbacks, are design failures.

This is a trust problem, not just another launch-week bug

Pokémon has always been built on trading and battling – the Game Boy link cable era to cloud storage and online VGC circuits. Pokémon HOME is the modern version of that cable, except now it’s also the vault that stores your history: shinies from the 3DS Virtual Console, event mythicals, breed projects spanning multiple generations.

When that vault starts behaving unpredictably, a lot more is at stake than a single game’s meta. For casual players, it’s emotional investment in favorite monsters they’ve carried for a decade. For competitive players, it’s their tournament roster, battle-ready spreads, and years of breeding and training. For both, the implicit deal was clear: pay for HOME, follow the rules, and your collection is safe.

Pokémon Champions was supposed to be a new competitive front-end on top of that stable infrastructure. Instead, its launch has highlighted how brittle that infrastructure can be under pressure. The uncomfortable question for The Pokémon Company is simple: why does a failed transfer ever leave a Pokémon in a half-moved, inaccessible state?

Any system that treats a failed write as final – without automatic, guaranteed rollback to the last known good state – is asking for exactly this kind of user-facing disaster. That’s the part the PR copy won’t mention, but it’s the part that matters if you’re deciding how much of your collection you’re willing to risk tying into new titles.

Practical damage control: how to use HOME safely right now

Until there’s a confirmed fix, the safest approach is to treat Champions integration as unstable infrastructure. That doesn’t mean you can’t touch it at all, but you should manage your risk like your collection actually matters – because it does.

• Do not send irreplaceable Pokémon into Champions. Anything with sentimental value, hard-to-replace event status, or origins in older generations should stay in HOME or your mainline games for now.
• Start with expendable test batches. If you want to experiment with Champions, begin by sending a handful of common or low-value Pokémon. Confirm that they appear in Champions and can be returned to HOME before scaling up.
• Keep transfer sizes small. Avoid full-box moves. Community experience with 10015 suggests that one problematic Pokémon can cause the whole batch to fail. Moving one box or fewer at a time reduces blast radius and makes it easier to isolate troublemakers.
• Avoid anything with questionable origins. Even if you didn’t create hacked or genned Pokémon yourself, anything acquired from random trades or external tools is a risk factor. Keep them out of Champions until the system is better understood.
• Verify the return path often. After each successful batch, move a subset back from Champions to HOME or another linked game to ensure the round-trip still works.
• Document what matters. Screenshots of your most important Pokémon – including OT, ID, and markings – won’t fix a bug, but they’ll be invaluable if support ever needs to track or verify missing monsters.

If you already have Pokémon stuck as “visiting” Champions, basic troubleshooting – clearing the HOME cache, reinstalling the app, fully closing and reopening Champions – is worth trying once. Just don’t keep hammering the system with additional transfers in the hope that it will sort itself out; every extra move is another chance for more Pokémon to end up in limbo.

What a real fix needs to look like

For this to be more than a warning story, Pokémon HOME and Champions need more than a quiet, backend hotfix. A serious response would include:

• A server-side cleanup pass that identifies all Pokémon flagged as “visiting” Champions without a valid save entry and returns them to standard HOME storage.
• Stricter transactional behavior for future transfers: either a Pokémon moves cleanly to its destination or it remains fully accessible where it started, with no in-between state visible to users.
• Clear documentation of error codes like 10015, including whether they are strictly legitimacy-related or can be caused by server-load and batch issues.
• Transparent policy on illegitimate Pokémon that distinguishes intentional cheating from false positives and explains what happens to flagged monsters.
• A willingness to disable or limit Champions–HOME transfers temporarily if they can’t be guaranteed safe, rather than leaving a known-risk integration live.

For players, the practical takeaway is straightforward: treat HOME as critical infrastructure and plan around its current failure modes. Until we see explicit confirmation that stranded Pokémon have been restored and the underlying logic hardened, use Champions integration conservatively, back up what you can, and assume that any transfer pathway can break under the wrong conditions.

What to watch next

• The next Pokémon Champions patch notes: if HOME integration or transfer stability is mentioned explicitly, that’s the first signal a real fix is underway.
• Scheduled Pokémon HOME maintenance windows: backend work without fanfare is often where cross-title issues like this are actually resolved.
• An official statement from The Pokémon Company: acknowledgment of stuck “visiting” Pokémon and a recovery commitment would go a long way toward restoring trust.
• Competitive community guidance: if prominent VGC players and organizers begin advising against using Champions with HOME teams, expect the issue to get elevated faster.
• Change in error patterns: a visible drop in 10015 reports on transfers to Champions will be the practical sign that legitimacy checks and rollback behavior have been adjusted.

TL;DR

Pokémon HOME’s integration with Pokémon Champions is currently unstable, with some transfers failing and leaving monsters stuck as “visiting” and unusable. Error code 10015 and shaky rollback behavior mean both hacked and legitimate Pokémon can end up trapped in database limbo instead of safely returning to storage. Until there’s a confirmed fix, keep high-value monsters out of Champions, move only in small test batches, and treat HOME less like an unbreakable vault and more like critical infrastructure that still has weak points.