Zwift Workouts and N+One: Bridging an FIT File Into Your Adaptive Plan
5 min read
Learn how to move a Zwift FIT file into N+One as either a completed ride or a planned structured workout without breaking your adaptive plan.
On this page
Photo by Rafael Peier on Unsplash.
Get your FIT file, preserve the interval data, then mark that session in N+One so your adaptive plan can account for it.
Zwift, head units, and training apps often leave you with an FIT file and a planning question. This guide gives you one clean path: identify what the file is, preserve the workout intent, and place it in N+One without turning one session into a scheduling mess.
A FIT file is a small data file used by many bike computers, watches, and training platforms. It may hold time, power, heart rate, cadence, position, elevation, and device fields.
The key first step is not conversion. It is knowing whether you have a completed ride log or a workout prescription.
A completed ride tells N+One what you already did, much like ride imports from Garmin Edge auto-sync or Strava activity import. A workout prescription tells the app what you plan to do later.
Open the FIT in a viewer before changing formats.
Label it as completed ride or workout prescription.
Look for interval markers, power targets, and timestamps.
Keep the original file untouched as a backup.
In N+One terms: the same file extension can mean past work or future work, so sort that first.
Photo by Domenico Adornato on Unsplash.
Use Path A when the Zwift session is already done. Upload the FIT as a completed ride, then let N+One update the plan around that work.
Use Path B when you want to repeat the workout later. Convert the FIT, or rebuild the intervals, so N+One can schedule it as planned work.
This split keeps your training record clean. It also helps avoid doubling a ride as both completed work and a future workout.
Completed the ride already: upload it as done.
Want to repeat it later: rebuild or convert intervals.
Unsure which path fits: log the ride first.
Do not count one session twice.
Preserve the work you did, then let the plan move from that fact.
In N+One terms: completed rides are inputs; workout files are planned stimuli.
Export the FIT file from your device or platform first; that file is the source of the interval data you want to preserve.
A converter is only useful if you can inspect the result before the file enters your plan. Prefer tools that show interval length, target power, and step order.
If Zwift does not accept the FIT as a workout, rebuild the session in the Zwift workout editor. Copy the interval times and targets rather than guessing from memory.
For device data, make sure your sensors are paired and named clearly. N+One setup guides for power meter pairing and smart trainer connections can help keep the data path clean.
Preview the workout before saving it.
Check interval order against the original session.
Confirm target fields are present or clearly rebuilt.
Avoid blind one-click imports when targets are hidden.
Before import, check whether the workout used the same FTP or threshold value you use in N+One. If not, scale the targets before you schedule it.
Also check whether the workout fits the current week. A clean file can still be the wrong dose if it clashes with recent load, travel, or missed work.
If the week has already shifted, let N+One re-plan instead of forcing the old layout. The same logic applies when N+One handles a missed workout.
Match the workout FTP to your N+One FTP.
Scale power targets if the values differ.
Keep the key intervals, not every extra minute.
Move the session if it crowds recovery.
The goal is not a perfect file; it is the right next training choice.
In N+One terms: preserve the session’s quality, then adjust the dose to the week you are in.
One tactical email with training ideas and product updates. No spam — unsubscribe anytime.
Keep reading
- Setting Up Your N+One Account: A Walkthrough for First-Time Cyclists — Create your N+One account, verify email, complete your rider profile, connect devices or apps, set goals, and log a short ride to confirm setup.
- How N+One Builds Your Weekly Cycling Plan: From Goals to Daily Workouts — A practical, source-cautious outline of how N+One can turn goals, availability, recent rides, and recovery notes into one clear weekly cycling plan.
- Personalised Cycling Training: Adaptive Periodization to Peak — Personalised cycling training using adaptive periodization and performance modelling to time your peak for an A‑race. Learn AI‑driven tapering, rate‑...
If you completed the Zwift session recently, upload the FIT to N+One as a completed ride. That is the right first move because the plan needs the work you already did.
If you want to repeat the workout later, convert it to a structured workout or rebuild it by hand. Then import it as a planned session scaled to your current N+One settings.
If you want day-to-day guidance without second-guessing, let N+One translate your latest training and recovery context into one clear next decision.
Done already: upload the FIT as completed.
Repeating later: convert or rebuild the workout.
Planning the week: let N+One place it.
If the week is crowded, trim volume before intensity.
This keeps the adaptive plan tied to what actually happened.
In N+One terms: log completed rides now; import scaled prescriptions only when they guide future work.
A workout file should not become a contract. It should be one planned stress inside a week that still has to fit work, sleep, riding history, and recovery notes.
N+One works best when the plan has current inputs. For a wider view of how sessions are placed, see how N+One builds your week.
If you are moving from another planning stack, keep the migration simple. Bring over key workouts, verify power data, and use the migration checklist for cyclists to avoid file clutter.
Treat the imported workout as a draft plan.
Let new ride data change the week.
Keep only sessions you may repeat.
Delete duplicate or stale files.
Step 1 — Identify file type: Open the FIT in a viewer. Decide whether it is a completed ride log or a workout prescription, then note timestamps, power plateaus, and interval markers.
Step 2 — Decide action: If completed, upload it as a ride. If it is a prescription, convert it or rebuild it as a structured workout.
Step 3 — Inspect targets: Check whether the FIT used an FTP or threshold value. If it differs from N+One, note the gap before you import.
Step 4 — Convert or upload: Completed rides go into N+One, or through a linked service that syncs. Prescriptions should be previewed after conversion.
Step 5 — Rescale targets: If FTP differs, adjust the workout targets to match your N+One setting. If unsure, choose the more conservative version.
Step 6 — Let N+One decide placement: Import the structured workout or confirm the uploaded ride, then let the adaptive plan place or account for it.
Step 7 — Reassess after the next few days: Watch how the week changes after the file lands. If fatigue is flagged, preserve the key intensity and trim non-key volume.
Get the FIT file, decide whether it records past work or describes future work, then place it in N+One the right way. Completed ride logs should update your training record; workout prescriptions should be converted or rebuilt, checked, scaled, and scheduled as planned sessions.
Not always. A FIT file may be a completed activity rather than a workout prescription, so Zwift may not read it as a reusable structured workout.
If the ride is already done, yes. Upload it as completed work first so N+One can account for it before you plan another session.
Scale the targets to match the FTP you use in N+One before scheduling it. If you are unsure, keep the key intervals and choose a conservative dose.
Only if the workout cannot be imported or rebuilt cleanly. Use a tool that lets you preview interval structure before you save or import the file.
ChatGPT for your training — connected to your wearables.