For the complete documentation index, see llms.txt. This page is also available as Markdown.

Migrating from another loyalty app

Plan: Bulk import is available on the Pro plan and above. If the Bulk Import page shows Upgrade Required, your plan doesn't include it.

Moving from another loyalty app means carrying your customers' balances with you. The path: export balances from the old app, reshape them into DollarBack's CSV format, import with notifications off, then spot-check before you announce anything.

If you'd rather start customers with credit calculated from their actual order history under your new rules, instead of carrying over old balances, see Backfill cashback for past orders. Backfill is available on the Enterprise plan only.

Prerequisites

  • A plan that includes bulk import (Choose a plan and start your trial)

  • Balance export access in your old loyalty app

  • Not a development store (bulk import is blocked on development stores)

Step 1: Export balances from the old app

Most loyalty apps offer a CSV export of customer balances (sometimes called points, credits, or wallet balances). Export it last thing before switching. Any earning that happens in the old app after the export won't carry over.

Step 2: Map the columns

Reshape the export into DollarBack's format. Required headers:

Column
Required
Notes

Amount

Yes

Positive number, in currency (convert points first). Quoted values and thousand separators like "8,260.90" are handled.

Currency

Yes

e.g. USD

Email or CustomerId

At least one

CustomerId (the Shopify customer ID) is tried first. If it finds no customer, the import tries the row's Email. Email must match the customer's email in Shopify.

ExpiryDays

No

Whole days until that row's credit expires. Leave blank to use the Credit expires setting for the whole file, or 0 to never expire.

ExpiresAt

No

An exact expiry date for that row, for example 2026-12-31 (end of that day, in your store's timezone) or 2026-12-31 18:00. It overrides ExpiryDays. A value that isn't a date rejects the whole file.

Use ExpiryDays or ExpiresAt to carry over each customer's remaining expiry from the old app.

Keep the file under 5 MB; split large migrations into multiple files if needed.

Step 3: Import with notifications off

  1. Open DollarBack admin β†’ Home and, in the Quick links card, click Open next to Bulk import ("Bulk credit or debit customers by uploading a CSV file").

  2. Set Action Type to Credit.

  3. Set Credit expires: Never keeps migrated credit forever. Choose After a number of days or On a date if you want migrated balances to expire. An ExpiresAt or ExpiryDays column in the CSV overrides this per row.

  4. Turn Notify Customers off. A migration shouldn't blast every customer with a "you just earned credit" email. Announce the switch on your own schedule instead.

  5. Optionally turn Send to Integrations off too, so the import doesn't trigger Klaviyo/Omnisend/Flow events for every row.

  6. Upload the CSV and click Import CSV.

  7. Watch the job move from pending β†’ processing β†’ completed. Rows commit in small batches; stopping a job keeps everything already processed.

Two DollarBack home page cards. Plan and usage shows the current plan with a Manage link and the orders this period with a View link. Quick links shows Bulk import and Backfill past orders, each with an Open link.
Bulk import has no item in the DollarBack menu. Open it from the Quick links card on the home page.
The Upload CSV File card on the Bulk Import page: Action Type set to Credit, Credit expires set to Never, the Notify Customers, Send to Integrations and B2B Mode switches all off, a Reason field, and the Download Sample CSV and Choose CSV File buttons.
For a migration, credit the balances with Notify Customers and Send to Integrations both off.

Rows where neither the CustomerId nor the Email finds a customer log "Customer not found" and the job continues; those rows are skipped, not fatal. Full field-by-field details are in Bulk import credit (CSV).

Step 4: Spot-check balances

  1. Download the job's log. It lists every row with customer ID, email, action, amount, currency, status, and message.

  2. Filter for anything that isn't a success. "Customer not found" rows usually mean the customer hasn't been migrated into Shopify yet, or the email differs. Fix and re-import only those rows.

  3. Pick five to ten known customers and compare their DollarBack balance against the old app's export: check DollarBack admin β†’ Analytics β†’ Activity β†’ Credits earned, or sign in to the storefront as a test customer and open the widget.

  4. Confirm the totals in Analytics β†’ Activity β†’ Credits earned, which lists imported credit. The Overview cards leave bulk imports out, so they won't match your CSV total.

Verify it works

Place a test order with a migrated customer account: at checkout, store credit appears as a payment option with the migrated balance available to spend.

Common issues

  • The job failed or many rows errored β†’ My bulk import failed

  • "Customer not found" on rows you expected to work: the customer doesn't exist in Shopify yet, or the email doesn't match; import customers into Shopify first.

  • A customer was credited twice: duplicate rows in the CSV; use Action Type: Debit with a correction file to remove the excess.

  • Balances imported but not offered at checkout β†’ Store credit isn't available at checkout

Last updated