A manager or commissioner moving an existing workflow into a new Gridiron room.
Brand-agnostic mappings for dynasty/redraft; no automatic account, roster, or history import.
HELP TOPIC // glossary
/concept-transition · corpus 0.1 · verified 43c1c50
Concept transition from another fantasy platform
Translate football questions into Gridiron's concepts without promising identical provider behavior.
Sources
Who can use this answer.
Read the current gate
Agree on cutover and verify every new runtime rule before inviting managers.
The label carries the consequence.
Mapping-reviewed, runtime-confirmed, not-applicable, unavailable, manual-exception.
Use the runtime clock
Old-provider timing is reference only; new deadlines come from runtime.
Keep the right audience
Do not paste passwords, private exports, or member addresses into public help/source.
Take the next safe step.
- →
Freeze/reference old rules.
- →
Map identity, seats, rosters, lineups, acquisition, trades, scoring, privacy.
- →
Configure new league.
- →
Verify each identity/seat.
- →
Record exceptions as notes.
Know what changes.
What happens
An alias such as owner or waiver budget does not imply identical permissions, deadlines, visibility, or scoring.
What can be undone
Mappings are reviewable; new actions use their own correction path.
What you should see
Mapping names canonical term, alias, difference, source, privacy, consequence, next action.
Keep context. Do not replay blindly.
Missing/conflicting old data becomes an explicit manual exception.
Return to concept map and /scoring or /admin; record a commissioner ruling.
One concrete read.
Example: Waiver budget maps to non-currency FAAB units whose use follows runtime rules.
Runtime source: New league config/state; old artifacts are reference input only.
Corpus receipt: introduced 0.1; last verified 43c1c50dfbd493b01368d2c74959eb23de098749.