AegisSwift ← All guides
Home/Guides/Golf Genius
Migration guide

How to export your roster from Golf Genius

Set the expectation before you start looking: Golf Genius is not an inventory system. It handles tournaments, leagues, rosters and handicaps. There is no item master to migrate. What it gives you is the people — a clean, current roster that becomes customer records.

Golf Genius is usually the second system, not the first. Clubs typically run it alongside a club-management platform — Jonas Club, ForeTees, Clubessential. Take your items and your authoritative member list from that system, and use Golf Genius only to fill gaps. Doing it the other way round produces duplicate members and no inventory.

1.Three routes

Route A — Season-level roster extract (recommended)

  1. Open the Customer Center.
  2. Go to the Report Center and run the Roster Extract Spreadsheet, selecting the season you want.
  3. This returns player and round data across the whole season — the widest net available without the API.

Route B — Per-event export

At event or league level, Control Panel → Export Players produces a spreadsheet of that roster. Fine for a single event; tedious if you want everyone, which is what Route A is for.

Route C — API v2

Golf Genius has a v2 REST API, but keys are not self-serve — the club must contact Golf Genius support and go through an application process. The key is then passed as a Bearer token. Only worth pursuing for an ongoing sync; for a migration the spreadsheet routes land faster.

One API quirk worth knowing before you write any code: Golf Genius IDs must be treated as strings, or as 22-digit numerics. Parsing them into a normal 64-bit integer will silently corrupt them — no error, just wrong IDs.

2.Field mapping into AegisSwift

Golf Genius field AegisSwift column Notes
party_type Set to customer for every row.
First Name + Last Name name Required. Match key for duplicates.
Email email Your best deduplication key.
Phone phone
Member ID / handicap index / custom fields notes Preserve the member ID — the club will keep using it.

3.Gotchas

Players repeat, a lot

Rosters are per-season and per-event, so the same player appears many times. Deduplicate on email — falling back to name — before importing, or you'll create the same customer a dozen times over.

Custom fields arrive as strings, keyed by display name

Ask the club which ones actually matter before mapping any of them.

Guests are in there too

A season roster includes non-members who played in an event. Decide explicitly whether they should become customers — for a pro shop the answer is often yes, which is a point in favour of importing them.

4.What happens on our side

This is a parties-only import: one spreadsheet, party_type = customer, matched on name. Because it carries no items, plan it as the second import after your item master lands from wherever that actually lives.

5.Questions people ask

Can I get my inventory out of Golf Genius?

There isn't any in there. It's a tournament platform, not a retail system.

How do I get everyone rather than one event?

The season-level Roster Extract Spreadsheet in the Report Center.

Do I need the API?

Not for a migration. Keys need an application to Golf Genius; the spreadsheet is faster.

Written from Golf Genius documentation and our onboarding experience. If a menu path here doesn't match what you see, tell us at hello@aegisswift.com and we'll correct it.

Run the pro shop on AegisSwift

Real-time inventory, barcode scanning, purchase orders, and QuickBooks sync from $69/month — with your member list already loaded. 14-day free trial, no credit card.

Start a free trial