How to prepare a CSV export from another app for upload
Most rejected uploads fail for four or five predictable reasons. A checklist for getting a CSV from another app into Trackly first time.
28 September 2026 · 8 minute read · The Trackly team
Trackly does not connect to other fitness apps. If you have history somewhere else and want it here, the route is to export a file from that app, tidy it up, and upload it for review. This article is the tidying up part, which is where almost all the difficulty lives.
The good news is that rejected files fail for a short list of reasons, and all of them can be checked in a few minutes before you submit.
Start by getting a real export
Look for an export, download your data or backup option in the other app, and choose CSV or JSON if you are offered a choice. What you want is a file with one row per record. A printable report, a PDF summary or a screenshot cannot be imported, because the individual figures are not separable.
If the app only offers a full archive, unzip it and look for the file that matches what you want to bring across, usually named for workouts, activities, measurements or nutrition.
Open it and look at the first ten rows
Open the file in a spreadsheet program or a text editor before doing anything else. You are looking for five things.
- A single header row at the very top, with a name for every column.
- One record per row, with no blank rows in the middle and no summary row at the bottom.
- Dates in one consistent format.
- Numbers that are numbers, without units typed into the cell.
- No merged cells, no colour coding carrying meaning, and no notes rows above the header.
Files exported from a spreadsheet someone maintained by hand are the hardest cases, because they usually contain a title row, merged headings and a total at the bottom. All three need removing.
Dates are the most common failure
Use the ISO format, which is four digit year, then month, then day, separated by hyphens. The eighth of September 2026 is 2026-09-08. This format sorts correctly and cannot be misread.
The trap is a file where 09/08/2026 means the eighth of September and the reviewer has no way of knowing whether it means the ninth of August. Mixed formats in one column are worse, and they happen often when a file has been edited in different places over several years. If your file has ambiguous dates, convert the whole column before uploading.
- Pick one format and apply it to every row.
- Check the last row as well as the first, because the format sometimes changes partway down.
- Watch for dates that a spreadsheet has silently converted while you were looking at the file.
- If times are included, state the time zone in your submission note.
Units belong in the header, not the cell
A weight column should contain 82.5, not "82.5 kg". Put the unit in the column name, such as weight_kg or duration_minutes, and keep every value in that column in the same unit. A column that mixes kilograms and pounds, or minutes and hours, cannot be imported and will come back as needing changes.
Use a full stop for the decimal separator and do not use thousands separators. Decimal commas are the second most common reason a numeric column arrives as text.
Encoding, separators and the empty cell question
- Save as UTF-8 so that accented characters survive. A file saved in a legacy encoding usually arrives with damaged text.
- Use commas as the separator. If your spreadsheet produces semicolon separated files, change the setting or save again as a comma separated file.
- Leave a missing value genuinely empty. Do not write 0, N/A or a dash, because zero is a real figure and will be imported as one.
- Quote any text field that contains a comma, which most spreadsheets do for you.
- Keep the file under the size limit shown on the upload page, and split a very long history into two files by year if needed.
Use the preview
When you upload, Trackly reads the file and shows the first rows, the columns it recognised and anything it could not parse. Read that screen properly. It is faster than a review cycle, and a file that looks wrong in the preview will look wrong to a reviewer too.
The preview also lists rows that look like entries you already have. Duplicates are flagged rather than merged quietly, so you can decide whether to keep your existing entry or the imported one.
Write a useful submission note
One or two sentences saves a round trip. Say which app the file came from, what the rows are, the date range covered, the units used and anything unusual you already know about. "Export from my old training app, one row per set, March to August 2026, weights in kg, the June rows were retyped from paper" tells a reviewer everything they need.
If it comes back needing changes
Needs changes is not a rejection. The record stays open, the reviewer comment says what was wrong, and you can upload a corrected file against the same submission. Fix the file rather than editing a few rows by hand, because the same problem usually affects a whole column.
Review checks that a file is readable and internally consistent. It is not a verification that the figures are accurate, and it is not an assessment of your training. Keep your original export until the upload has been approved.
Record it while it is fresh
Trackly keeps the detail so a session from March can be compared with the same session in September.