ZenotiHelp

Sync club members with CSI Software

ZTZenoti Docs Team Updated September 5, 2026 3 min readGuide

Member synchronization between CSI Software and Zenoti runs automatically for every center whose CSI integration is active. This workflow explains what each run does, how to check its outcome, and how to handle failures. It assumes the CSI integration has already been configured — see Club integrations (CSI) for the one-time setup.


On this page


Before you begin

Permission: You need organization administrator access to configure and run the CSI integration.

  • Your organization must have an active CSI Software account with API access.
  • Enable CSI must be on, with the connection details saved, on the center's CSI accordion (Configuration > Integrations > Integration Settings at center scope). See Club integrations (CSI).
  • Confirm with club IT that the CSI API and data-sync services are reachable before the first scheduled run.

How a member sync runs

There is no manual sync control on the CSI accordion; Zenoti's scheduler runs the sync for each center whose CSI integration is active. Each run does the following, in both directions (see Sync direction):

  1. Zenoti retrieves member data from CSI and creates or updates the matching guest profiles. For a main member it also creates the membership invoice; for a dependent member it links the record to the main member.
  2. Zenoti identifies the guest profiles modified in Zenoti since the last run and pushes those changes to CSI.
  3. Zenoti records the sync result for each guest.

The first run after you enable CSI imports the club's existing members; plan for it to happen outside business hours.


Review sync results

Zenoti records, per guest, whether the last sync succeeded or failed. To review a run:

  1. Check that members present in CSI now appear as guests in Zenoti (see Verify synced members).
  2. For a guest whose sync failed, correct the underlying data in the system of record (usually CSI); the next scheduled run retries the record.
  3. Escalate persistent failures to Zenoti Support with the CSI member reference and the center name.

Verify synced members

  1. Open the guest list in Zenoti.
  2. Search for a known CSI member by CSI Member ID or by email.
  3. Confirm the profile shows the expected CSI-sourced fields.
  4. If bidirectional, update a test profile in Zenoti and confirm the change propagates back to CSI.

Handle member sync failures

Failure mode User-visible symptom Resolution
CSI unreachable during a run No members are created or updated for the run; the per-guest result records the failure. Confirm the CSI API and data-sync services are up (Api Service URL, Data Sync Service URL on the accordion); the next scheduled run retries.
Authentication rejected The run fails for every record of the center. Regenerate the CSI service credential and update Consumer Name / Consumer Password on the center's CSI accordion.
Invalid member data Individual records fail. Correct the member's data in CSI; the next run retries the record.
Duplicate member A member is created twice in Zenoti. Merge the duplicate guest in Zenoti and correct the duplicated record in CSI so later runs match one guest.
Member inactive in CSI Updates for the member are not applied. If the member should be active, reactivate them in CSI; otherwise mark the guest inactive in Zenoti.
CSI rate limiting Part of a run fails. Ask club IT to raise the limit for the Zenoti service account or accept that the next scheduled run completes the remainder.

Conflicts — the same member updated in both CSI and Zenoti between two runs — resolve in favour of whichever change the run applies last. Keep membership data changes in CSI and center-side changes in Zenoti to avoid them.


Reconciliation

Source Report / view Match key Cadence
Zenoti Guest export filtered to CSI-sourced guests CSI Member ID After every full sync
CSI Active member export from the CSI admin portal CSI Member ID After every full sync

Investigate any member present on one side but missing on the other. Common root causes: a failed upsert during the last sync, a record manually deleted from one system, or an incorrect field-authority configuration.


Tips

  • Enable CSI outside business hours so the first scheduled run, which imports all existing CSI members, does not compete with front-desk traffic.
  • Keep the CSI service credential current; an expired credential fails every run for the center until it is updated.
  • If a member exists in both CSI and Zenoti with different details, confirm the sync direction before the first run to avoid overwriting the correct system's data.

Was this article helpful?
Your feedback helps us improve our documentation.