Plan your move from Clubworx

Clubworx currently has a discovery-led path because source access or export coverage must be confirmed. Booking Bible validates a sample export, the destination data model and the payment-account path before confirming scope, completeness or timing.

Migration discovery required·Timing: Confirmed after source review

Contact the migration team View pricing

How it works

Three phases, each with an explicit validation checkpoint.

Step 1

Export your data

Download your client list, memberships, and booking history from Clubworx using our step-by-step guide.

Step 2

Upload to Booking Bible

Upload the available files, review proposed field mappings, resolve validation warnings and approve each batch.

Step 3

Go live

Confirm timing after source review, then cut over only after reconciliation, payment-path review and any agreed parallel run are complete.

Step 1 · Export

What it looks like in Clubworx

Source export access and file shape vary by account. This checklist illustrates the records we ask you to locate before we validate a real sample.

Clubworx · Admin

Reports → Export

Download your data

Clients
Example field
Memberships
Example field
Visits
Example field
Staff
Example field
Pricing options
Example field
Promo codes
Example field

3 of 6 selected

Export selected

Illustrative checklist only. Export availability and file shape vary by source account.

What transfers, what doesn't

Honest breakdown — no surprises on cutover day.

Transfers to Booking Bible

Members, memberships, attendance, payments
Handled through an agreed manual mapping or retained as an archive outside the automated batch.
Saved payment methods
Account ownership, source-provider cooperation, token portability and destination-account locality must be validated before any saved-card move is approved.

What doesn't transfer

Clubworx-specific martial-arts rank tracking
Not part of the established importer; retain the source export and agree an archive or rebuild plan.

Step 2 · Import

What it looks like in BOOKING BIBLE

Upload the available Clubworx files to the import workspace. Booking Bible proposes mappings and flags duplicate, encoding and field-shape issues for human approval.

BOOKING BIBLE · Migration Wizard

Step 2 of 3

Upload CSV

2Review mapping

3Confirm import

Proposed column mapping

Approval required

Customer NameProfile · full_nameSuggested
Email AddressProfile · emailSuggested
PhoneProfile · phoneSuggested
Member StatusMembership · statusReview
Signed Up OnProfile · created_atSuggested
TagsProfile · tags[]Review

Review warnings before approving the batch.

Illustrative mapping preview. Actual fields and validation results depend on the source export.

Saved payment methods

Let's discuss your processor

We haven't verified Clubworx's payment processor. Contact us to discuss the specific card migration path for your setup.

Why teams evaluate Booking Bible

Platform capabilities to compare against your current contract and operating model.

Keep venue data portable through organization-scoped CSV and JSON export paths
Run scheduling, clients, passes, payments and enabled operating modules on one data model
Use audited imports, validation previews, reconciliation counts and parallel-run notes during cutover
Extend approved workflows through scoped REST APIs, webhooks and embeds when the active plan allows them

Step 3 · Go live

After migration

Approved records are reconciled before launch. The payment path is activated only after account ownership, locality and provider requirements have been validated.

Booking Bible · Cutover review

Illustrative

Reconciliation checkpoint

Approve each dataset and the payment path before scheduling production cutover.

Count match

Client profiles

Reconcile source and destination totals

Sample review

Memberships

Inspect dates, balances and status mappings

Exception check

Booking history

Resolve unmapped and duplicate records

Provider sign-off

Payment path

Verify account locality before activation

Recent activity

Source files stored for the agreed retention window
Validation exceptions assigned and resolved
Cutover and rollback owners confirmed

Illustrative launch checklist, not a customer migration result.

Ready to make the switch?

Clubworx needs a source review before we can confirm scope, completeness or timing.

Contact the migration team Talk to us

Frequently asked questions

How long does migration take?+

It depends on source exports, data quality, payment-method portability, validation and the cutover model. The estimate at the top is indicative until the migration team has reviewed your actual account.

Will my clients lose their booking history?+

Supported history can be mapped into client records, but completeness depends on the fields the source platform exports. We reconcile counts and samples before approving cutover.

Do I need to be technical?+

No developer is required for a standard supported file import. You still need someone who understands the source records to approve mappings, resolve validation warnings and sign off on reconciliation.

Can I run both systems in parallel?+

A parallel or read-only reference period can be part of the cutover plan when the source contract and workflow allow it. The correct duration depends on the operation.

What happens to my saved payment methods?+

It depends on the source processor, legal account owner, destination connected account and token-portability process. Booking Bible resolves card locality member by member and never assumes a card can be moved across accounts.

Is there a cost to migrate?+

Migration scope and any cost are confirmed after reviewing the source, data volume, payment-method path and support required. We do not ask you to rely on an unreviewed blanket promise.

← All platforms