Migration & Imports

Switch systems without rebuilding the club by hand.

GolfDock is designed to detect source files, map fields, preserve external identities, review duplicates, and produce a reconciliation report before data is committed.

CSV/XLSX/Golf Genius preset/Duplicate review/External IDs/Export anytime

Review a sample export →Reports & scorecards

Import safety

Review first

Source and field detectionPreview

Existing golfer matchingWeighted

Name-only mergeBlocked

Commit and reconciliationServer-authorized

Import flow

Every row should be understandable before it changes live data.

Upload

Choose the source system and upload a roster, event, pairings, results, or standings file.

Map and validate

Match uploaded columns to GolfDock fields and preserve safe unmatched fields as scoped custom data.

Resolve identities

Match exact external IDs, profile IDs, emails, phones, or handicap IDs before manual review.

Preview and reconcile

See new, updated, matched, skipped, warning, and error counts before the authorized commit.

Migration scope

Move the operational relationships—not just a list of names.

Master golfer directory

Unclaimed golfers, claimed accounts, guests, member numbers, handicap IDs, and preferred tees.

League and season structure

Facility affiliations, league membership, season eligibility, teams, flights, and divisions.

Event operations

Registrations, waitlists, pairings, starting assignments, scorekeepers, and event snapshots.

History and trust

Results, standings, external IDs, import history, warnings, errors, and exportable reconciliation.

Matching rules

A shared name is not enough to merge two golfers.

Exact identity first

External source ID, GolfDock profile ID, email, normalized phone, or handicap-service ID.

Secondary confirmation

Name plus a second identifier can create a review candidate—not an automatic merge.

Manual resolution

Ambiguous and conflicting rows stay visible until an authorized staff member resolves them.

Low-risk switching

Export from the current system, preview the outcome, and prove the migration before launch.

A course should never have to trust a black-box import or lose the external IDs needed for the next update.

Start with a sample file Integration roadmap