Compatibility

Simulator export guide

Turn a Generic session into one Divot Card.

Use a shot-level Generic CSV/XLSX export so DivotData can detect the pattern, show the evidence, assign one practice block, and tell you how to retest the same setup.

Get your first free cardSee a sample Divot Card

Current beta status

Generic CSV/XLSX

Supported

Best upload

CSV, TSV, XLSX, JSON, TXT

File types

.CSV, .TSV, .XLSX, .JSON, .TXT

Confidence boost

Club, carry, offline, launch, spin

Mechanical proof

Needs impact data or coach review

DivotData reads shot rows, not summary screenshots. Missing optional metrics lower confidence instead of breaking the flow.

What to upload

Shot-level data works better than summary reports.

Use any shot-level table with club and at least one measured result column.

Compatibility note: Clear headers and one row per shot produce the best results.

Who this is for

Home simulator golfers who want a practical answer to what changed today and what to practice next.

What improves confidence

Clear club labels, one row per shot, carry or total distance, offline/deviation, launch, spin, shot order, and a matched retest.

Export steps

Prepare the file before you upload.

Use the cleanest export path available. If the source only gives a table, copied rows can still be useful.

  1. 1Export or copy a shot-level table from your simulator.
  2. 2Keep one row per shot.
  3. 3Include club, carry, total, offline/deviation, launch, spin, speed, or smash when available.
  4. 4Save as CSV, TSV, XLSX, JSON, or copied table text.
  5. 5Return to DivotData and use the upload box at the top of the page.
  6. 6Drop the exported file on the upload box or click Choose files. If your source only shows a table, paste the copied rows into Paste Table Text.

Click-by-click walkthrough

Upload any clear shot-level table.

Generic CSV/XLSX is not a vendor system, so there are no official vendor screenshots. Use it when the source is unsupported or when you have a clean table from a coach, spreadsheet, or simulator report.

  1. 1No vendor screenshot

    Start from shot rows

    Export, copy, or build a table with one row per shot.

    Note: A summary report with only averages is not enough to detect pattern evidence or sample-size quality.

    No fixed screenshot

    This screen can vary by device, operating system, or account state. Follow the note and choose the option that produces a CSV or other shot-level table file.

  2. 2Header quality

    Keep clear headers

    Use plain column names such as club, carry, total, offline, launch angle, spin rate, ball speed, club speed, and smash.

    Note: Clear headers help DivotData map the file without guessing. Ambiguous headers can trigger manual beta review.

    No fixed screenshot

    This screen can vary by device, operating system, or account state. Follow the note and choose the option that produces a CSV or other shot-level table file.

  3. 3Choose shot rows

    Save or paste the table

    Save the file as CSV, TSV, XLSX, JSON, or TXT, or copy the rows for Paste Table Text.

    Note: If you paste text, keep the header row and do not remove blank optional columns unless they create parsing noise.

    No fixed screenshot

    This screen can vary by device, operating system, or account state. Follow the note and choose the option that produces a CSV or other shot-level table file.

  4. 4Next click: DivotData upload box

    Upload to DivotData

    Return to DivotData, keep the source set to Generic CSV/XLSX, then upload the file or paste the rows.

    Note: DivotData should show missing-metric and sample-size warnings rather than pretending the data proves exact swing mechanics.

    No fixed screenshot

    This screen can vary by device, operating system, or account state. Follow the note and choose the option that produces a CSV or other shot-level table file.

Expected metrics

Metrics DivotData looks for in Generic files.

ClubCarryTotal distanceOffline or deviationLaunch angleSpin rateBall speedClub speedSmash factor

Data quality tips

  • Use plain column names when possible.
  • Avoid summary-only reports; DivotData needs shot rows.

What this cannot prove alone

  • Generic imports rely on header names, so clear column labels matter.
  • Launch-monitor data can detect patterns, but exact swing mechanics still need richer context, strike data, or coach review.

Sample proof

The upload is only useful if it becomes a focused card.

A Divot Card should show pattern detected, evidence, confidence, likely focus, what not to chase, the practice block, and a matched retest protocol.

Upload Generic dataSend an export sample

Sample Divot Card

Low-right / low-fade pattern

Open

Today's focus

18-minute 8-Iron Reset

A short block that narrows start line first, then checks face control, then checks strike/low point.

18 min
Club8-iron
PatternLow-right fade
ConfidenceMedium · 64/100

Start with

Start-line gate

Start the ball through a narrow target window before judging curve.

VideoOpen

Why this card

Data quality

82/100

good beta file

Sample

20 shots

Matched stock 8-irons

Coach-style note

The ball-flight pattern is clear enough to practice, but the exact mechanical cause should stay a hypothesis until a coach or impact evidence validates it.

Get your first card free

Demo card. Launch-monitor data can identify patterns and confidence levels, but it does not prove exact swing mechanics by itself.