# Support for rowing data / migrating from rowsandall.com

**URL:** <https://forum.intervals.icu/t/support-for-rowing-data-migrating-from-rowsandall-com/117915>\
**Category:** Uncategorized\
**Created:** [21 December 2025 13:30 UTC](https://forum.intervals.icu/t/support-for-rowing-data-migrating-from-rowsandall-com/117915 "2025-12-21T13:30:15Z")\
**Posts on this page:** 1\
**Showing post:** 39

<div class="post-metadata">

**Author:** ![Jaap\_van\_Ekris](https://forum.intervals.icu/letter_avatar_proxy/v4/letter/j/49beb7/32.png) [@Jaap\_van\_Ekris](https://forum.intervals.icu/u/Jaap_van_Ekris)\
**Post date:** [14 March 2026 17:45 UTC](https://forum.intervals.icu/t/support-for-rowing-data-migrating-from-rowsandall-com/117915/39 "2026-03-14T17:45:53Z")

</div>

> [@Sander\_Roosendaal](#):
>
> Intervals.icu has excellent interval discovery functionality. And there is WorkoutState and LapIdx. It was my intention to keep the FIT export a function of the rowingdata python library ([GitHub - sanderroosendaal/rowingdata: Python tools to process rowing (the sport) data · GitHub](https://github.com/sanderroosendaal/rowingdata)). On Rowsandall I have some extra fields but intervals are basically calculated from Workoutstate.

Our experience is vastly different for indoor rowing. With ORM we report on a session, spilt (= ORM interval) and lap (= ORM split) level, and there is a bug on parsing that data, as intervals messes with that data. See [Question on FIT file parsing: Misaligned Splits / "Summary First" vs "Summary Last" handling](https://forum.intervals.icu/t/question-on-fit-file-parsing-misaligned-splits-summary-first-vs-summary-last-handling/123523)

I see the same happens with Garmin data: [First intervals too short? Rest of intervals shifted](https://forum.intervals.icu/t/first-intervals-too-short-rest-of-intervals-shifted/124558)

> [@Sander\_Roosendaal](#):
>
> FYI, if you want to track details of what I am doing, best to check this document in the develop branch of the rowingdata repo: [rowingdata/docs/FIT\_EXPORT.md at develop · sanderroosendaal/rowingdata · GitHub](https://github.com/sanderroosendaal/rowingdata/blob/develop/docs/FIT_EXPORT.md) I’ll try to keep the discussion here high level and digestable for non-coders.

Good idea!

If you want a (bad) example of how we report data: [openrowingmonitor/app/recorders/fitRecorder.js at 0.9.7-(under-construction) · JaapvanEkris/openrowingmonitor · GitHub](https://github.com/JaapvanEkris/openrowingmonitor/blob/0.9.7-(under-construction)/app/recorders/fitRecorder.js)

Unfortunately, this isn’t too non-developer friendly. We do try to document much of the parameters and timestamp stuff etc as well. AFAIK, this is the maximum of the documented native datafields that can be used.

We are working with an upstream developer to include undocumented Garmin fields as well. But that will be in the next release for us. This includes some summary fields which are interesting.

---

_[View the full topic](https://forum.intervals.icu/t/support-for-rowing-data-migrating-from-rowsandall-com/117915)._