Bring your SpringBig data with you and keep your options
Your customer list is the most valuable asset your marketing owns, and right now it lives behind a message-credit meter. This page is the exit ramp: import your SpringBig contacts and loyalty data, run our email alongside your SpringBig program, and if the numbers convince you, complete the switch in about two hours of setup work.
Exactly what comes over, and from where
Straight talk first: there is no native SpringBig API connector, and you don't need one. SpringBig lets you export your data and our importer does the rest. Your POS becomes the source of truth for what customers actually buy, not SpringBig.
| Data stream | What flows | Cadence | Powers |
|---|---|---|---|
| Contacts | Your SpringBig customer export: email, name, phone. The importer is header-flexible, so whatever column layout the export gives you maps cleanly. | Imported during onboarding (minutes, not weeks) | Day-one sending, plain-language segments |
| Consent state | Opt-in status travels with the import; opted-out contacts land straight in the suppression list and are never mailed. | At import, then enforced on every send | A clean start that keeps your compliance history intact |
| Purchase history | Comes from your POS, not from SpringBig. Our Treez feed syncs completed tickets nightly, and Dispense supplies the live catalog and offers. | Nightly POS sync, in your store’s timezone | Purchase-rule segments, win-back detection, POS revenue attribution |
| Loyalty balances | Point balances live inside SpringBig’s system. Export them alongside your contacts and we review them with you during onboarding to set a starting position your customers will recognize. | White-glove onboarding step | A loyalty program you own, with wallet cards on top |
Consent is the non-negotiable: opt-outs from your SpringBig program are honored from the first import forward, enforced at send time on every send. Signup consent records (IP, timestamp) are kept for everyone who joins from here on.
Run it side by side first
You don't have to cancel anything to start. Keep SpringBig running your texts and points exactly as today, and move just the email onto our stack: campaigns generated from your POS data, sent from dedicated IPs your store doesn't share, with register-verified revenue per campaign on supported POS integrations (Treez today). Same customers, two senders, one month. Then compare the invoices and the numbers.
We're honest about the split: we are an email-first platform and we do not sell SMS today. That's deliberate, not an oversight. If texting stays in your mix, SpringBig (or any SMS vendor) can keep that lane while your email moves somewhere built for it: no per-message meter, no carrier filtering.
The two-hour switch, spelled out
When you're ready to move fully, this is the clock. The switch-from-SpringBig guide covers the same timeline in detail.
- 0:00
Export from SpringBig, connect your POS
Your contact list is your data. Export it from your SpringBig dashboard, or request it from your rep. Meanwhile your POS connects with an API key.
- 0:30
Contacts imported, suppression honored
The header-flexible importer maps the file, dedupes, and routes opt-outs to the suppression list. No opted-out contact will ever be mailed.
- 1:00
Dedicated IPs and domain auth configured
Two dedicated IPs for your store, DKIM and reverse-DNS automated, warm-up governor armed with automatic safety pauses.
- 1:30
First ready-to-send campaign appears
Drafted from your POS catalog and offers, with products, photos, prices, menu deep links, and a visible “why this email” reason.
- 2:00
You press send
Then the honest second act: over roughly two weeks, the warm-up governor shifts volume engagement-first onto your dedicated IPs. Sending reputation is earned, not declared.
Questions worth asking any loyalty vendor
Before signing a multi-year contract with anyone (including us), ask about financial stability, and ask what happens to your data and your customers' wallet passes if the vendor restructures. For SpringBig specifically, the public filings are worth reading: the company trades OTC Pink (formerly Nasdaq), its annual report carries going-concern language, noteholders issued a Notice of Default in April 2026, and a July 13, 2026 reorganization agreement extinguished roughly $12.5M of senior secured notes. Retail client count was reported at 744, down from 900 a year earlier. In fairness: management points to cost controls and positive adjusted EBITDA in recent quarters, and every one of these facts comes from filings and press coverage, not from us.
We're not predicting anyone's future. We're saying your list shouldn't depend on it. Our answer to the same question: your contacts, consent records, campaign history, and images are exportable at any time, and the import path you used to arrive works just as well in reverse. The full SpringBig comparison lays out the product side.
Why not just import that CSV into Mailchimp?
You could. The export is yours. But Klaviyo merely tolerates cannabis email (and bans cannabis SMS), Mailchimp enforcement is unpredictable, and both put you on shared IPs whose reputation you inherit. More practically, a generic ESP treats your list as a blank canvas: no POS feed, no product photos with prices and menu links, no purchase segments, no register-verified revenue. Our platform drafts the campaigns from your store's own data and sends them on dedicated IPs approved with full cannabis disclosure, infrastructure that agreed, in writing, to serve this industry.
Frequently asked questions
Bring a SpringBig export to the demo
Book a demo and we'll run your actual export through the importer. You'll see your list land, your segments form, and your first POS-drafted campaign, live.