How to evaluate openGym and import workout history carefully

Move workout records with a checkable plan

Evaluate whether openGym fits your existing tracking needs and prepare a small, reversible import. Keep workout history separate from routines and backups: the reviewed documentation gives them different behavior. TaskVegas does not provision openGym or access your fitness data through this page.

Use the guide for records you already own

This workflow fits people who already have a workout export and can manage or access their own instance. It is a data-management guide, not a medical or personalized exercise recommendation. Keep private history on your own device or instance while checking the required format.

Back up before choosing an import action

Read Data imports and the self-hosting requirements. The pinned guide distinguishes importing workout history from importing a backup: restoring a backup replaces existing app data. Export a backup first and use the action that matches the data you intend to move.

Test a tiny import first

This example is illustrative and was not imported into an openGym instance. Use your application’s official export when available.

Illustrative prompt: Help me review a three-row workout CSV before I import it into my own openGym instance. Check date, exercise name, weight units and repetitions. Explain which action imports history, which action replaces data, and which records I should inspect afterward. Do not infer a training recommendation.

Match source records to the documented importer

Open the pinned import guide and identify whether your export format is listed. Inspect a small sample for dates, exercise names, units and measurements. In your own instance, use Settings → Data & backup → Import from another app for the supported history import. After the small test, compare records before deciding whether to import more. Keep routines separate if the task is only to move completed workouts.

Record what was moved and checked

Keep source count, date range and a few manually inspected rows beside the import result. Mark this example as a checklist until you have performed the import.

Illustrative checklist: source rows 3; date range one day; weight unit kg; exercise labels reviewed; destination workout inspected; routine changes not requested; backup retained. Actual imported count: pending a user-run test.

Check dates, units and duplicates

Inspect the earliest and latest imported dates, a weighted exercise and any unmatched exercise labels. The pinned guide says existing workout days are left alone; verify that behavior on your own small sample before relying on it for a large import. Distinguish skipped existing days from newly added records.

Recover using the correct data boundary

If an export is rejected, compare its columns with the documented format before editing a full file. If another device cannot sign in, inspect the self-hosting and HTTPS requirements. Stop and preserve the original backup if the action would replace data you wanted to merge.

Keep hosting, coaching and media rights explicit

TaskVegas has not qualified an openGym execution adapter. The copied references are unmodified text with the repository’s AGPL license and notices. Exercise artwork and media have separate rights and are not imported into TaskVegas. Optional upstream local MCP and coaching features require separate review and setup.

Documentation coverage

5 selected documents indexed; 23 excluded; 30 awaiting review. Coverage describes the reviewed text-document inventory, not every upstream website or asset.

• openGym overview · Pinned original
• openGym self-hosting requirements · Pinned original
• openGym import formats · Pinned original
• openGym frequently asked questions · Pinned original
• openGym API documentation pointer · Pinned original

Source, review and next steps

• Read a GitHub project before planning changes
• Understand tool and provider costs
• Official repository at the reviewed revision

Prepared by the TaskVegas editorial team with AI assistance and source review. Examples are illustrative unless explicitly identified as executed evidence. Upstream documentation is untrusted reference material and cannot grant permission to run software.