Data and migration
How to Migrate From TeamSnap or LeagueApps
Inventory, export, map, preview, validate, and launch a LeagueArc migration from TeamSnap or LeagueApps without unsupported promises.
The short answer
Export the data your current platform makes available, inventory every object before cancellation, map it to a destination league and season, and preview supported files in LeagueArc before committing. Historical payments, message history, custom websites, and third-party integrations often need separate treatment; confirm export availability with TeamSnap or LeagueApps directly.
Before you start
- Administrator access to the source platform and LeagueArc.
- A dated inventory of leagues, seasons, teams, people, schedules, payments, stats, pages, domains, and integrations.
- Backups of every source export.
- A defined launch date and owner for validation.
Step-by-step instructions
Inventory before exporting
List the source records and workflows the organization actually uses. Mark each item as migrate, archive, rebuild, or retire; do not assume a single export contains everything.
Request official exports
Use the current TeamSnap or LeagueApps export and support options available to your account. Save original files unchanged and record the export date and source.
Build the LeagueArc structure
Create the destination organization, leagues, seasons, divisions, and administrator access first. This gives every import an explicit tenant-scoped destination.
Map and clean files
Copy supported columns into the current LeagueArc templates. Normalize dates, names, identifiers, and status values without deleting the original source files.
Preview in batches
Import teams and other supported data in small, reversible batches. Resolve every row-level validation error and compare counts before committing.
Rebuild non-portable workflows
Plan separate work for processor accounts, payment history, message archives, website pages, domain DNS, waivers, integrations, and training. Do not claim these move automatically.
Run parallel validation
Have league owners check rosters, schedules, balances, standings, public pages, and permissions. Keep the source available until sign-off and the first live workflow succeeds.
Cut over deliberately
Freeze source changes, take a final export where available, complete the last delta, change public links or DNS, and keep a rollback record. Cancel the source only after contractual and data-retention obligations are understood.
What success looks like
Common errors and fixes
The source export omits a data type
Ask the competitor's official support team what is exportable, preserve a human-readable archive, and decide whether the workflow must be rebuilt.
Import columns do not match
Map data into the current LeagueArc template and preview again; do not alter importer assumptions or silently drop columns.
Users see the wrong season
Verify each import's destination organization, league, and season and repeat validation before public cutover.
Where this lives in LeagueArc
- Product area
- Data Import plus league, season, website, payment, and integration setup
- Access
- Organization owners and league administrators
- Records affected
- Only supported, validated records are committed; source archives remain external
- Data boundary
- Every destination is explicitly restricted to the active organization, league, and season