Begin with the rewards you already owe
Quick answer
To migrate paper loyalty cards to digital, start with your existing promise. Customers collected stamps because you offered a benefit. A new platform is an opportunity to improve convenience, but it should not quietly erase earned progress or make an existing reward harder to use.
An operator in a Square Community migration discussion describes honoring old paper cards during a transition. That is one policy example, not a universal formula. Your best approach depends on outstanding cards, earning rules, staff capacity, and the commitments you originally made.
Choose a transition policy customers can understand
You have several options. Continue accepting old cards until completion while issuing only digital cards to new participants. Convert verified paper progress into an equivalent digital balance. Or offer a clearly explained, reasonably generous settlement of outstanding paper rewards while launching different future rules.
If paper earning was item-based and digital earning will be spend-based, do not convert by guesswork. Define what the old progress entitles the customer to, then map that value transparently. Already earned free items may need to remain a separate redemption entitlement rather than being converted to a smaller points balance.
Boomerangme's digital punch cards allow configurable stamp and reward structures. That can help you preserve the existing customer experience instead of redesigning everything on launch day. A migration pilot is easier to explain when customers recognize the old earning threshold.
Understand the actual import limits
Boomerangme's customer-import documentation supports starting stamp counts and reward-point balances through CSV imports. It also states that existing multipass visit balances cannot currently be bulk imported. Those visits require manual handling in the customer profile or scanner workflow.
This is not automatic portability from every platform or a photograph of every paper card. You still need to verify the source balance, prepare the correct template, select the intended card, and test the result. Different card types use balance fields differently, so a generic spreadsheet copied across programs can create incorrect benefits.
Keep paid gift-card value, prepaid packages, and promotional stamp rewards separate. They may represent different obligations and need different records. Do not turn a customer's prepaid service balance into a discretionary loyalty reward simply because both can appear on a digital card.
Work through a small conversion example
Suppose, hypothetically, a paper program earns a regular drink after eight stamps. A customer presents a verified card with five stamps. If your new digital program uses the same rule, recording five starting stamps is straightforward. Confirm that the installed card shows five and that the next three eligible purchases unlock the intended benefit.
Now suppose you want a ten-purchase threshold. Adding five stamps without explanation would reduce the value of the customer's progress. Options include keeping an old-program digital template for those customers or honoring the old benefit separately while new purchases follow the new rules. Cost the decision and explain it before staff face the question at checkout.
Do not assume one policy fits already completed cards. A customer who has earned a reward needs an entitlement that staff can actually redeem, not merely a historical progress number that fails to trigger the promised benefit.
Prevent double counting without creating confrontation
Create a one-time migration record with the old balance, new balance, date, and employee who verified it. Mark or retain the surrendered paper card under your announced policy. If customers may keep it as a keepsake, clearly indicate that its reward value has transferred.
Boomerangme's import/export guidance describes CSV templates and customer exports. Use a small test file before a bulk import and retain a reconciliation copy in your approved record process. Check duplicates and identifiers carefully; a shared household email does not always mean two cards belong to one account.
A migration-day checklist
- Inventory old terms, known balances, completed rewards, and prepaid liabilities separately.
- Publish the conversion policy and a reasonable transition period.
- Test zero, partial, complete, and disputed balances in the chosen card type.
- Train staff on verification, paper-card marking, and the exception route.
- Confirm enrollment and messaging permissions rather than assuming import grants consent.
- Offer a documented alternative for customers without a suitable smartphone.
- Audit a sample of installed cards against original balances after launch.
Questions owners ask
Can I import a photograph of every paper card automatically?
Do not assume that capability. The documented import process uses structured customer data and card-specific balances. Verification and conversion decisions still require a business process.
Should I change the reward threshold during migration?
You can review future rules, but protect existing earned value. Keeping a familiar threshold during the pilot reduces explanations and makes balance testing easier.
Can old multipass visits be bulk uploaded?
Current Boomerangme documentation says existing multipass visit balances are not supported in bulk import. Plan the manual workflow and staffing before committing to that migration.
Make the move feel like an improvement in service, with each customer's progress accounted for. Explore Boomerangme and run a small migration test with your real card types before announcing a complete switch.
Sources & further reading
- Boomerangme digital punch cardsVerified configurable stamp/reward structure used to discuss preserving an old program.
- Boomerangme customer import and reward preservationVerified stamp and point import support; existing multipass visit balances cannot be bulk imported.
- Boomerangme import/export guidanceObserved CSV templates and exports; article does not claim automatic migration or transferred permissions.
Sources reviewed October 5, 2026. Numerical examples are illustrative unless a cited source states otherwise.



