Switching
Changing software mid-season, without closing
Four steps, one parallel week, and your existing terminal untouched. The old system stays available until your team says otherwise — which is the only migration plan anybody actually trusts.
- No day closed
- No new merchant account
- No contract either way
See exactly what comes across
- Clients and their visit history
- Services, durations and prices
- Staff, pay profiles and commission rules
- Future appointments already booked
- Outstanding package and gift card balances
The week, step by step
- 1
Send us what you have
A spreadsheet, or an export from your current platform. Clients, services, staff, price list and future appointments are what matter; the rest can follow.
Nothing changes at the counter while this happens.
- 2
We build your setup
Services with their real durations and cleanup time, staff with their real pay arrangements, rooms and chairs as the resources they are, taxes as they actually apply.
You review it before anyone books into it.
- 3
Connect the terminal you own
Dejavoo over the SPIn cloud proxy or PAX over your local network, using your credentials against your merchant account. There is a live connection test, so you know before a client is standing there.
No re-application. No new merchant account. No rate change.
- 4
Run both for a week
Take real sales on Groww POS alongside whatever you have now. A week of Saturdays tells you more than any demo, and nothing is switched off until your team says so.
The old system stays available the whole time.
The four things owners actually worry about
“We will lose our client history.”
Clients, their history and their upcoming appointments import first, because a client record that starts empty is what makes staff quietly keep using the old system.
“We will have to change payment processor.”
No. That is the point of the product. Your terminal, your merchant account, your negotiated rate — and no feature is withheld for keeping them.
“The team will hate it.”
Bring them to the demo and let them break it. The people who ring up twenty sales on a Saturday will tell you in five minutes what an owner might not notice in a month.
“What if it does not work out?”
No contract, and your data exports on request. Leaving should cost nothing but the time it took to try.
Migration questions
How long does a migration take?
For a single location with a clean export, the setup is usually ready to review within a few days. Multi-location and clinical setups take longer because permissions, registers and locations are worth getting right rather than fast.
Do we have to close for a day?
No. That is what the parallel week is for — you keep trading on your current system while real sales run through Groww POS alongside it.
What if my current platform will not export?
A spreadsheet works. Clients, services, staff and prices in columns is enough to build from; awkward exports are a common starting point rather than a blocker.
Will my card rate change?
No. You keep the merchant account and the rate you already negotiated. If that rate is already competitive, the calculator on the pricing page will tell you so.
What about gift cards and packages already sold?
Outstanding balances come across as part of the import. A client holding a package bought last month should not discover it vanished when you changed software.
Bring your busiest week. That is the one that matters.
A migration that survives a Saturday is a migration. Everything else is a demo.