Roster Sharing Must Transfer in NHL 26/27 - It’s Time
For the last two years, the community has been carrying NHL games on its back.
I’ve seen people recreate:
- Full 1990s NHL rosters
- NHL 04, 06, 2010, 2014 throwback seasons
- Entire NCAA programs
- Full custom leagues
- Even deep builds like GTHL and OMHA AAA circuits
And every single year? It all gets wiped. Deleted. Reset. Gone.
Meanwhile, Madden — another EA title — allows roster imports from the previous year.
So the question is simple: Why doesn’t NHL?
The Problem: Creative Work Gets Erased Every Year
Building a custom roster isn’t casual.
It takes:
- Hundreds of hours
- Accurate player builds
- Ratings balancing
- Jersey numbers
- Equipment edits
- Face builds
- Contract setups
- League structure tweaks
- Team creation
- Logo matching
This isn’t a weekend project. It’s an entire season commitment. And for what? So it can exist for a few months… and then vanish when the next game drops?
That kills motivation.
Why would anyone spend an entire year building out a fully playable NCAA system, or a 2010 NHL recreation, or a full GTHL AAA league — knowing it won’t transfer forward?
Madden Already Solved This
EA already has the infrastructure.
Madden lets you:
- Import draft classes
- Carry over franchises
- Transfer custom teams/rosters year to year
Same publisher. Same ecosystem. Same console generation.
So how is roster continuity not already standard in NHL after two years of roster sharing being in the game?
This isn’t a new feature request. It’s a missing foundational system.
Why Roster Transfer Is Mandatory:
Roster sharing isn’t just about downloading something cool for a few months.
The entire point is:
- Long-term league building
- Community collaboration
- Annual updating
- Version improvements
- Historical preservation
If I build a full OMHA AAA league, the vision isn’t “use this for six months.”
The vision is:
- Let others download it
- Let them tweak and update it
- Let it evolve year over year
- Let it become the definitive version
Without carryover, that never happens. The ecosystem resets every fall. That discourages creators. And without creators? Roster sharing dies.
What Happens Without It:
Here’s the reality:
- Fewer people invest time
- High-effort rosters disappear
- Casual, low-effort uploads dominate
- Community depth declines
- The mode loses long-term value
It becomes temporary content instead of an evolving universe. Which is the opposite of what roster sharing should be.
The Bigger Picture
Sports games thrive on:
- Customization
- Legacy
- Community effort
- Long-term engagement
Right now, NHL’s roster sharing feels disposable, and that’s a problem.
If EA wants:
- More engagement
- More time spent in creation
- More online downloads
- A stronger community ecosystem
Then roster transfer into NHL 26 is not optional. It’s mandatory.
Final Thought
If I spend 300+ hours building a full NCAA league, or a 2006 NHL recreation, or a complete minor hockey circuit…
Why would I do it knowing it dies in 12 months?
The whole point is for others to build on it.
To refine it.
To update it year over year.
Madden already proves this is possible.
It’s time for NHL 26 and NHL 27 to catch up. Roster sharing without transfer is temporary. This is so big it should be mentioned in promotional material for 27. Roster sharing with transfer builds legacy, and legacy is what keeps communities alive.
