Ask an owner why they have not changed point of sale systems, and outstanding gift cards come up faster than price does.

It is a reasonable fear. Those balances are money customers already paid you, sitting on cards you no longer control the database for. Handled badly, a switch turns every one of them into a guest standing at your counter holding something that does not work.

In this article

• Why Gift Cards Block So Many Switches

• What Actually Has to Move

• Plastic Is Not the Problem People Think It Is

• The Questions to Ask Before You Sign

• A Migration Sequence That Does Not Break the Counter

• After the Switch: Watching the Liability

• Where Peblla Fits — and Where It Does Not

• Frequently Asked Questions

Why Gift Cards Block So Many Switches

A gift card balance is a liability on your books and a promise to a guest. Unlike a menu or a floor plan, you cannot rebuild it from scratch — the numbers have to come across exactly, card by card.

That makes it the one part of a migration with no acceptable margin of error. A menu item priced wrong gets fixed at the register in ten seconds. A balance that came across short becomes a refund, an argument, and sometimes a review.

So owners do the rational thing and postpone. The result is that a system nobody likes stays in place for years, guarded by a few thousand dollars of outstanding balances.

What Actually Has to Move

Three things have to survive the switch, and they are easy to confuse with each other.

The card identifier. Whatever is printed, encoded or scanned on the physical card has to be recognizable to the new system. If the identifier changes, every card in a customer wallet is dead.

The remaining balance. Not the original load — the amount left today, per card, at a known moment in time.

The status. Cards that were deactivated, refunded or already emptied need to arrive in that state. Importing a zeroed card as active is how a closed liability quietly reopens.

Transaction history is the fourth item, and it is the one you can usually live without. It is useful for disputes, but it is not required for a card to work, and treating it as mandatory is a common reason migrations stall.

Plastic Is Not the Problem People Think It Is

Most owners assume a switch means reprinting every card. Usually it does not.

If your existing cards carry a magnetic stripe or a printed number, the identifier on the card is just data. A system that can import that identifier alongside the balance can keep the same plastic in circulation. Peblla supports importing gift card records from a previous system, including magnetic stripe cards, so guests keep using the card they already have.

This matters more than it sounds. Reprinting is not only a cost — it is a communication problem. You cannot reach the person who received a card as a gift eight months ago, and you should not need to.

The cards you sell after the switch are a separate question. Those are printed on the new program, and it is a reasonable moment to redesign them if the old ones were tired.

The Questions to Ask Before You Sign

Every vendor will say gift card migration is supported. These are the questions that separate a real answer from a hopeful one.

What file do you need from my current provider, and who requests it? If the answer is vague about who extracts the data, that work is about to become yours.

Can the existing physical cards keep working, or do we reissue? Ask it directly and get the answer in writing before the contract, not during onboarding.

What happens to a card that is used between the export and the go-live? There is always a window. The vendor should be able to describe how it is reconciled without you noticing.

Can I see a test import before cutover? A dry run on a copy of the file catches format problems while they are still cheap.

How do I report on the balance afterward? You need to be able to see the outstanding liability at any moment, not just at year end.

A Migration Sequence That Does Not Break the Counter

The sequence that works is unglamorous and it is always the same.

Request the export from your current provider early — this is usually the slowest step and it is entirely outside your control. Get a full card file with identifiers, balances and statuses.

Run a test import while the old system is still live. Pull ten cards you can physically hold, check each balance against the old system, and confirm the identifier scans on the new hardware.

Freeze new gift card sales for the last day or two before cutover. It is a small revenue delay and it removes an entire class of reconciliation problem.

Take a final export at cutover, import it, and spot-check the highest balances first. If something is wrong, it will hurt most on the biggest cards.

Then tell your staff what to do if a card fails. One clear instruction — look it up, honor the balance, note the card number — prevents a guest ever feeling the switch.

After the Switch: Watching the Liability

Outstanding gift card balance is real money you owe. Once it lives in the same system as your sales, it stops being an annual accounting exercise and becomes a number you can look at.

It is also a demand signal. A large unredeemed balance after the holidays is dormant revenue sitting in people's wallets, and a reminder text to card holders in a slow week often brings some of it back through the door — usually with a check that runs above the card value.

Where the card gets redeemed matters too. If a balance can be used at the counter, on a phone and at a table where the order is fired to the kitchen without staff doing anything special, redemption stops being an event and becomes ordinary.

Where Peblla Fits — and Where It Does Not

Peblla fits when the gift card program is meant to live inside the same system as the register and the guest record. Balances import from a previous provider with the existing plastic intact, cards sell and reload at the point of sale, and the outstanding liability shows up in reporting rather than in a spreadsheet someone maintains by hand.

It is not the right call if your gift cards are run through a mall or association program you are contractually part of, or if you are committed to a standalone card platform you have no intention of leaving. In those cases the card data is not yours to move, and no migration story changes that. This also does not make an old file clean — if your previous system has balances nobody trusts, importing them faithfully preserves the mess.

The wider reasoning for keeping cards, checks and guest history on one platform is covered in why restaurants choose Peblla.

Frequently Asked Questions

Do customers have to swap their old gift cards for new ones?

Not if the new system can import the card identifiers. Magnetic stripe and printed-number cards can usually stay in circulation, which matters because you have no way to contact someone who received a card as a gift.

What happens to the money on unredeemed cards?

It remains your liability and it remains the guest's money. A migration moves the record; it does not change who owes what. Escheatment rules vary by state, and that is a question for your accountant rather than your POS vendor.

How long does a gift card migration take?

The import itself is fast. The slow part is getting a complete export out of your current provider, which is why it should be the first thing you request, not the last. A single bakery with a few hundred active cards can be ready in days. A multi-location group carrying years of balances should plan for the export, a reconciliation pass, and a quiet cutover window.

Can I keep selling gift cards during the switch?

You can, but freezing sales for the final day or two before cutover is simpler. Cards sold in that window are the ones most likely to fall between two exports. A counter-service coffee shop can pause plastic and keep selling digital cards. A full-service dining room can hold physical card sales at the host stand until every migrated balance has been verified.

What if a card fails at the counter after go-live?

Give staff a standing instruction to honor the balance and record the card number rather than turn the guest away. Nearly all failures are lookup problems, and the cost of honoring one is far below the cost of the conversation you would otherwise have.

Will I lose the transaction history?

Often yes, and it is usually acceptable. Balances and statuses are what a card needs to work. Ask whether history can come across, but do not let it hold up a migration that is otherwise ready.

If outstanding balances are the reason you have not moved yet, the fastest way to settle it is to bring your card file to the Peblla team and watch a test import run against real cards before anything changes.