Bringing content in from other apps
Last updated: August 13, 2026
Start by checking whether we connect to it
If your content already lives in Google Drive, Notion, or Dropbox, connect that app and pick the file directly — no downloading required. See all connections and integrations for what's supported.
For everything else, the pattern is: export from the other tool, upload here. The rest of this article is about doing that well.
Pick the right export format
This is where most of the quality is won or lost. The same content exported two ways can be either immediately useful or nearly opaque.
| If it's… | Export as | Why |
|---|---|---|
| A spreadsheet, log, or table | CSV | Structured data COORDINATOR can analyse row by row, not just read |
| A document or plan | PDF, Word, or Markdown | Text stays text |
| Notes | Markdown or plain text | Clean, no formatting cruft |
| A presentation | PowerPoint or PDF | Both read fine |
| Data from a specialist tool | CSV or JSON if offered | Far better than a formatted report |
The general rule: prefer data over pictures of data. A CSV of your training log is enormously more useful than a PDF report showing the same numbers in a chart, because COORDINATOR can compute with the first and only describe the second.
Avoid these
Screenshots of text. An image of a spreadsheet can be looked at but not calculated with. Export the underlying file instead.
Scanned PDFs with no text layer. These are images in a PDF wrapper — the words aren't extractable. If you must use one, run OCR first.
Proprietary formats. If a file only opens in one specific application, export a common format alongside it.
Common sources
Training platforms and coaching software
Most export a plan as PDF and a log as CSV. Take both if offered — the PDF for structure and intent, the CSV for the numbers.
If you're moving an entire program across, export it in whatever the tool's most structured format is and upload that. You can then ask COORDINATOR to turn it into a workspace document you keep editing here.
Note-taking apps
Obsidian, Apple Notes, Evernote, OneNote, and the rest all export to Markdown, PDF, or plain text. Markdown keeps headings and lists intact and is the cleanest option where it's available.
For a large set of notes, export the handful that actually matter rather than the whole vault. A focused upload gets a better answer than a bulk dump.
Spreadsheets
Export as CSV rather than the native format when you want analysis, and one sheet at a time — CSV holds a single sheet, so a multi-tab workbook needs either several exports or an .xlsx upload.
Once uploaded, a spreadsheet can become a workspace document you keep working on inside COORDINATOR.
Wearables and fitness apps we don't support
Check first whether we support it directly — Strava, Oura, WHOOP, Withings, Suunto, Hevy, and Amy all connect properly, which is always better than a manual export because it stays current.
For anything else, most fitness services offer a data export, usually CSV. That gives you a point-in-time snapshot — useful for history, but it won't update itself. You'll need to export again for newer data.
If you use Garmin, note that Garmin watches commonly push to Strava; connecting Strava is usually the easiest route to getting that data in continuously.
Video and game film
See Adding Hudl video to COORDINATOR, which covers Hudl and other team video platforms.
Email and calendar
Export or forward the specific content you need as a document. Don't paste enormous threads into a chat — save the relevant part as a PDF or text file and upload that.
After uploading
Uploading a file makes it available; it doesn't automatically reorganise it. What usually comes next:
- Ask COORDINATOR to summarise or restructure it — turn an exported plan into something you can work from here.
- Turn data into a workspace document — a CSV can become a sheet you keep updating.
- Keep the original in your library so you can come back to it.
A note on exports going stale
A manual export is a snapshot. It captures that moment and nothing after it. That's fine for a document, and a real limitation for anything ongoing — a training log exported today says nothing about tomorrow.
Where a proper connection exists, use it. Where it doesn't, plan on re-exporting periodically, and be aware that COORDINATOR is reasoning from the version you gave it.
Common issues
The export has strange formatting or symbols
Formatting rarely survives a conversion perfectly. For text, Markdown or plain text is cleanest. For data, CSV avoids the problem — there's no formatting to lose.
My CSV columns are jumbled
Some tools export with extra header rows or metadata above the real table. Open it, delete anything above the header row, and re-save.
The file is too large
See Uploading files to COORDINATOR for limits and what to do about them.
COORDINATOR misread my data
Check the file itself first — column headers that are blank, duplicated, or ambiguous cause most misreadings. Clear headers fix most of it. If the file is clearly right and the reading is clearly wrong, that's a bug on our side; please report it.
Contact support
Email [email protected] from the address on your COORDINATOR account. Tell us which tool you're coming from and what you're trying to bring across — if there's a better export route, we'll point you at it.
For privacy questions, data export, or deletion requests, see Privacy Policy.