No silent skips
Missing, corrected, or unusable records are documented for staff review.
Assisted migration
Change systems without gambling the operating week.
Lobby reviews the source export with your team, configures the workspace, and keeps the public switch behind staff sign-off. This is an assisted service, not a self-serve importer.
See the product loopImport preview
Your club · illustrative dry run
Example only12s
| Source field | Target field | Rows | Status |
|---|---|---|---|
| Playtomic.members | lobby.users | 1 842 | ok |
| Playtomic.bookings | lobby.bookings | 18 204 / 24 mo | ok |
| Playtomic.player_notes | lobby.clients | 412 | ok |
| Playtomic.coupons | lobby.coupons | 38 | ok |
| Stripe.customer_ids | preserved | 1 842 | ok |
| Stripe.past_payouts | reference-only | — | read-only |
Example source rows mapped for staff reviewIllustrative demo data
The migration path
Review, configure, verify, then decide.
The source system remains the reference until the club accepts the configured result.
01
Review the source
Lobby support reviews the files your current system can actually provide. The scope is agreed before setup starts.
02
Configure the workspace
Courts, programs, members, and future bookings are mapped with visible notes for anything skipped or corrected.
03
Check a real week
Staff compare the upcoming schedule, sample members, rosters, and payment references with the source system.
04
Switch with sign-off
Public links move only after the operator accepts the result and the written rollback plan.
Scope depends on the export
Bring what the old system can prove.
These records are usually reviewed, but none are promised before Lobby inspects the source files. Historical payment data remains reference-only unless usable processor identifiers are present.
- Members and contact details
- Courts, spaces, and program types
- Future and recurring bookings
- Classes, capacity, and rosters
- Player notes and booking history
- Payment references exposed by the source
Deliberate safeguards
The honest version of migration.
A clean rollout depends on the source data and the people who know the club day. The process makes those dependencies visible.
Parallel run · cutover
illustrativeWrites accepted
After sign-off
Previous tool
Lookup only
Cutover timing
Club agreed
No automatic launch
A source review and configured workspace do not publish anything to members.
No invented timeline
Timing is agreed after the export is inspected, because source quality varies.
Questions
Know the boundary before the switch.
Is this a self-serve importer?
No. Migration is currently an assisted process. Lobby support reviews the source export, agrees the scope, and helps configure the workspace.
Can every source system provide the same data?
No. The migration can only use data the current system exposes in a usable export. Any gaps are documented before a launch decision.
How long does migration take?
There is no universal timeline. Lobby confirms timing after reviewing the export, the upcoming schedule, and the operating rules that need to be reproduced.
What happens if the schedule does not match?
The public switch does not happen. Staff keep the current system in place while the mismatch is corrected or the rollout is stopped.
Ready when you are
Bring the export and the difficult week.
Use a focused demo to review the source system, the schedule that cannot break, and the migration scope Lobby can support.
See pricing