
Need a copy of your N+One data? Use this cautious guide to request an export, ask for CSV, JSON, FIT, TCX, or GPX files, and verify the archive.
On this page

Photo by loka studio on Unsplash.
I don’t have N+One’s official export docs available, so use this cautious checklist to request a full data export now.
Owning a local copy of your training data can help you keep records, share files with a coach, or move to another tool. Because official N+One export instructions were not available in the supplied sources, this guide keeps claims narrow and gives you a practical support-request path.
Start with an account-level request, because it is the cleanest way to avoid missing linked records. Ask for profile details, account settings, training history, device sync records, plan history, and billing records if they apply.
For training files, ask for both raw activity files and summary tables when available. Raw files help preserve rides, while tables make it easier to scan dates, titles, distance, time, and key fields.
If you want to understand the broader data context, review privacy and your data before you send the request. If your account holds sensitive details, also check account sign-in safeguards first.
Ask for a full account-level export.
Include profile, settings, and training history.
Request raw activity files where available.
Ask for plan, sync, and billing records if relevant.
This keeps the export broad before support narrows what can be sent.
In N+One terms: ask for the raw rides, the summaries, and the account context around them.

Photo by Mathias Reding on Unsplash.
Ask for machine-readable files, because they are easier to keep, search, and move. CSV works well for spreadsheets, while JSON is better for structured records and app-to-app use.
For workouts, request FIT, TCX, or GPX files where those formats exist in your account. These files are often used by bike computers, training apps, and other activity tools.
If you synced rides from another service, confirm whether N+One can export those files or only its own records. For imported rides, verify synced power data before you rely on the archive.
Request CSV for spreadsheet checks.
Request JSON for structured records.
Request FIT, TCX, or GPX for rides.
Ask for a zipped archive if files are large.
In N+One terms: use raw files for rides, and use tables for checks.
I don’t have N+One’s published export procedure available; confirm details in your account or with support.

Photo by Haberdoedas II on Unsplash.
An export request does not always mean every record can be sent back in one file. Some records may include other people’s data, third-party rights, or internal system details.
Ask support to state what is excluded, not just what is included. That wording helps you know whether missing files are unavailable, out of scope, or still being processed.
If you need help wording the request, use N+One support guidance rather than guessing. Keep the message calm, exact, and tied to your account identifiers.
Ask what data is excluded.
Do not expect internal models or system logic.
Request third-party limits in writing.
Include the date range you need.
One tactical email with training ideas and product updates. No spam — unsubscribe anytime.
Keep reading
- Easy AI Cycling Coach — How N+One Makes Coaching Accessible — N+One is an easy AI cycling coach that turns complex training science into simple, personalized daily guidance. Learn how conversational AI, adaptive...
- How N+One’s AI Cycling Coach Works — A Deep Dive — Discover how N+One’s AI cycling coach delivers personalized training plans and adaptive coaching. Learn how real-time data (power, HRV, sleep), CTL/A...
- Personal Records in N+One: How the App Detects Breakthrough Efforts — What can and cannot be said about N+One personal-record detection from the provided source, plus a safe protocol for reviewing a breakthrough effort.
One clear next move: open account settings and look for Data & Privacy, Data Export, or a similar label. If you cannot find it, send a support request the same day.
Use a short message with your account email, the date range, and the formats you prefer. Ask support to confirm the expected delivery path and whether the download link will expire.
Copy-ready request: “Please provide a full export of my N+One account data, including profile, settings, activity history, raw workout files, device sync records, training plan records, physiological metrics stored in my account, and billing history where available. Please send CSV or JSON for tables, FIT, TCX, or GPX for workouts where available, and confirm any items you cannot export.”
Open account settings first.
Look for Data & Privacy or Data Export.
If missing, send the support template.
Ask support to confirm limits and timing.
Your best next step is to request the export before sorting the details.
Do not treat the archive as complete until you open it and check the range. Match the first and last workout dates against what you expected.
Spot-check a few ride files in the app or tool you plan to use next. If power, GPS, or time fields look wrong, note the exact file names before contacting support.
If your export includes plan records, compare them with how your week was built inside N+One. You can use weekly plan structure as a plain reference for what those records may describe.
Check the first and last activity dates.
Open several workout files.
Compare key totals with your account view.
Send missing file names to support.
In N+One terms: download first, verify second, then decide where the files go.
Day 0 — Request: Open account settings and look for Data & Privacy or Data Export. If you cannot find it, send the support template in this guide.
Day 1–3 — Monitor: Watch for a confirmation message or support reply. Check spam or junk folders if email delivery is used.
Day 3–7 — Verify: Download the archive, check the date range, open several workout files, and list any missing items before you reply to support.
I don’t have N+One’s official export docs available, so use a cautious path: request a full account export, ask for CSV or JSON plus raw workout files, and verify the archive before you move your data elsewhere.
No. The supplied sources did not include official N+One export documentation, so this guide gives a cautious request process and tells you what to confirm with support.
Send the support request template from this guide. Include your account email, requested date range, preferred formats, and a clear ask for any limits or exclusions.
Ask for CSV or JSON for account tables, and FIT, TCX, or GPX for workout files where available. That mix is practical for review, storage, and import into other tools.
It may depend on the source and permissions. Ask support whether third-party synced records are included, limited, or must be requested from the connected service directly.