Export your list first, since Waya doesn't connect directly to another app
Migrate off a standalone punch-card app by exporting your customer list as a spreadsheet first, then re-enrolling everyone onto a Waya wallet card — there's no direct one-click transfer between the two, because Waya doesn't integrate with third-party loyalty apps. Most punch-card apps let you export customers as a CSV or Excel file from their settings or support page; get that file before you cancel anything.
Once you have the list, there's no bulk import to load it into Waya — not on Growth, not on any plan. Message that list the enrollment link instead, so each customer adds their own card, and put a QR at the bay too for anyone the list misses. Stamp counts from the old app have to be re-entered per customer manually during the overlap window either way, since nothing brings across a stamp history from another platform.
This is more manual than moving from paper, ironically, because a paper card is physically in front of the customer at the till with its punch count visible, while an app's stamp history lives on a server you no longer control once you cancel the subscription.
Run a short overlap so nobody loses a stamp mid-switch
Keep the old app running for a two-to-four-week overlap while every customer who visits gets enrolled on the new Waya card, with staff asking each one for their current stamp count from the old app and crediting it manually. This is slower per customer than paper migration, but it only needs to happen once per person, at their next visit.
Don't cancel the old app's subscription until the overlap period ends and the bulk of regulars have visited at least once — cancelling early means losing the ability to verify a customer's claimed stamp count against the app's own records.
- Export your customer list as Excel/CSV from the old app before cancelling anything
- Message that exported list the Waya enrollment link so each customer adds their own card
- Ask each customer their stamp count at their next visit and credit it manually
- Keep the old app active through the full overlap window before cancelling
What transfers automatically vs. what doesn't
Setting expectations correctly before you start saves the most frustration during this specific migration.
| Data | Transfers automatically? | How to handle it |
|---|---|---|
| Customer name and mobile number | No — no direct integration | Message the exported list the enrollment link; add a QR at the bay too |
| Stamp/points balance | No | Manual credit per customer at their next visit |
| Push notification history | No | Not needed — new triggers start fresh on Waya |
| Ongoing wallet messaging | N/A — new to Waya | Set up welcome, stamp, and win-back triggers |
The migration, step by step
Doing this in order avoids the two failure modes: losing access to the old app's records too early, or leaving customers stranded with no card during the switch.
- Export the customer list
Pull a CSV or Excel file of names and numbers from the old app before cancelling.
- Build the Waya stamp card
Match the free-wash threshold customers already expect from the old app.
- Message the list its enrollment link
There's no bulk import — send the exported list the link so each customer adds their own card, and put a QR at the bay too.
- Print an overlap poster
Tell customers both cards work during the switch window, and for how long.
- Credit stamp counts at each visit
Ask, verify against the old app if needed, and manually add the matching stamps.
- Cancel the old app
Only after the overlap period ends and most regulars have visited at least once.
Where this fits against the Free plan
There's no bulk import step at all, not on Growth, not on any plan. What Growth buys during a migration is headroom: unlimited customers instead of the Free plan's 100-customer, 1-stamp-card cap. If your existing app has more than a small handful of customers, budget for Growth from day one of the migration rather than hitting the Free ceiling mid-switch.
Growth also raises the message allowance to 5,000 a month, useful during migration since you'll likely send an overlap-announcement campaign — the enrollment link plus a note about the switch — to everyone on the exported list at once.
After the switch
Once migration finishes, Waya works the same way for these customers as for anyone enrolled from scratch: staff scan the wallet card by hand on an ordinary phone, since Waya has no POS or till integration, and there's no SMS channel — only wallet lock-screen messages.
Send a short one-off message once the overlap ends: "Your wash card is now in Apple/Google Wallet — same free-wash deal, no more app to open."
Frequently asked questions
Can Waya import customer data directly from another loyalty app?
No. Waya doesn't integrate directly with third-party punch-card apps, and it has no bulk import either. Export your customer list as a CSV or Excel file from the old app, then message everyone on it the Waya enrollment link so each customer adds their own card.
Do stamp counts transfer automatically when switching apps?
No. Stamp or points balances have to be credited manually per customer, typically by asking at their next visit and crediting the matching count on their new Waya card.
How long should the overlap between the old app and Waya last?
Two to four weeks is usually enough to catch most regulars at their next natural visit, since car wash customers tend to return within that window anyway.
Is there a faster way to move a large exported list onto Waya?
Not a bulk import — Waya doesn't have one on any plan. The fastest path is messaging the whole exported list the enrollment link at once; Growth's 5,000-message allowance covers a large list where Free's 100-message cap would not, and a QR poster at the bay catches anyone the message misses.
Should I cancel the old punch-card app before or after the overlap ends?
After. Keeping it active through the overlap lets you verify a customer's claimed stamp count against the app's own records before crediting it manually on Waya.