Compatibility

Simulator export guide

Turn a Full Swing session into one Divot Card.

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

Current beta status

Full Swing KIT

Needs validation

Best upload

Shared session data, copied rows

File types

.CSV, .XLSX, .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 Full Swing app session sharing/export, then upload the downloaded session details or copied shot rows.

Compatibility note: Public export format appears version-dependent.

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. 1Open the Full Swing app and sign in to the KIT profile.
  2. 2Open Session History and select the Practice or Combine session.
  3. 3Open the session share/export control.
  4. 4Share or download the practice session details.
  5. 5If the export opens as an interactive webpage, download any available data file or copy the shot table rows.
  6. 6Return to DivotData and use the upload box at the top of the page.
  7. 7Drop 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

Use Full Swing KIT session history or sharing data.

Full Swing publishes official KIT app screenshots for historical data and session sharing, but I did not find official click-by-click CSV export screenshots. Treat the exact export control as app-version dependent.

  1. 1Official app screenshot

    Open historical data

    Open the Full Swing app, sign in to the KIT profile, then open the historical data or session history area.

    Note: Use a practice or combine session with enough shots for a real pattern. DivotData will warn when the sample is too small.

    Official Full Swing KIT app screenshot showing historical data.
  2. 2Official sharing screenshot

    Open session sharing

    Select the session and use the app's share/export control when available.

    Note: Full Swing's official app page shows session sharing, but does not publish a stable CSV export-menu screenshot.

    Official Full Swing KIT app screenshot showing session sharing on a tablet.
  3. 3Export UI varies

    Save data or copy rows

    Download any available data file. If sharing opens a webpage or summary table, copy the shot rows instead of uploading a screenshot.

    Note: If only summary values are available, use manual beta review and include the Full Swing source path in the note.

    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 Full Swing, then drop the file or paste copied rows.

    Note: Keep the 16 data points when possible; missing optional metrics lower confidence instead of creating a fake conclusion.

    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.

Official source: Full Swing KIT app. Labels and DivotData notes are written for the upload-to-card workflow.

Expected metrics

Metrics DivotData looks for in Full Swing files.

ClubCarryTotal distanceOffline or deviationLaunch angleSpin rateBall speedClub speedSmash factorLaunch directionCurveClub pathFace angleFace to pathAttack angle

Data quality tips

  • Keep the 16 data points visible in the session when sharing/exporting.
  • Name the session by club and date before exporting.

What this cannot prove alone

  • Full Swing documents session export/sharing in app release notes, but file format and controls can vary by app version and subscription.
  • 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.

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.

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.