Move your client list from CSV to Skedful.
A practical map of the files, columns and checks. Import clients first, then any future bookings you can prepare in the required format.
Start with your original exports
Download a client list and, if needed, a separate future-appointments file from your current system. Keep the originals unchanged and work on copies. CSV is required for the Skedful upload.
Export instructions checked 29 September 2026
Import in the right order
Prepare your client CSV
Keep a name column or first and last name columns. Map email, phone and notes when available. Save as CSV and check that sensitive data is shared only with authorized staff.
Open Clients → Import from CSV
Upload the client CSV in Skedful. Check every proposed column match and the preview counts for invalid and already present rows before confirming.
Set up services and staff
Create active services and any staff who will own future bookings. The booking import matches existing records by exact name and does not create them.
Prepare and import future bookings
Use Schedule → List → Appointments → Import bookings. Enter a source name and keep it unchanged on retries. Include a stable original reference, existing client email, active service and an ISO 8601 start time with offset, for example 2026-11-04T14:00:00+02:00. Preview conflicts, then confirm.
Check the result before switching links
Compare client and future-booking counts with your source. Inspect failed and skipped rows, then verify a few bookings by date, staff and client. Only then update your public booking link.
What the CSV importer reads
Clients
Name (or first and last name), email, phone and notes. A name is required. Invalid email rows are skipped; an unparseable phone is omitted with a warning. Review the proposed column mapping before confirming.
Upcoming bookings
A separate CSV import accepts a unique source booking reference, existing client email, active service name and a future start time with a timezone offset. Staff, end time and internal notes are optional. Add services and staff first; bookings do not create them.
File limits
Client imports accept up to 5,000 rows. Booking imports accept up to 500 rows, 50 columns and 500 KB per file. Split larger files and preview each batch.
What does not come across
History and payments
Past visits, lifetime spend, payment history and stored payment cards are not imported. Keep a private copy of your original export for records.
Services and consent
Services, staff accounts, signed consent forms and marketing consent do not transfer. Set up services and staff yourself; collect fresh consent where your process requires it.
No automatic messages on import
Importing clients or bookings does not itself send a welcome message, booking confirmation or reminder. Later ordinary edits and scheduled workflows may still act on imported bookings.