From a spreadsheetThe spreadsheet was the system. Now it is the import file.
Most training providers we meet run on a spreadsheet, a booking form and a shared inbox. It works until it does not. Cademy imports the spreadsheet in an afternoon and gives every row a record.
What the spreadsheet did, and what does it now.
| The spreadsheet | Cademy | |
|---|---|---|
| Course dates | A tab per year, capacity in a cell | A schedule, with capacity, waitlist and price on each date |
| Bookings | Typed in from emails and a form | Taken on your website, paid, confirmed and reminded automatically |
| Who attended | A tick column | A register on the date; attendance issues the certificate |
| Certificates | Made in Word, filed somewhere | Issued automatically, with an expiry date, on the learner’s record |
| Invoices | Raised by hand, chased by memory | Raised at booking with the PO, posted to Xero, overdue reminders on |
| Who paid for whom | A column, if you were disciplined | Contacts linked to organisations, automatically by email domain |
| Two people editing | A conflict | A team, with roles |
One CSV per thing.
Export what you have
Contacts, organisations, courses, dates, registrations and orders. One sheet each, any column names.
Map and import
Match your columns to Cademy fields. Contacts import on every plan, courses from Pro. We will do it with you on a call.
Switch the website over
Embed the course list on your site, or use your Cademy booking page. The spreadsheet retires.
Everything with a date on it. Especially the dates.
Migrations go wrong when history is left behind. We move the history, not just the list.
Titles, prices, formats and settings. Video and SCORM upload straight into the outline.
Future dates with venue, trainer and capacity, bookable on day one. Past dates for the records.
Every contact with their organisation and tags.
Who booked what, imported as bookings and orders.
Who attended what, so the history is on the record from day one.
The old widget comes off, the Cademy snippet goes on. Same pages, live dates.
Five working days, one person on our side who knows your setup.
The plan for a typical provider. Larger migrations get a scoped one, in the same shape.
Kick-off and export
A call with our team. We agree what moves; you export what you can.
Export in handImport and mapping
We map your fields and import into a staging account. You check a short list.
Data in, checkedWebsite, payments, calendars
Snippet on your site, Stripe and Xero connected, calendars synced.
BookableTeam and automations
Logins with the right roles. Reminders and follow-ups switched on, in your words.
Running itselfFirst course live
Register taken, certificate issued, invoice in Xero. Old system off.
LiveUp and running in a week. Not a quarter.
Before retiring the spreadsheet.
Does my spreadsheet have to be in a particular format?
No. Export it as CSV and map the columns during the import. If a column does not exist in Cademy, leave it out or put it in notes.
Can I import certificates I issued before?
Not as certificates. Import the registrations with their dates and we can help you record which ones were certified.
How much does Cademy cost?
There is a free plan. Pro is £99 a month billed yearly, or £119 monthly. Teams is £499 a month billed yearly, or £599 monthly.
Can I keep the spreadsheet for a while?
Yes. Exports to CSV are on every plan, so the spreadsheet can stay as a report while the bookings run in Cademy.
Send us the spreadsheet.
We will tell you what imports as-is and what needs a tidy, before you commit to anything.
No card needed. Import a spreadsheet and run a course this week.