To compare gift card migration options, start with a complete list of outstanding balances, then ask each provider how those balances can be recognized and reconciled after the switch. Compare a direct transfer, a period of parallel acceptance, and a manual exchange against the same inventory, costs, and acceptance test.
The safest-looking option is not necessarily the cheapest quote. A transfer that leaves some cards unrecognized, or a parallel setup that lets a guest spend the same balance twice, creates work at the counter. Before choosing, decide who owns each balance, how staff will look it up, and how a guest gets help when a card does not work.
Inventory cards, balances, and restrictions
Ask your current provider for an export of every card with an outstanding balance, including cards that have not been used recently. Request the balance in cents, card identifier, status, issue date if available, and any restrictions attached to the card. Also ask for a separate list of voided, expired, blocked, and zero-balance cards so you can investigate differences rather than silently leave records out.
Agree on an inventory timestamp. Cards can still be sold or redeemed while you prepare, so the first export is a starting point, not necessarily the balance you will move. Ask how to obtain transactions after that timestamp and who can produce a final balance file at cutover. If you cannot pause gift card activity briefly, establish how later activity will be captured and applied.
For each record, check the items that affect a guest's ability to use it:
- Identifier: Does the card have a number, barcode, or other credential the new system can recognize? Can the identifier be transferred safely without exposing full card details to unnecessary staff?
- Balance: Is it recorded in cents, and does the card-level total agree with the provider's summary?
- Restrictions: Are there location, channel, expiration, promotional, or other conditions that staff need to preserve or explain?
- Status: Is the card active, disputed, blocked, or subject to an unresolved adjustment?
- History: Can staff see enough prior activity to investigate a guest's balance question after the old account closes?
Do not assume every field can be imported. Ask both providers which identifiers and restrictions can move, which require a separate lookup, and what happens when a record is rejected. If some cards cannot be transferred, put them on an exception list with an owner and a resolution date.
Also map where guests currently redeem cards: at the counter, online, or at another participating location. If you use a restaurant ordering system, ask how gift card acceptance would work in that specific checkout. A successful in-store lookup alone does not answer the online question.
Compare three ways to change providers
Vendor transfer moves eligible records into the new provider's system. Ask for a sample import layout, supported identifiers, rejection reports, and a written description of how transactions between the initial export and cutover will be handled. Confirm whether old cards will still be recognizable or whether guests need replacements.
Parallel acceptance keeps the old provider available for existing cards while new cards are issued through the new provider. This can reduce immediate conversion work, but staff must know which system owns each card. Set an end date or review date for the old service, and agree how remaining balances will be handled. A balance should be spendable in one authoritative system at a time, not independently in both.
Manual exchange replaces old cards with new ones after staff verify each balance. It can be useful for a small exception group, but it adds counter time and creates a handoff risk. Record the old identifier, verified balance, new identifier, date, and staff member. Establish how the old balance is disabled or otherwise marked so it cannot also be redeemed.
The following hypothetical worksheet compares operational quote totals for one restaurant. The amounts are planning assumptions, not vendor prices. Fixed costs cover setup; variable costs cover expected handling; exception costs cover an allowance for investigating difficult cards. Payment processing, ongoing software charges outside the transition, and any legal or tax advice are excluded. Recalculate if those excluded costs differ between options.
| Option | Fixed + variable + exceptions | Transition total | Decision condition |
|---|---|---|---|
| Vendor transfer | $300 + $120 + $80 | $500 | Import and cutover preserve eligible card balances and restrictions. |
| Parallel acceptance | $100 + $240 + $90 | $430 | Old cards remain usable in one system, with a workable closeout plan. |
| Manual exchange | $60 + $300 + $150 | $510 | Staff can verify, replace, and retire old cards reliably. |
Under these assumptions, parallel acceptance has the lowest modeled transition total, $70 less than transfer. Choose it only if the old service can stay available for the required period, staff can route cards correctly, and the closeout plan is acceptable. If those conditions fail, the $70 difference does not make it a workable option. Request written quotes for the same scope and compare excluded charges before deciding.
These totals are transition costs. They are not gift card sales, guest balances, deposits, or quoted payment processing fees. Keep those figures separate when reviewing the plan.
Reconcile opening and closing balances in cents
Use a card-level ledger as well as a summary total. A matching total alone can hide one card being overstated and another understated by the same amount. Retain the original export securely, then record each accepted, rejected, or adjusted item against it.
In a separate hypothetical reconciliation, an inventory contains 120 active cards with a combined opening balance of 180,000 cents, or $1,800.00. After the inventory timestamp, one guest redeems 2,535 cents, or $25.35. There are no new gift card sales, refunds, voids, or other adjustments in this example. The expected closing balance is:
180,000 cents − 2,535 cents = 177,465 cents ($1,774.65).
Suppose the chosen transfer produces a destination report of 177,465 cents across the same 120 cards. The total agrees, but the work is not finished. Match each destination balance and identifier to the source ledger, including the one card reduced by 2,535 cents. Check restrictions and status as well. If the destination report instead shows 177,500 cents, there is a 35-cent difference to investigate before sign-off.
Record the source file timestamp, transaction window, expected closing total, destination total, card count, and exception count. For each mismatch, note the card identifier, expected and actual balances, likely cause, assigned owner, and next review date. Do not adjust a guest's balance simply to force the totals to match; trace the underlying transaction first.
For a parallel setup, the same principle applies without importing every card. The old system's remaining balance report is the control for cards it still owns. Track any cards exchanged into the new system separately, and make sure the old and new reports do not count the same spendable balance twice.
Set an acceptance test and an exception owner
Before cutover, agree on a test with the outgoing and incoming providers. Use a sandbox or other isolated test environment and a simulated card with a known balance. The practice must not charge a real payment method, send a guest message, or dispatch a courier. If the providers cannot supply an isolated environment, agree on a safe alternative before proceeding; do not improvise with a guest's live card.
Record the expected result before running the simulation:
- Create or load a simulated card with a balance of 4,000 cents and the identifier format staff will encounter.
- Simulate a partial redemption of 1,250 cents. The expected remaining balance is 2,750 cents.
- Look up the card again in the system designated as authoritative. Confirm that it shows 2,750 cents and that the transaction appears in the relevant report.
- Check that another system cannot independently spend the original 4,000 cents. For a manual exchange, verify the simulated old card is retired or clearly marked according to the agreed process.
- Repeat a lookup for a simulated rejected or restricted card. Confirm that staff receive a usable next step rather than guessing at the balance.
Accept the test only if the expected balance, transaction record, card routing, and exception handling all work as agreed. Write down the actual results and who approved them. A simulation proves only the scenario checked; it does not prove every card or checkout channel is ready.
Plan the live service pilot separately. Choose the locations, channels, dates, and staff who will participate, and explain the procedure before service. Monitor real transactions and reconcile them against the live ledger. Have a documented way to pause the rollout and help a guest if a card is not recognized. A live pilot involves real operations; it should not be confused with the isolated practice above.
Name one person who owns unresolved balances after cutover, plus a backup. Give front-of-house staff a short escalation path: capture the card identifier securely, explain when the guest can expect a response, and send the case to that owner. Decide how long the old provider's reports remain accessible and who can retrieve them. For contract terms or legal and tax treatment, consult qualified advisers rather than assuming the software workflow settles those questions.
Your wider restaurant management software review should include access controls and reporting during the transition. If you also plan guest communications, keep access to contact information separate from permission to send marketing. The loyalty reward cost guide can help with a separate rewards review; gift card balances should remain their own ledger.
Next step: Take your inventory and acceptance test to each provider, request written answers and quotes, then compare your marketing requirements with the workflows available from Fleksa's restaurant marketing tools, including the gift card workflow you need.
Frequently asked questions
Should I transfer every card at once?
Only if the providers can account for the full inventory, activity through cutover, and rejected records. A parallel period or manual exchange may be more practical for cards that cannot be transferred reliably.
What if the balance totals match but a guest's card does not?
Investigate the individual card against the source ledger and transaction history. A matching aggregate can hide offsetting errors on different cards.
When can I close the old gift card account?
Consider closing it after the remaining balances, exceptions, reporting access, and guest support handoff are resolved under your agreed plan. Check the account's terms before setting the date.
