Migrate from Pike13
Move from Pike13 to PeakSpitz, safely.
Moving off Pike13 should feel like restoring from a backup, not a leap of faith. Your class & membership tool data is read into a PeakSpitz environment of your own, checked against your real numbers, and run in parallel — while Pike13 keeps running, untouched, the whole time. Here is exactly how, step by step.
Pike13 is client scheduling and membership management for fitness, education and wellness businesses, and its combination of clean scheduling, memberships and passes, recurring billing, and staff payroll reports is what people value most — booking, plans and instructor pay tie together in one place. Teams usually migrate when they need a real business system underneath: double-entry accounting with VAT, a storefront and inventory typically sit outside Pike13, so scheduling and the books stay separate. PeakSpitz keeps the scheduling-plus-passes model and adds the accounting and retail core around it.
The safe way to leave Pike13
Work down the list at your own pace. Nothing here is irreversible, and your current system stays live throughout.
- 1
Before you touch anything — get a backup you own
Get a copy of your data out of Pike13 that you control — a file held on your side, not just a setting inside the system. Confirm in your contract that you have the right to export, and note any renewal, notice or lock-in dates so the timing stays on your terms.
- 2
Export your data
Pull members, classes, schedules, bookings and passes out of Pike13 in the most complete format it offers — CSV, spreadsheet, or an account/API export. Take the history too, not just open items: past records, documents and contacts are worth keeping.
- 3
Send us a sample
Before you commit, send us a representative slice — a handful of customers, a few recent orders or bookings, part of your catalogue. We map it into PeakSpitz and show you the restored result, so you see exactly how your class & membership tool data lands before you move the rest.
- 4
See what maps to what
We line Pike13 up against PeakSpitz: members, classes, schedules, bookings and passes become customers, catalogue, orders, documents and ledgers in one joined-up system. Anything without an obvious home is flagged early, not discovered late.
- 5
Bring it in — a read-only restore
Your data is read into a fresh, isolated PeakSpitz environment of your own. Nothing inside Pike13 is touched, changed or switched off — it keeps running exactly as it is.
- 6
Verify against your numbers
Before you trust it, reconcile the totals — balances, counts, tax and revenue — against what Pike13 shows today. The numbers have to match before anything goes live.
- 7
Run both in parallel
Keep Pike13 live and run PeakSpitz alongside it for as long as you like. Compare like for like, move one area across first, and build trust before you depend on it. No big-bang cutover, and no deadline from us.
- 8
Cross over and decommission — on your terms
Switch over only when PeakSpitz has earned it. Keep your Pike13 export archived as a safety net, and close the old subscription when you are ready — not a moment before.
What maps where: Pike13 → PeakSpitz
Pike13
Client
PeakSpitz
Customer record
Individual clients map directly; where a parent pays for a child, both become linked contacts.
Pike13
Service and its schedule
PeakSpitz
Bookable service on a schedule (appointment fulfilment)
Pike13
Enrollment / Visit
PeakSpitz
A booking tied to the customer, with attendance
Past visit history imports as closed records.
Pike13
Plan (recurring membership)
PeakSpitz
Subscription (recurring billing)
Pike13
Pass (punch pass / class pack)
PeakSpitz
Redeemable pass
Remaining punches are a cutover decision — see watch-outs.
Pike13
Staff / instructor records
PeakSpitz
Staff records in PeakSpitz
Payroll runs themselves don't migrate — see watch-outs.
What to watch when leaving Pike13
- ⚠
Recurring-billing card tokens do not transfer — every client on an auto-billed plan re-authorises their card on PeakSpitz. Because Pike13 bills plans on a cycle, switch just after a billing date to leave the longest runway before the next charge.
- ⚠
Pass balances (unused punches, class-pack credits) are a cutover decision, not an automatic import: decide whether to recreate remaining punches as PeakSpitz redeemable passes or let clients burn them down on Pike13 first, and reconcile the count so nobody loses a paid-for visit.
- ⚠
Pike13's payroll reports are a real strength, but payroll itself typically doesn't migrate — historical pay runs stay where they were computed. Staff records and roles come across; re-establish pay rules on your payroll process rather than expecting them to import.
- ⚠
Waivers clients signed in Pike13 usually need re-signing to remain enforceable under the new system; collect them at first login instead of assuming the prior acceptance carries over.
Common questions about leaving Pike13
Do client visit histories and attendance come with us?
Client records, memberships and attendance history import — past visits come across as closed records so the history is intact. What resets is anything the new system has to re-establish: card authorisations and, if you use them, signed waivers.
What happens to unused passes and punch cards?
They're a decision, not an automatic import. Typically you either recreate remaining punches as PeakSpitz redeemable passes or let clients use them up on Pike13 before cutover. Reconcile the counts first so nobody loses a paid-for session.
We rely on Pike13 payroll reports — does PeakSpitz replace those?
Pike13's per-visit payroll reporting is genuinely handy, credit where due. PeakSpitz brings staff records and real accounting with VAT, but payroll runs don't migrate and you'll keep computing pay on your payroll process. Where PeakSpitz adds is joining scheduling, memberships, retail and the books in one system.
As much help as you want
Do it yourself, or have us map your fields, run the import and reconcile the result with you. Support is a ladder — you start where you are comfortable and step up only where an area needs it.
See the full safe-migration approach →Why people leave Pike13
PeakSpitz runs the whole business on one AI platform — not a single corner with the rest bolted on — with Spitz AI and unlimited users included. See the difference side by side.
Compare PeakSpitz vs Pike13 →Bring your Pike13 data in safely. Cross over when you are ready.
Send us a sample of your data and we will show you the restored result — no commitment, no risk to your live system.