Restoring a Delighted archive
Delighted shut down on June 30, 2026, and the customer data went with it — the product, the API and the help documentation are all gone. What survives is whatever CSV you downloaded before the lights went out. Firsthand reads those archives: the scores, the verbatim comments, and the dates people actually gave them.
Read this part first
This one is different from the others.
The other three importers move a live account. This one recovers a dead one, and that changes what's possible. Being straight about the limits matters more here than anywhere else on this site.
Most Delighted archives can't be joined to orders
Delighted was a standalone feedback tool rather than a Shopify app. Unless you configured it to pass an order id or order number through as a custom property, its export carries an email address and a timestamp — and nothing that ties a response to a specific order.
Firsthand will not guess. Those responses import as standalone history: fully readable, correctly dated, searchable, and charted in the months they belong to — but not connected to order values, and not part of the Attribution Reality Check, which needs a real order to compare against. If your archive does carry an order column, Firsthand finds it even when it's buried under a custom property name, and those rows join properly.
How to do it
Three steps.
-
Find your archive
Check downloads folders, shared drives and any scheduled export that was mailing you a CSV. There is no way to request a fresh one — Delighted's export button no longer exists, and neither does the data behind it.
-
Upload it unchanged
Surveys → Import → Delighted (archive) → choose the file. Delighted archives vary by account and era, so Firsthand reads the headers rather than expecting a fixed layout.
-
Review the draft it creates
A Delighted response is a score plus an optional comment, so the import becomes exactly two questions: the score, and the follow-up comment. Rename either one on the draft if your survey asked it differently.
Specifics
What Firsthand does with the file.
Comes across
- Every score, with the 0–10 NPS scale preserved as a scale
- A 1–5 CSAT or star rating recognized as its own thing rather than mislabeled NPS — Firsthand infers which from the scores actually present in the file
- Verbatim comments, kept in full as text answers
- The original response date, so a 2024 answer charts in 2024
- An order id or number when a custom property carries one, even under an unexpected column name
Doesn't
- Names and email addresses. Delighted's export leads with both. Firsthand reads neither into the database — they're identified at parse purely so they can be dropped.
- Permalinks and platform metadata. They point at a service that no longer exists.
- Custom properties. Beyond order ids, these are customer metadata rather than survey answers, and turning columns like "Plan" or "Country" into fake survey questions would be worse than leaving them out.
- Order joins, usually. See the note above — this is the real limitation, and it's a property of the archive, not of the importer.
Why bother
A dead vendor's CSV is still your data.
There's a reasonable case for writing off an archive from a shut-down service. But NPS is only meaningful as a trend, and a score with no history behind it is just a number. If you have two years of Delighted responses sitting in a folder, importing them means your first month on Firsthand starts with a baseline instead of a blank chart.
It's also the clearest argument for the way Firsthand handles exports in general: everything here is exportable on every plan, forever, including after you cancel. The reason that matters is sitting in your downloads folder right now.
Not sure your archive is usable?
Delighted exports varied a lot between accounts. Send yours over and we'll tell you what's recoverable — how many responses, whether the scores read as NPS or CSAT, and whether anything in it can join to your orders.