Data import and export
From Muzeqo Wiki
Data import and export in Muzeqo covers how a school brings its existing records into the app and takes them out again. An import wizard reads spreadsheets and the exports of other systems, shows every row before anything is written, and can be undone. An “Export everything” page puts the school’s records into one zip of CSV files, which Muzeqo’s own import can read back.[1]
Imports never contact anyone: nobody is e-mailed by an import, and teachers and families are invited later, when the school chooses.[1]
Importing students, teachers and lesson types
The wizard takes three kinds of list: students with their parents or guardians (up to 2,000 rows a file), teachers (up to 200) and lesson types with their instrument, length and price (up to 500). Blank templates for each are published, generated from the same list of fields the wizard reads.[1]
- Column matching: the wizard proposes which column is which from the headings other systems and spreadsheets use, and from the values when a heading says nothing useful. The office can change any match.
- Preview: every row is shown with its values, its blocking problems and its warnings, numbered as in the spreadsheet. Names in capitals are tidied, “Surname, Given” is understood, phone numbers are normalised and duplicates are matched against what the school already has.
- Import: each row is written through the same code as the app’s own forms, so an imported student is exactly what the form would have made. Siblings who share a parent’s e-mail address are linked to the same parent. Plan limits are checked as rows go in.
- Undo: rows that failed can be downloaded, and a whole import can be undone in one step.
Teacher invitations from an import are held until the office decides to send them.[2]
Files and other systems
Files can be CSV, TSV or plain text, Excel workbooks in .xlsx format (the first sheet is read) or JSON. The older .xls format is not read, and the office is asked for .xlsx or CSV instead. Several files can be dropped in together. Each is recognised by its headings: a list of students, teachers or lesson types goes to its import, while a file recognised as something else — lesson history, invoices, payments, an address book or a calendar — is set aside with a note saying why it is not imported.[2]
The recognition rules know the export layouts of several other music-lesson management systems, as well as Google Contacts, Outlook, Xero, vCard and iCalendar files. Where the rules leave a column unmatched, Muzeqo AI can suggest a match from the headings and a description of what each column holds (such as “looks like an e-mail address”) — never the cell values themselves — if the school has it switched on (see Muzeqo AI).[2]
A host school’s own timetable can be typed into a grid, pasted or uploaded as CSV or TSV; that import is described in Lessons and timetable.
Timetable, balances and history
A second import, “Timetable, balances and history”, brings in what the import of people does not:
- Recurring lessons, created as the calendar’s own form would create them — with closures, terms, prices and clash checks — from the next matching day on. Nothing in the past is made up, lessons follow term time by default where the school has terms, and a row that would double-book is held back.
- Opening balances: past invoices and amounts owed in the old system, kept as a read-only record. They are not invoices — nothing charges, reminds or auto-pays them, and they are not counted as revenue — and the office raises an ordinary invoice to collect one.
- History: the old system’s audit trail or activity log, kept read-only and apart from Muzeqo’s own audit log, which records only what happened in Muzeqo.
Each kind is open only to the roles that may see it: the timetable to the office, balances to staff with finance access, and history to owners and admins. Like the other imports, it shows a preview first and can be undone.
Exporting
Under Settings › Your data, “Export everything” downloads one zip of CSV files holding the school’s records in Muzeqo: students and families, staff, the timetable and every lesson with its attendance, invoices, payments, credits and packages, expenses, pay runs, term reports, practice logs, jobs, the audit log, and the school’s reports for the current and previous financial years. The zip includes a README saying what each file holds and a manifest a program can read. Each file can also be downloaded on its own, and the audit log for a chosen date range.
Only owners and admins can export everything, and every export is recorded in the audit log. The export runs with the exporting person’s own permissions, filtered to the school, and leaves out secrets and values that are useless outside the app: password hashes, sign-in tokens, sealed numbers, bank account numbers and internal storage paths.
Other exports sit where their data lives: CSV downloads of each report, accounting files laid out for Xero (see Billing and invoices), private calendar feeds, a family’s statement of what it paid, and a teacher’s earnings statement (see Teacher pay).
Moving to or from Muzeqo
A school considering Muzeqo can send a sample of its current system’s export, and Muzeqo says what the wizard will bring across before the school starts; help reading an old system’s export is part of support on every plan.[3][2]
A school that leaves keeps its records: cancelling a plan deletes nothing, and the export gives the school its data to take to another platform, an accountant or an auditor (see Plans and pricing).[4]
See also
References
- abcd“Data import and setup”. Muzeqo. Retrieved .
- abcd“Everything in Muzeqo”. Muzeqo. Retrieved . The catalogue of features, group “Setup, import, exports and automations”.
- ^“Muzeqo: frequently asked questions”. Muzeqo. Retrieved . Home page questions and answers.
- ^“Pricing”. Muzeqo. Retrieved . Questions about cancelling a plan.
Facts last checked on .
