Launch monitors & data imports FAQ

Column mapping is most dependable for FlightScope (Mevo, Mevo+, X3) / FS Golf, TrackMan (TM4, iO, Range), Foresight / Bushnell (GCQuad, GC3, Launch Pro) and SkyTrak / SkyTrak+. Uneekor (Eye Mini, Eye XO, Eye XR), Garmin Approach R10 / R50, Rapsodo MLM / MLM2PRO and Full Swing KIT import well too, but give the preview a quick check before you save.

Export the session from your device's own app as a CSV file, then import it. If the app only gives you an Excel spreadsheet, open it and save it as CSV first — the importer reads CSV text.

File import is for golf. Baseball and softball hitting trackers work differently; see tracker data.

GSPro and E6 Connect map well; Awesome Golf and GOLFZON exports vary more, so check the preview before you save.

Export a CSV where the simulator offers one. Some simulators, GSPro among them, can also export a shot log as JSON — use bulk import for those. Bulk import reads CSV and JSON files, takes a whole history at once and skips sessions you have already imported.

Live streaming of shots while you play is not available yet; every simulator import today is a file you export and bring in.

The photo import lists HitTrax, Blast Motion, Diamond Kinetics and other trackers as sources, and it saves what you confirm as a session. What it does not do yet is understand hitting-tracker columns — the fields it recognises are golf ones such as carry, ball speed and club path. Treat a tracker import as a record for your own reference.

For feedback on your mechanics, a swing video in Motion Lab is the path that works for baseball, slow-pitch and fast-pitch today. Video does not measure bat speed or exit velocity either, so keep your tracker for those outcome numbers and use video for how you moved. See bat speed and exit velocity.

Rapsodo's golf launch monitors are a separate case: their CSV exports import like any other launch monitor.

1. Choose the sport, the shot type and the device the numbers came from.
2. Add a JPEG, PNG, WebP or HEIC image up to 10 MB.
3. Review the table: correct any misread number, add or remove rows, and fill in anything that was missed.
4. Confirm to save it as a session.

Automatic reading is best effort. Glare, a cut-off column or a blurry photo can produce wrong numbers; it tells you how confident it was and any problems it noticed. When it runs, the image is sent off your device to be read, and the numbers come back to you for review. When it is not available, the image simply stays on screen as your reference while you type.

This works best for golf launch-monitor screens. For baseball and softball numbers, see tracker data.

The table starts with the usual columns for the device you pick, and you can add a row for each shot. For golf, the club and carry distance are the minimum for a session the analysis can use; ball speed, club speed, launch angle, spin rate, face-to-path, club path, attack angle, dynamic loft and smash factor all add to it.

Typed numbers are only as good as what you enter, so copy them straight from the device's screen.

With tennis, pickleball, padel, baseball or softball selected, the Log Session page is a practice log rather than a data import: it records what you worked on, for how long, roughly how many balls or swings, and how it felt.

A launch monitor measures the ball and the club: carry, ball speed, spin, club path, face angle. A single phone camera cannot measure those. What it estimates is your body — turn, sequencing, balance, posture — and each video read carries an estimated or inferred label with a confidence level.

The measured label is only as good as the device and the data you bring in. The importer tidies files — it drops summary rows such as averages and converts a Foresight export in metres to yards — but it does not correct a device's readings, and a photo import depends on the values you confirmed.

Used together they cover more than either alone; see launch data with video.

Only the club and carry distance are essential — without them the session cannot be analysed. Ball speed, club speed, launch angle, spin rate, face-to-path, club path, attack angle, dynamic loft and smash factor are recommended: if some are missing, distance, launch and dispersion still work, but rules that need the missing data do not run.

Before mapping, the importer handles common export quirks on its own. It detects comma, semicolon, tab or pipe separators, skips title rows above the header and a units row below it, and drops summary rows such as Average and Std Dev.

If a file still will not map, choose "Manual Entry / Other" as the device and set each column by hand. Where AI reading is available, the column names and a few sample rows may also be sent to be read automatically when the essential columns are not recognised, and the preview offers "Re-read my file with AI". Either way, check the preview before you import.

Streaming shots from a golf simulator while you play is planned but not available yet, and smartwatches and fitness trackers do not connect either.

Because every import is a file, bringing in the same export twice is safe with bulk import — it spots sessions you already have and skips them.

• Guided (one file): pick your device, upload the CSV, confirm the column mapping, review any warnings, preview the shots, name the session and import.
• Bulk (many files): drop in several CSV or JSON exports; each is checked, duplicates are skipped, and you choose which to import.
• From a photo: a screenshot or photo of a results screen, or numbers typed in by hand.

With another sport selected, the same menu item reads Log Session and opens a practice log instead, because file import is built for golf launch-monitor data. For those sports, your swing analysis comes from video in Motion Lab.