Connecting intervals.icu to N+One: What Syncs and What Stays Local
5 min read
Learn what may sync between intervals.icu and N+One, what likely stays local, and the safest way to test a structured workout import.
On this page
Photo by Greg Doane on Unsplash.
Don’t assume fields transfer. Export one sample workout, import it into N+One, then check what appears.
There is no PubMed-indexed source that documents exact sync behavior between intervals.icu and N+One. Treat each field as unconfirmed until you test it with a sample export and import.
Photo by Mattia Cioni on Unsplash.
The safe model is simple: intervals.icu may act as the planning source, while N+One handles import, guidance, and ride context. Since public evidence does not list exact shared fields, verify a test file before you trust the workflow.
Start with one typical workout that has a name, steps, targets, and a planned date. Then compare what appears in N+One against the original, much like you would check Apple Health workout connections after linking a phone source.
Live sensor streams are different from file sync. If you need device-side setup, use the same care you would use when pairing a power meter with N+One.
Export one sample workout first.
Import it into N+One.
Compare name, steps, targets, and date.
Do not assume notes or custom fields moved.
In N+One terms: think of intervals.
In N+One terms: think of intervals.icu as a possible session author and N+One as the execution and tracking layer.
The most likely data to move is the data inside a structured workout file. That may include the workout name, step order, interval targets, and other fields stored by the chosen format.
Supported formats depend on what each app offers at the time you export and import. If FIT or TCX is available, start there before trying broader files such as GPX or JSON.
A planned calendar item may not equal a full structured session. After import, open the workout in N+One and check the session view before you ride, just as you would after setting up Garmin auto-sync.
Use FIT or TCX first when offered.
Check the workout name after import.
Open the steps and review targets.
Confirm the planned date before saving.
No authoritative PubMed evidence exists describing exactly what fields sync between intervals.icu and N+One — treat specifics as unknown …
Live ride telemetry is usually a stream from sensors to the app or head unit. It is not the same thing as a saved workout file that can be moved later.
Power meter zero offset, trainer setup, sensor pairing, and device settings may stay with the device or its companion app. For trainer-side checks, follow the same local setup mindset used in smart trainer setup in N+One.
Private notes, tags, and custom fields should also be treated as local unless you can see them in the exported file. If a field matters to your training review, check it by hand after import.
Treat live sensor data as local.
Check device calibration outside file sync.
Do not rely on private notes moving.
Inspect custom fields before deleting originals.
One tactical email with training ideas and product updates. No spam — unsubscribe anytime.
Keep reading
- Garmin Activity Privacy and N+One: Public, Followers‑Only, and Private Sync Behavior — No supplied PubMed source confirms Garmin privacy sync behavior. Use this N+One protocol to test Public, Followers‑Only, and Private before relying o...
- How N+One Builds Your Weekly Cycling Plan: From Goals to Daily Workouts — See how N+One turns your cycling goal, recent training, and recovery signals into one weekly focus, daily workouts, and adaptive plan changes.
- Recovery Weeks in N+One: How the App Decides You Need One — Learn how N+One decides you need a recovery week, which signals it weighs, and the clear seven-day next move when the app lowers your load.
Your next move is to test one representative workout, not your whole history. Pick a session with enough structure to show whether the import keeps the parts you need.
Export the workout from intervals.icu in a format N+One can read. Then import it, open the session, and check targets against your current settings before you save it to the calendar.
If you already use device files from other platforms, the logic is the same as checking Strava activity imports and power data. The file arrives first; the coach value comes from what N+One can read and use.
Export one structured workout.
Import the file into N+One.
Review target steps before saving.
Save it to the calendar only after checking.
If you want day-to-day guidance without second-guessing, let N+One translate your latest training context into one clear next decision.
If the session does not appear, re-export it in another supported format and try again. Keep the first test small so you can spot what changed without sorting through many files.
If targets look wrong, check whether both tools use the same current athlete settings. The issue may be a zone mismatch, not a broken workout file.
If the file imports but feels incomplete, compare the exported file, the original workout, and the N+One session side by side. When numbers still look off, use the same check order as forcing a resync for power numbers.
Retry with FIT before other formats.
Check current FTP or HR settings.
Confirm account permissions in both apps.
Contact support with the sample file attached.
In N+One terms: fix the data path before you judge the training advice.
Step 1 — Export: From intervals.icu, export the workout using FIT if available; otherwise use TCX. Save the file to a known folder on your device.
Step 2 — Import: Open N+One, go to Add Session or Import, and select the exported file. Confirm the session name and that target power or heart-rate intervals are present.
Step 3 — Verify zones: Check that N+One uses your current FTP or heart-rate settings. If not, update them so the targets match the intended session.
Step 4 — Save and schedule: Save the imported session to your training calendar, then sync to your device or head unit ahead of the ride.
Step 5 — Quick pre-ride check: Before starting, confirm device pairing and check that live targets display correctly on the head unit or trainer app.
Don’t assume fields transfer between intervals.icu and N+One. Export one sample workout, import it, verify the name, steps, targets, and date, then use that result as your source of truth.
No. The grounded source set does not document exact field-level sync behavior, so treat every field as unknown until you verify a sample import.
Use FIT first if both tools offer it, then try TCX if needed. If neither works, check the current export and import options in both apps.
No. Live readings usually come from your sensors, trainer, head unit, or device connection. A workout file is a plan, not a live sensor stream.
Send the exported workout file, a screenshot of the source workout, and a screenshot of what appeared in N+One. That gives support the data path to inspect.