Importing a 2Timer Backup
Purpose
Explain when to use a .2t backup, what it is good for, and how the import workflow behaves when restoring or reusing an existing 2Timer meet.
When to Use This Workflow
Use the .2t backup workflow when:
- you exported a meet from 2Timer earlier
- you want to restore a full meet from backup
- you want to reuse an older meet as the starting point for a new one
- you want to selectively bring data into a newly created meet
This is different from CSV or semicolon-file import. A .2t file is a 2Timer-native backup, not a third-party source file.
Where to Start
From the home screen, choose Import 2T Backup.
This workflow is designed for building or restoring from an existing 2Timer archive rather than typing the meet structure by hand.
What the Workflow Does
The .2t import flow:
- reads the backup file
- shows a preview of what is inside
- lets you set up the destination meet first
- lets you choose which parts of the backup to bring over before anything is written
This makes it useful for both full restoration and selective reuse.
Good Uses
Restore a meet
Use the full backup to recover a meet after moving to another machine or after a browser reset.
Reuse last year’s meet
This is one of the best ways to start a recurring meet. You can carry forward structure and setup instead of rebuilding everything manually.
Use a meet as a template
If you have a “base meet” with standard divisions, events, teams, or reports, export it once and reuse it through .2t import.
Why Use .2t Instead of Starting Over?
Use a .2t backup when your old meet already contains setup you trust:
- events
- divisions
- venue information
- team structure
- scoring-related settings
- report/export configuration
That is usually faster and safer than recreating the same meet by hand.
Practical Recommendation
If the meet already exists in 2Timer, .2t is usually the best starting point.
If the meet exists outside 2Timer and your best source is a semicolon-format meet-data export, use that creation workflow instead of .2t.