The Skedda importer takes the CSV that Skedda exports and turns it into venues, users, and bookings here. It is built for the export Skedda actually produces, so you do not need to reshape the file first.
Only organisation admins can run an import.
1. Export your data from Skedda
In Skedda, export or print your booking data as CSV. Export the widest date range you care about — past bookings give the importer enough history to suggest sensible operating hours and booking constraints for each venue, which saves a lot of manual setup later.
2. Upload the file
- Open Import from Skedda in the dashboard sidebar
- Upload the CSV
- Review the preview — it shows how many bookings, spaces, and bookers were found
The importer groups related rows into logical bookings, so a single reservation split across rows in the export comes through as one booking here rather than several.
3. Map your spaces to venues
Every distinct space in the export is listed with a suggested match against your existing venues. Accept the suggestions that are right, correct the ones that are not, and create new venues for the spaces you have not set up yet.
This is the step worth slowing down on. A space mapped to the wrong venue puts real bookings on the wrong court, and untangling that afterwards is manual work.
4. Map your bookers to users
The same matching happens for the people who made the bookings. Match them onto existing users where you have them, and let the importer create the rest so historic bookings keep their owner.
5. Review and import
The final step summarises what is about to happen and lets the importer derive operating hours and booking constraints for new venues from the historical bookings it can see. Start the import and progress streams as it runs — large exports are processed in batches.
After the import
- Spot-check a busy week in the calendar against the same week in Skedda
- Open each new venue and confirm the derived operating hours match your real ones
- Check booking durations and time increments on venues the importer created
- Only then enable your public booking page, so customers never see a half-migrated schedule
Run the import once
Import in a single pass rather than uploading the same export repeatedly. Re-running an import with the same file can create duplicate bookings, and cleaning those up is slower than getting the mapping right the first time. If something looks wrong partway through, finish, check the calendar, and delete rather than re-importing over the top.