Moving platform

Import existing vouchers without losing the balances people rely on.

A voucher migration is a liability handover. Treat codes, remaining value and original terms as records to reconcile, not just rows to upload.

01A unique voucher code or reference for each active voucher.
02The original value and the remaining balance in the merchant’s currency.
03The Bronora product slug when the merchant has more than one active product.
04The original expiry date, where an expiry applies, in YYYY-MM-DD format.
05A record count and total remaining balance to reconcile against the previous system.
06A clear decision about vouchers that are expired, cancelled, refunded or already fully used.

Export before changing the old system

Take an export while the current platform is still available and record the date and time it was produced. Compare the number of active vouchers and the total outstanding value with the source reporting. If those figures do not agree, pause and resolve the difference before a new system treats the values as live balances.

Keep original expiry and customer promises

An import should not silently replace an existing voucher’s expiry, restrictions or balance. Preserve the original expiry where one applies and identify any vouchers that need a separate decision because they are expired, partially used, cancelled or subject to a customer query. The Irish expiry guide explains why this matters for many vouchers sold in Ireland.

Prepare the Bronora products first

Create the active voucher products that imported records will map to before uploading a CSV. When there is more than one active product, use the product slug in the file so that each imported voucher keeps the correct type of gift. Review the product terms alongside the source export; a new product description should not rewrite the promise made to an existing voucher holder.

Use the preview before commitment

Bronora’s import flow previews the CSV, shows a sample of the records and returns validation issues before it creates live voucher balances. Check the row count, totals, product matches, expiry dates and sample codes. The same file cannot be imported twice, but a careful preview is still the best place to catch an avoidable error.

Do not email active codes or customer records

Active voucher codes can be redeemed, so ordinary email is not an appropriate transfer channel for an import file. Use the secured import route available in the merchant workspace. If the available export does not fit the standard CSV format or the reconciliation is unusually complex, contact Bronora before transferring any customer or voucher data.

Plan a short cutover

Decide which system is authoritative during the move, brief the people who redeem vouchers and avoid selling from two uncoordinated voucher ledgers. After the import, check a small set of records against the old system, confirm that staff can look up the balance and keep the source export with the migration notes.

Open when you are ready

A voucher shop that works like part of the business.

  • No setup or monthly fee
  • 3% when a voucher sells
  • Your own Stripe account
Request launch access