Software Integration Guide for Music Schools
Two tools carry almost all the integration load in a music school's stack — My Music Staff and QuickBooks Online. Everything else either plugs into one of those two, or it doesn't talk to the rest of your stack at all.
My Music Staff and QuickBooks Online carry almost all the integration load — the rest either plug in or stand alone
Based on the current integration map for a 15-teacher music school's tool stack.
Ask which tools in a music school's stack "integrate" and the honest answer is: almost everything eventually connects to either My Music Staff or QuickBooks Online, and a shorter list stands almost entirely on its own. That matters more here than in a lot of small businesses, because enrollment marketing, practice tracking, and billing all need to reach the same family record eventually — and which studio platform you picked decides how many of those connections are automatic.
The two hubs
My Music Staff and QuickBooks Online are the two nodes almost everything else in the stack connects through.
My Music Staff connects directly to Google Local Services Ads, Mailchimp, QuickBooks Online, Stripe, SmartMusic, Google Workspace, and DocuSign — seven connections, the widest reach of any tool in this stack, which is exactly why it functions as the operational hub even though it's the cheapest tool in its own category. QuickBooks Online connects directly to Gusto, Ramp, My Music Staff, Fons, and Stripe — five connections, and the one place tuition revenue and instructor pay are supposed to reconcile before the bookkeeper closes the month.
Direct connections per tool
Where the studio-platform hub actually reaches — and where Fons doesn't
Direct integration coverage, by tool
| Tool | My Music Staff | Fons |
|---|---|---|
| Mailchimp | ||
| SmartMusic | ||
| DocuSign | ||
| Stripe | ||
| QuickBooks Online |
Checking which side of an "integration" claim is actually live is worth doing before you build a workflow around it.
A Fons school running Mailchimp for recital and tuition-reminder email is relying on a tool that doesn't currently list a native Fons connection — that's a manual roster export, not automation, no matter how either sales page describes it. Same with SmartMusic: the practice data doesn't route back into a Fons roster automatically. And a signed DocuSign enrollment contract doesn't currently flow into a Fons student record the way it can on My Music Staff, so someone re-enters the family's details into the roster after signature either way on Fons.
The finance cluster runs on its own, mostly
Gusto and Ramp both connect to QuickBooks Online and to each other, but neither connects directly to either studio platform — which is normal, since payroll and expense cards have no reason to touch a lesson schedule. Both My Music Staff and Fons do connect directly to QuickBooks Online, so tuition-to-ledger reconciliation works cleanly regardless of which studio platform you run; the integration gaps in this stack live in marketing and practice tracking, not in finance.
Security tools protect the login, not the roster
1Password and Huntress secure the devices staff use to log into your studio platform — not the platform's own data.
1Password and Huntress connect to each other and to Google Workspace, not to either studio platform directly. In practice, that means your password manager and endpoint protection cover the devices front-desk staff use to access My Music Staff or Fons — they don't give you visibility inside the studio platform's own access logs or billing history. DocuSign connects to Google Workspace and, on My Music Staff, to the roster itself; on Fons it's a single-spoke tool that doesn't reach back into the platform.
Questions to ask before you assume two tools "integrate"
- Does the integration move roster or billing data, or is it just single sign-on?
- Is the connection listed on both vendors' side, or only one?
- If you switched studio platforms tomorrow, which of your other tools would silently lose their sync?
- Who currently owns re-entering data when a sync doesn't happen — front desk, bookkeeper, or nobody?
None of this changes the sticker price of any single tool — the optimized music-school stack still runs $1,115-1,409/mo either way. It changes how much front-desk time that number actually buys you, which is the real cost of a "good default" that still needs configuration.
Good default doesn't mean zero configuration. The marketing/practice-tool gap on Fons and the roster-to-Mailchimp export are the two places a music school loses the most hours to integration friction nobody priced in.
Run the free audit to see the full stack we'd build for a music school your size, with these integration gaps already factored into the recommendation — not discovered six months after you've signed.