Operations
Updated Oct 2026
Moving a paper appointment book online in one week
A paper book is not the problem. The problem is that everything you know about your clients lives in your handwriting, and handwriting does not export.
Why one week is the right deadline
Migrations that get a month become projects. Projects get postponed, and the book stays on the desk for another year. A week is long enough to do the work properly and short enough that you cannot drift. You will not end up with a perfect archive. You will end up with a working calendar and a clean client list, which is what the business actually runs on.
Pick the week carefully. Start on a Monday, finish on a Sunday, and treat the Sunday as the cutover day.
What to move, and what to leave
| Item | Move it? | Reason |
|---|---|---|
| Future appointments | Yes, all of them | This is money already booked. Nothing else matters more. |
| Names and mobile numbers | Yes | Your only irreplaceable asset. |
| Visit history | Last 12 months only | Older history almost never changes a decision. |
| Notes, formulas, allergies | Yes, shortened | Colour codes and allergies must survive the move intact. |
| Old no-show records | No | Keep the book. Do not import grudges into a new system. |
| Prices and durations | Yes | Online booking needs both to work at all. |
The seven-day plan
- Monday: choose, then stop comparing. Write down three requirements before you open any pricing page: reminders you can edit, a deposit option, and a client-facing booking page. Pick the first tool that meets all three.
- Tuesday: build the service list. Every service, real duration, real price. Use the duration you actually take, not the one you wish you took. If a colour service runs 2.5 hours, enter 2.5 hours.
- Wednesday: enter clients. Names and mobile numbers first, notes second. Do not attempt full records for everyone. Get the list usable, then fill gaps as people book.
- Thursday: enter every future appointment. Work backwards from the last page of the book. Mark each one off in the book with a pencil tick so you can see progress and catch missed rows.
- Friday: set opening hours and blocks. Lunch, school run, the hour you keep for admin. If you skip this, the system will happily sell that hour and you will resent it.
- Saturday: announce it. One message to everyone with a future booking, plus a post. Keep it short: the link, the reason, and what stays the same.
- Sunday: cut over. Turn on the booking page, update your Google Business Profile, Instagram bio, and any printed material you can reprint cheaply. Then close the book.
The client data problem
The book itself is easy. The phone is where the mess is. Expect these issues and decide how to handle them before Wednesday, not during it.
- Names written as descriptions. "Anna mobile", "the Tuesday lady", "James wife". You will need to make a judgement call and it is fine to enter "Anna (Tue)" and fix it later.
- Duplicates. The same person under two spellings with two numbers. Merge on the mobile number, not the name.
- Missing country codes. Add the country code to every number as you type. This takes a second per client and saves a failed reminder later.
- Bookings under someone else's name. A parent booking for a teenager. Create a record for the person attending, with the payer's number in the notes.
The month after cutover
Keep the book, but move it
Put it in a drawer, not on the desk. For the first two months you will hear "I usually get the same colour" and the answer will be in the book rather than the new system. Treat it as a reference document, not a backup. A backup gets used, and a migration that gets used reverses itself.
What breaks in week two
The first week is setup. The second week is where migrations fail, and it is almost always one of these four things.
- Reminders arrive from an unknown number. Tell clients to save the sender in their contacts. A saved sender is read; an unknown number is ignored.
- Double bookings. If you run both systems in parallel, end parallel running on a fixed date and do not extend it.
- Deposits feel sudden. Announce the policy a week before you enforce it, even if you announced the software.
- Staff revert to the book. Usually because the system is slow at the desk. Remove the book entirely and fix the speed problem instead.
What good looks like on day eight
Every future appointment is in the system, every client has a number with a country code, the booking page loads on a phone in under three seconds, and the book is in a drawer. That is the whole target. You do not need a perfect archive, a loyalty programme, or a marketing plan to call the migration done.
If you are still choosing, the comparison of Booksy, Fresha and Square Appointments covers the three tools most small studios end up with. Once you are live, the next win is a reminder sequence that actually cuts no-shows.