Quantified Self   9.0.6
Navigation
Home
Membership
Login
Preferences

Guides

Training data sync guides

Choose the guide that matches the workflow you need: Garmin to Suunto, COROS to Suunto, or a centralized Garmin, Suunto, and COROS workout archive.

Garmin to SuuntoCOROS to SuuntoCentralized dataCatch-up syncProvider setup

Sync Setup

Use route-specific guides for cross-service sync

Each sync guide explains the provider connections, route toggles, and catch-up behavior before you start moving activities between services.

Garmin -> Suunto

Connect Garmin and Suunto, enable the Garmin -> Suunto route, and use manual catch-up for existing Garmin activities.

COROS -> Suunto

Connect COROS and Suunto, enable the COROS -> Suunto route, and account for the provider-limited recent history window.

Explicit route control

Automatic sync routes are opt-in, and manual catch-up can queue selected date ranges without changing future route settings.

Centralized Archive

Plan the dashboard before you connect everything

The centralization guide explains how provider imports, manual uploads, source files, benchmark reports, exports, and AI Insights fit together.

Garmin, Suunto, and COROS together

Centralize Garmin, Suunto, and COROS workout data while preserving provider source context for each activity.

Files when services are not enough

Use FIT, TCX, GPX, JSON, and SML uploads for unsupported services, review units, lab tests, and custom exports.

Analysis after import

Once data is centralized, use comparison features, benchmark reports, exports, and chart-backed AI questions from the same archive.

FAQ

Guides FAQ

Which guide should I use first?

Use the Garmin -> Suunto or COROS -> Suunto guide when your goal is cross-service sync. Use the centralization guide when you are planning a private dashboard across providers and uploaded files.

Do automatic sync routes import old history?

No. Automatic routes handle newly imported activities. Existing workouts need provider history import and manual catch-up when you want them queued to another service.

Where do I find provider-specific setup details?

Use the integration pages for provider-specific capabilities, permissions, imports, uploads, and troubleshooting, then use these guides for the workflow sequence.

Next Step

Start with the workflow, then connect the services

Pick the guide that matches the job to be done so provider setup, route toggles, catch-up sync, and analysis stay predictable.