How to Move from a Paper Diary or Spreadsheet to Online Booking
By MyAppointments Team · 18 August 2026
The dangerous part of moving online is not the CSV import. It is the afternoon when the paper diary, spreadsheet and new calendar are all accepting changes and nobody knows which one to trust.
A calm migration has a boring shape: one owner, one cutover time, one read-only backup and a small test before the real data moves. That is the approach below.
Prepare before importing
Make a copy of your current diary or spreadsheet. Remove duplicates, check phone and email fields, standardise service names and identify appointments that still need to happen after your intended launch date. Only move information that you need for a clear business purpose and protect exports while you work.
Choose a cutover date and an owner
Pick a quiet, realistic launch window and name one person responsible for decisions. Write down which system is authoritative before, during and after cutover. If staff continue editing two diaries, conflicts become inevitable. A short written plan should include the final export time, import window, testing owner, customer communication and fallback route.
Do not choose a launch date only because a subscription renews. Allow time to correct data and support customers. Avoid the busiest week of the year or a period when the person who understands the diary is unavailable.
Handle personal information deliberately
A migration creates extra copies of customer information, so control where exports are saved, who can open them and when temporary files will be deleted. Do not email unencrypted spreadsheets between personal accounts. Use named access and keep a record of who performed the transfer.
The ICO’s guidance on data protection by design and default recommends considering privacy from the start of a project. Its security guidance helps frame access, storage and deletion controls. Apply current guidance to your circumstances and obtain advice where needed.
Clean a copy, not the original
Keep an untouched source export with its date and checksum or other identifying record. Perform cleanup on a working copy. Standardise dates, country codes, email casing and service names; remove obvious duplicates only when you can establish they represent the same person. Preserve future appointment references so they can be reconciled after import.
Do not invent missing consent or contact preferences. An empty field is more accurate than an assumption. Record any transformation rules so a result can be explained and repeated.
Map fields before moving rows
Create a mapping table from every source column to its destination field. Note data type, required format, default and what happens when the value is invalid. Pay special attention to time zones, all-day entries, appointment duration, staff identity and service price. A date that looks correct in a spreadsheet can be interpreted differently during import.
If one source column contains several ideas, such as “service - staff - room”, decide how it will be split. If the destination has no equivalent, choose whether the information belongs in a note or should remain in the archive.
Run a controlled setup
- Create services with accurate duration, price and any buffers.
- Add staff availability, opening hours and time off.
- Import a small test file first and review the results.
- Create several test bookings on a phone.
- Check confirmation, reminder, cancellation and payment wording.
- Keep the old diary read-only during the transition so there is one source of truth.
Test with representative records
A ten-row sample should include straightforward and difficult examples: a future appointment, an appointment around daylight-saving change, a customer with no email, a duplicate-looking name, a mobile service, a cancelled booking and text containing punctuation. Validate the result in the user interface, not only the import summary.
Check totals by category. Compare customer count, future appointment count, appointment value where relevant and the earliest and latest future dates. Spot-check records against the source and write down discrepancies.
Configure the booking rules before opening
Services, availability, buffers, deposits and cancellation rules determine what customers can create. Test each staff member and location. Confirm that private calendar events block time as expected and that online availability does not expose internal notes.
Create bookings as a new customer and a returning customer. Test cancellation, rescheduling, payment failure and an appointment inside the reminder window. Review every customer-facing screen and message.
Run a short parallel verification period
Parallel verification does not mean accepting new appointments into both systems. Keep one system authoritative and use the other as read-only evidence while staff compare the next several days. Resolve differences centrally and record the reason.
Give staff a visible cutover time. If a customer phones during the transition, everyone should know where to enter the booking and who can resolve uncertainty.
Tell customers exactly what changes
Send a short, factual message with the new booking link and explain what customers need to do. Do not turn an operational update into marketing unless you have the right basis and preferences for that channel. Keep a staff member available for customers who need help during the first week.
Prepare a fallback
Before launch, export or print the next few days of essential appointment information and store it securely for business continuity. Record vendor support details and the steps for disabling online availability if a serious issue appears. A fallback is not permission to keep uncontrolled copies indefinitely; set a deletion date.
Define the conditions for pausing launch, such as missing future appointments, wrong staff assignment or messages going to the wrong customer. Cosmetic preferences can wait, but data integrity and privacy cannot.
Support the first week
Review the next day’s appointments at the end of each day. Keep one issue log with severity, owner and resolution rather than scattered messages. Brief staff on common customer questions and how to escalate payment, privacy or duplicate-record problems.
Watch for bookings arriving through old links. Update your website, Google Business Profile, social profiles, email signature and saved message templates. Where possible, redirect rather than leaving two live routes competing.
Close the old process carefully
After reconciliation, remove edit access to the old system and document where retained records live. Cancel integrations only after confirming they are no longer needed. Delete temporary transfer files according to the migration plan and keep evidence that the cleanup occurred.
Do not destroy records that must be retained for an established purpose. Separate long-term archive obligations from day-to-day booking access and apply appropriate controls.
A seven-day launch rhythm
Two days before launch, freeze configuration and complete the final sample check. One day before, export and reconcile future appointments. On launch day, switch public links, monitor the first bookings and keep the issue owner available. For the next three days, review upcoming appointments and message failures daily. At the end of the week, resolve remaining medium-priority issues, remove temporary files that are no longer needed and brief the team on the confirmed process.
This rhythm is an example rather than a fixed rule. A larger team, several locations or sensitive records may need a longer staged migration and specialist support.
Doing the test import in MyAppointments
The MyAppointments import flow accepts customers, services or appointments from CSV. It reads the headers, lets you map source columns to destination fields, and shows a validation preview before the import runs. Use that preview as a challenge, not a ceremonial “next” button.
Start with ten awkward rows: a missing email, punctuation in a name, two similar customers, an appointment near a clock change and a service whose name changed last year. Compare the imported records with the source. Only then prepare the full file. After cutover, use customer management as the live record and make the old diary read-only. If you are still choosing the destination, step back to the software selection guide first.