← Back to 2Timer

2Timer Help

Practical guides for humans, with structure that is easy for AI systems to parse.

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 clear and replace selected categories in a meet
  • you want to import roster data into an existing meet without clearing it

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 and then From 2T Backup.

This workflow is designed for building or restoring from an existing 2Timer archive rather than typing the meet structure by hand.

Moving an Old-Origin Meet

To move a meet from the previous 2timer.app/app origin to manager.2timer.app, use the same .2t workflow:

  1. Open the old app at https://2timer.app/app.
  2. Export the meet as a .2t backup.
  3. Open manager.2timer.app.
  4. Choose Import and then From 2T Backup.
  5. Open the imported meet and confirm the setup and data you care about.

Do not delete old-origin local data until the imported meet has been checked on the manager origin.

What the Workflow Does

The .2t workflow first asks which operation you mean:

  • reads the backup file
  • shows a preview of what is inside
  • Restore clears and replaces the categories you choose
  • Import adds or updates athletes, teams, and entries without clearing existing data; stored ids and result fields in the backup are ignored
  • shows a Review step before applying either operation
  • finishes on a Done step with the restored meet or useful follow-up actions

These operations are deliberately separate. Restore never merges a selected category, while Import never clears one.

Restore Choices

When creating a new meet, choose Everything, Setup only, Setup and roster, or Custom. Setup-only choices leave result values, places, statuses, heat data, and round result state behind.

Inside an existing meet, choose Replace this meet with the backup, replace timing evidence and chip assignments, or choose a custom set of categories. Categories that link records by internal id are available only when the backup belongs to the same meet. Replacing the whole meet remains available for a backup from another meet.

Before a replacement, Review shows how much current meet data the selected categories will clear. 2Timer asks you to acknowledge that the replacement cannot be undone, and the Replace button stays unavailable until you do. Make a fresh backup first when the current meet contains work you may need again.

When importing from the home screen, Review uses Create meet from backup if the chosen name is new. If that sport and name already identify a meet, Review names the replacement, shows its current data counts, and requires the same acknowledgment before Replace existing meet is available.

After restore, 2Timer refreshes Data Issues. Identity problems in the stored backup do not block recovery; they appear there for review after the data has loaded. A damaged file with duplicate stored ids or unknown tables is still refused because it cannot be loaded safely.

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.

Related Pages

Metadata

  • Last Updated: 2026-08-28
  • Document Version: 0.4
  • Status: Active