Evaluate Relay for staff, Pulse for retention, Momentum for sales or Circle for loyalty while booking and billing remain in Mindbody. We confirm the source access and workflow your studio needs before activation.
Connect: keep the approved source system and add a focused staff workflow.
Full ClassFlow: review imports, memberships and payments, then move core operations on an agreed launch plan.
Product selection alone does not establish compatibility, connect a provider or begin billing.
Ask for a written answer to these questions before using the workflow with live members.
Mindbody’s official developer FAQ describes business-granted site access, and its API billing FAQ describes location-based access charges. Those source capabilities do not establish a particular ClassFlow connector’s supported scope. Reviewed October 6, 2026.
Coverage, instructor context and team handoffs.
Attendance changes, explainable signals and owned member interventions.
A clear next step for inquiries, intro visits and sales conversations.
Participation, milestones, referral rules and staff-managed rewards.
Review all Connect products and current pricing. If you want to move booking and billing too, use the Full Platform migration guide and Mindbody alternative comparison.
Yes. Keep Mindbody authoritative for live booking and billing while you evaluate the ClassFlow workflow. Connect adds a focused product when the source data and provider permissions required for your studio are verified. Full Platform migration follows a separate import and cutover plan.
No. Signup records your product choice. ClassFlow must confirm the source account, approved access, location mapping, available records, refresh behavior and provider readiness before a live workflow is activated. This page does not promise a universal two-way integration.
Relay needs class and instructor context; Pulse needs member, attendance and membership context; Momentum needs leads, intro progress and conversations; Circle needs member participation and reward rules. The actual supported records and update method are confirmed for your studio, rather than inferred from the source vendor’s API.
Treat Mindbody as the booking and billing source unless a specific supported write action is documented and approved. Confirm every proposed write-back, staff permission and audit trail before enabling it. A prepared draft or task is not evidence that a source-system change has been authorized.
Payment credentials require an available processor-to-processor migration path. Confirm the current processor, destination account, memberships, renewal timing and any member action before launch. Member exports alone do not transfer saved-card tokens.
Tell us which product you need and how your studio uses Mindbody. We’ll review the required records, permissions and next setup step.