Migrating from Clover

Clover shows you your outstanding gift card balances clearly, but getting a self-serve CSV of the full card numbers is the least documented step across the major platforms. This guide gives you the report to start with, and an honest fallback if you cannot export full numbers yourself.

Deactivate first

Freeze or deactivate your gift cards in Clover before you export, so a customer cannot spend the same balance in both Clover and Shopify. Export at the moment of cutover. See the migration hub for the full reasoning.

Run the Outstanding Balance report

1. Open your Clover Dashboard.
2. Go to Reports > Gift Cards.
3. Open the Outstanding Balance report.
4. Set your date range.
5. Use the Columns button to add the columns you need.

This report includes the gift card number, starting balance, remaining balance, activation date, last transaction date, promo code, and description.

Getting the full card numbers

You need the complete card number to preserve a card. A masked or last-four number cannot be imported. Before you go further, confirm your export shows complete, unmasked numbers. If it does not, the contact-support route above is the reliable path, and it is a normal request for Clover support to handle.

Which balance to import

Import the remaining balance column, the amount each customer has left to spend, not the starting balance.

Check your codes

Clover gift card numbers are typically 16 numeric digits, which fit Shopify's 8 to 20 letter-and-number rule and carry over as-is. Because Clover programs are often processor-backed, code length and format can vary, so check your file.

If any code falls outside the 8 to 20 letter-and-number rule, use the fresh-code workflow to reissue those cards and notify those customers.

Import into BatchCard

1. In BatchCard, map the Clover gift card number column to Code and the remaining-balance column to Value.
2. Review the mapping and validation results.
3. Create the batch.

For the full walkthrough, see the import guide. The CSV and XLSX format reference documents the Code column and every other supported field.

Related

• Migrating to BatchCard: shared concepts for every migration
• Importing from CSV or XLSX: bring your file into BatchCard