The OptiFlow team · Updated 2026-07 · 6 min read
The spreadsheet is not to blame
Let us start fairly: a spreadsheet is an excellent tool, and in many stores it has run the customers, the orders and sometimes the prescriptions for years. If it carried you this far in good order, that is a sign of discipline, not amateurism.
The problem is not the spreadsheet — it is growth. One file works beautifully for one person; it starts to crack when several people need to update it at once, when “copy of copy of copy” files appear, and when the links between things — customer, exam, order, payment — live only in the memory of whoever built the file.
The signs the time has come
Some familiar signs: the same customer appears twice under different spellings; nobody is sure which file is current; a simple question like “what was ordered for this customer, and when” means opening three files; and the file that really matters lives on one computer — or with one employee.
The deepest sign is dependence: when the business cannot answer a customer without a particular person or a particular computer, the information is no longer an asset of the business. That is usually the moment owners start looking for a system.
Migration is a process change, not a copy-paste
The common mistake is translating the move into “get the whole spreadsheet into the system”. That is not the goal. The goal is that from today onward, the work happens in one place. History matters — but not all of it equally.
The practical distinction: what is alive moves; what is dormant gets archived. Active customers, open orders and recent prescriptions belong in the system. A table of customers who have not visited in years can remain a reference archive. Trying to move everything at once is the surest way to postpone the move by another year.
Move gradually — do not gamble
A good migration looks like stairs, not a leap: pick a date from which every new customer, appointment and order is opened only in the system. Existing customers move as they show up — someone walks in or calls, a card is opened, and their relevant history comes in with them. Within a short while, the customers who are genuinely active are inside.
Two rules keep the process sane: the old spreadsheet becomes read-only — consulted, never updated; and each employee learns their own part first — front desk the diary, sales the orders — instead of a single all-day course about everything.
Documents, money and the books
A moment of caution: financial documents and bookkeeping are not just another table to migrate. How the period closes in the old tool, from which date documents are issued from the system, and how continuity is kept in the books — settle these with your own accountant before the move, not after it. One hour of coordination up front saves a whole year-end of untangling.
The move as an opportunity — and a word about us
A system change is also a rare chance to tidy up: merge duplicate customers, drop fields nobody ever filled, and set one process where three habits used to live. Do not rebuild the spreadsheet inside a system — build the process you always wanted.
And if you evaluate OptiFlow: it is built around the workflow described here — customer, appointment, exam, prescription, order, payment — in full Hebrew, with or without stock tracking, and onboarding happens gradually, together with you. The best way to test it is exactly as above: bring your own scenarios and watch them run.