Day one
Client import: move from another system without losing anyone
The clinic exports its current base to a spreadsheet, uploads the file and sees a preview: how many rows land, which columns were recognised and exactly which rows stay out, with the row number and the reason. Only after that is anything saved.
Switching systems usually stalls at one point: the client base stays behind. Import exists to take that barrier out of the way — and so nobody finds out months later that people went missing.
- Preview before saving: nothing lands without your check
- Every discarded row comes back with its row number and reason
- Recognises headers in Portuguese, English and Spanish
- A phone repeated in the file is flagged, not duplicated in the system
- Large files travel in batches, with no practical ceiling
- Export sits in the same place: your base leaves whenever you want
How it works, from file to base
You export the spreadsheet from your current system and upload it. The reader identifies the name column, the WhatsApp column and the birth date on its own, accepting the labels systems tend to use. Dates arrive as day/month/year or in the international format and are normalised.
- Upload the file as CSV, with one header row
- Check the preview: rows read, rows landing and what stayed out
- Open the problem list and fix the spreadsheet if you want
- Confirm — and only then is the base written
Nothing disappears quietly
A row with no name, no WhatsApp, an incomplete phone or repeated inside the file itself does not land — and it shows up on the list, with the row number so you can find it. That is the point: in a migration, losing a client without warning is worse than not migrating.
Duplicates handled on the server
Before saving each client, the system locks that phone number and checks whether it already exists in your clinic. If it does, the row counts as skipped instead of creating a second record. Every creation is written to the audit trail, marked as coming from a batch.
Leaving is easy too
The same screen exports your base as CSV, with name, phone, funnel stage, temperature, opt-out and signup date. Your base is yours: coming in must never be easier than going out.
What the import does not do
Real limits, so you can plan the migration:
- Imports name, WhatsApp and birth date — it does not bring appointment history, records, photos or finance
- Needs a name column and a phone column; without both the file is refused rather than guessed
- Does not connect to the previous system's API: the bridge is the spreadsheet
- An existing client is skipped, not merged — merging duplicates is a separate tool with double confirmation
Frequently asked
Questions about switching systems
My spreadsheet came from another system with different column names. Will it work?
In most cases yes: the reader accepts labels such as name, client, patient, phone, mobile, WhatsApp and their Portuguese and Spanish equivalents. If it cannot recognise them, the file is refused with a warning rather than importing the wrong column.
How many clients can I import at once?
There is no practical ceiling. The upload is split into batches automatically, so a base with thousands of clients lands in the same operation.
What if I import twice by mistake?
Anyone already there is skipped. The system checks the phone under a lock before creating, so repeating the import does not create duplicate records.
Can I undo it?
There is no bulk undo. That is exactly why the preview comes first: you check what will land while it still has not landed.
Bring your base and look before it saves
Create the account, upload the spreadsheet and check the preview with no commitment.
Meet Bia