Siirry pääsisältöön
100 paikkaa · Ilmainen kokeilu · Ei korttiaHae nyt
Etusivu/howToSwitch.hero.breadcrumbLabel

howToSwitch.hero.breadcrumbLabel

howToSwitch.hero.intro

howToSwitch.hero.eyebrow

howToSwitch.hero.title

howToSwitch.hero.intro

howToSwitch.hero.microTrust

howToSwitch.fearAcknowledgment.eyebrow

howToSwitch.fearAcknowledgment.title

howToSwitch.fearAcknowledgment.intro

howToSwitch.fearAcknowledgment.fears.lostData.title

howToSwitch.fearAcknowledgment.fears.lostData.calmly

howToSwitch.fearAcknowledgment.fears.lostData.ourPromise

howToSwitch.fearAcknowledgment.fears.staffRetraining.title

howToSwitch.fearAcknowledgment.fears.staffRetraining.calmly

howToSwitch.fearAcknowledgment.fears.staffRetraining.ourPromise

howToSwitch.fearAcknowledgment.fears.downtime.title

howToSwitch.fearAcknowledgment.fears.downtime.calmly

howToSwitch.fearAcknowledgment.fears.downtime.ourPromise

howToSwitch.timeline.eyebrow

howToSwitch.timeline.title

howToSwitch.timeline.intro

  1. howToSwitch.timeline.steps.day1.label

    howToSwitch.timeline.steps.day1.title

    howToSwitch.timeline.steps.day1.commitment

    howToSwitch.timeline.steps.day1.outcome

  2. howToSwitch.timeline.steps.week1.label

    howToSwitch.timeline.steps.week1.title

    howToSwitch.timeline.steps.week1.commitment

    howToSwitch.timeline.steps.week1.outcome

  3. howToSwitch.timeline.steps.weeks2to4.label

    howToSwitch.timeline.steps.weeks2to4.title

    howToSwitch.timeline.steps.weeks2to4.commitment

    howToSwitch.timeline.steps.weeks2to4.outcome

  4. howToSwitch.timeline.steps.month2.label

    howToSwitch.timeline.steps.month2.title

    howToSwitch.timeline.steps.month2.commitment

    howToSwitch.timeline.steps.month2.outcome

howToSwitch.staysVsChanges.title

howToSwitch.staysVsChanges.subtitle

howToSwitch.staysVsChanges.labels.before

howToSwitch.staysVsChanges.comparisons.staysClientData.before.title

howToSwitch.staysVsChanges.comparisons.staysClientData.before.description

howToSwitch.staysVsChanges.labels.after

howToSwitch.staysVsChanges.comparisons.staysClientData.after.title

howToSwitch.staysVsChanges.comparisons.staysClientData.after.description

howToSwitch.staysVsChanges.labels.before

howToSwitch.staysVsChanges.comparisons.staysScheduleStructure.before.title

howToSwitch.staysVsChanges.comparisons.staysScheduleStructure.before.description

howToSwitch.staysVsChanges.labels.after

howToSwitch.staysVsChanges.comparisons.staysScheduleStructure.after.title

howToSwitch.staysVsChanges.comparisons.staysScheduleStructure.after.description

howToSwitch.staysVsChanges.labels.before

howToSwitch.staysVsChanges.comparisons.changesAutomation.before.title

howToSwitch.staysVsChanges.comparisons.changesAutomation.before.description

howToSwitch.staysVsChanges.labels.after

howToSwitch.staysVsChanges.comparisons.changesAutomation.after.title

howToSwitch.staysVsChanges.comparisons.changesAutomation.after.description

howToSwitch.staysVsChanges.labels.before

howToSwitch.staysVsChanges.comparisons.changesReporting.before.title

howToSwitch.staysVsChanges.comparisons.changesReporting.before.description

howToSwitch.staysVsChanges.labels.after

howToSwitch.staysVsChanges.comparisons.changesReporting.after.title

howToSwitch.staysVsChanges.comparisons.changesReporting.after.description

howToSwitch.staysVsChanges.cta

howToSwitch.staysVsChanges.ctaNote

howToSwitch.founderLedSetup.eyebrow

howToSwitch.founderLedSetup.title

howToSwitch.founderLedSetup.intro

howToSwitch.founderLedSetup.founderName

howToSwitch.founderLedSetup.founderStudio

howToSwitch.founderLedSetup.agendaHeading

  1. 1

    howToSwitch.founderLedSetup.agenda.studioAudit.title

    howToSwitch.founderLedSetup.agenda.studioAudit.body

  2. 2

    howToSwitch.founderLedSetup.agenda.parallelPlan.title

    howToSwitch.founderLedSetup.agenda.parallelPlan.body

  3. 3

    howToSwitch.founderLedSetup.agenda.staffWalkthrough.title

    howToSwitch.founderLedSetup.agenda.staffWalkthrough.body

  4. 4

    howToSwitch.founderLedSetup.agenda.goLive.title

    howToSwitch.founderLedSetup.agenda.goLive.body

  5. 5

    howToSwitch.founderLedSetup.agenda.checkin.title

    howToSwitch.founderLedSetup.agenda.checkin.body

howToSwitch.termsReassurance.eyebrow

howToSwitch.termsReassurance.title

howToSwitch.termsReassurance.intro

howToSwitch.termsReassurance.bullets.noSetupFees.title

howToSwitch.termsReassurance.bullets.noSetupFees.body

howToSwitch.termsReassurance.bullets.noCardOnFile.title

howToSwitch.termsReassurance.bullets.noCardOnFile.body

howToSwitch.termsReassurance.bullets.cancelAnytime.title

howToSwitch.termsReassurance.bullets.cancelAnytime.body

howToSwitch.termsReassurance.closer

Usein kysytyt kysymykset

Löydä vastauksia yleisimpiin kysymyksiin Pepperoni Booking -palvelusta

Nothing — you don't have to bulk-import anything before you begin. Your current system keeps its records exactly as they are. New bookings populate Pepperoni naturally as your existing clients book through it for the first time. The relationship with each client carries; the system just learns about them as they show up.
Yes — that's the default path. The parallel-run period exists specifically so you don't have to commit before you've seen Pepperoni work on real bookings. One class type, one instructor, or one location goes live on Pepperoni first. Everything else stays where it is. You decide when (or whether) to retire the old system.
Not in any meaningful sense. The instructor view is small on purpose — instructors see the day's classes, students, and attendance. There's nothing to learn beyond logging in. We've onboarded instructors who use Pepperoni daily without ever attending a training session.
The parallel-run approach is specifically designed for this. Your team doesn't switch tools all at once — they see Pepperoni handle one class type while everything else stays familiar. Most resistance disappears when staff realize they're not being asked to abandon what they know. They add to it.
You can leave at any time. There's no contract, no termination fee, and no setup fee paid upfront that you'd lose. The 45-day trial requires no card on file. Monthly billing means cancellation takes effect at the next cycle. The decision to switch is reversible by design.
Almost nothing. Where bookings are flowing through Pepperoni, clients see a new booking link — same studio, same brand, just a cleaner experience. Where bookings are still on your current channels, nothing changes for them. There's no email blast asking clients to migrate, no password reset, no 'please join our new system' moment.
Most studios are running the majority of their bookings on Pepperoni by month two. Day one is a 30-minute founder call and basic setup. Week one moves one class type. Weeks two through four run both systems in parallel. By month two, the decision to fully switch is usually a non-event — the new system has been running for weeks.
No. Founder-led onboarding is included in the plan price. There's no separate setup fee, no implementation contract, and no consulting bill at the end. The founder is on the calls because every studio in the founding cohort gets the same level of attention — that's part of the program, not an upgrade.

Onko sinulla vielä kysyttävää?

Näytä kaikki UKK:t

howToSwitch.finalCta.titleLine1howToSwitch.finalCta.titleLine2

howToSwitch.finalCta.subtitle

howToSwitch.finalCta.trustSignal