Scores, comments, dates, people, accounts — and every custom property you were passing, because that order number is often the only join back to your ERP.
For orphaned Delighted and GetFeedback customers
Delighted is gone. GetFeedback is next.
Neither of them failed for lack of customers. Understanding why they died is the fastest way to work out where to go — and what to check before you sign anything.
The pattern
Three shutdowns in twenty-four months, all the same shape.
| Tool | Acquired by | What happened | Date |
|---|---|---|---|
| Delighted | Qualtrics (Silver Lake) | Shut down, customer data deleted | 30 Jun 2026 |
| GetFeedback Direct | SurveyMonkey (STG) | Sunsets | 31 Dec 2026 |
| Promoter.io | Medallia | Wound down, no announcement | — |
| Wootric | InMoment | Running, no roadmap | — |
An independent tool gets acquired by an enterprise parent. The parent goes private. The low-margin product line gets cut to improve the leverage metrics. It has now happened three times to the same category, and the customers were never the problem.
What to check before you sign anything
The question worth asking your next vendor.
Not "what are your features". Ask: who owns you, and what happens to my data if this product stops being strategic for them?
Delighted's customers got about twelve months' notice and lost their history. If that answer makes you uncomfortable, it should — and it should make you uncomfortable about us too, so here is ours in plain terms.
Avota's answer
We're owned by Web Pros, a small independent company with no investors and no acquirer. Nobody can decide our margins aren't good enough for a portfolio.
Export is available at any time, on every plan, including a lapsed one. If you stop paying we stop sending — we don't delete anything, ever. That isn't a promise about our intentions; it's the only arrangement that makes the question moot.
Bringing your history
Your trend line shouldn't start at zero.
If you exported from Delighted before it went dark — or you're exporting from GetFeedback now, which you should do today rather than in December — Avota reads it.
There's no single format to hand you, because Delighted's export included a column for every custom property you'd ever passed it, so every file is a different shape. Its documentation is already offline. So Avota reads what it finds, shows you exactly what it understood, and asks rather than guessing when two columns could be the same thing.
Your unsubscribes. Anyone who opted out of Delighted is suppressed in Avota before a single message goes out, including from rows we otherwise reject.
Your history never triggers a send. A four-year backfill would otherwise email thousands of people about orders from 2022 on your first day.
The mapping, the row count, every rejected row with a reason, and your own historical score — so you can confirm the number survived the move before anything is written.
Upload it twice if you like
Imports are idempotent. Re-uploading the same file adds nothing, and duplicate rows inside one file collapse. Nobody should have to be careful with a migration.
The part that's actually different
Don't replace Delighted. Replace what Delighted couldn't do.
Delighted was good at sending surveys. It had no idea what was happening in your business, so you had to tell it — a CSV, a Zapier recipe, a tag on an email thread.
Avota starts from the other end. It reads your system of record, so it knows an order closed, an invoice cleared, a quote was lost — and it knows what the account is worth and who owns it. That changes what's possible downstream:
- Scores weighted by revenue, because your largest account probably isn't a rounding error and shouldn't count as one vote.
- Detractors routed automatically to the rep who owns the account — no assignment rules to configure, the ERP already knows.
- Loops that have to be closed with a written outcome, then re-checked after sixty days to see whether the fix held.
- Nothing installed in your ERP. Read-only, over an integration your admin can revoke in a click.