Blog
Delighted shut down: how to move your NPS program without losing your history
A practical migration path when Delighted is gone: what history to preserve, how a full-fidelity CSV import works, and how to keep collecting without a dead archive folder.
If you ran a simple one-question NPS (or CSAT) program in Delighted, the hard part of moving is not picking a new form tool. The hard part is keeping years of scores, comments, and timestamps alive so your trend still means something next quarter. This guide is for teams who need a clean landing place, not a research suite rebuild.
What to preserve from the old program
Before you abandon the export file, decide what "history" means for your team:
- Score and metric type (NPS 0-10 vs CSAT 1-5): mixing scales silently ruins averages
- Comment text: the qualitative trail that explains score moves
- Response timestamps: so trends sit on real collection dates, not import day
- Respondent identifiers you actually use (email or external id), if you segment later
- Any properties you filter on (plan, surface, persona) if they were columns in the export
You do not need every internal Delighted id forever. You do need enough fidelity that last year's dip still appears next to this year's recovery.
Export, then map carefully
Export a CSV from the source system while you still can (or use the last good export you have). Open it and confirm headers for score, comment, time, and type. Common failure mode: importing a CSAT 1-5 column into an NPS survey, or treating the import clock as the response time.
A full-fidelity importer should preview the mapping, refuse silent scale mismatches, and write rows with their original timestamps. In UserVane, the Delighted CSV path is built for that: score, comment, timestamp, and respondent metadata land in live results, not a side archive you never open again.
A migration path that keeps the program simple
- Create a project and choose the metric you actually ran (usually NPS).
- Import the export; preview mapping; commit only when scales and dates look right.
- Confirm historical points show on the trend with original times.
- Ship collection again: in-product widget, hosted link, or bring-your-own email through your ESP.
- Keep the same one-question shape people already understand. Do not invent a 40-question research project unless that is a separate goal.
The point of migration is continuity of the listening program. Complexity is optional later.
What "without losing history" does and does not mean
It means your past responses remain queryable beside new ones, with honest timestamps and comments. It does not mean UserVane is an official continuation of Delighted, or affiliated with Qualtrics. Delighted is a trademark of Qualtrics, LLC; UserVane is independent.
It also does not mean every edge-case property from every custom workflow will magically appear. Bring the columns you care about; verify the preview; treat the import as a deliberate cutover, not a black box.
After cutover: keep the habit, not the vendor nostalgia
Re-establish the moments you survey (post-purchase, post-support, in-app milestones). Reconnect the people who used to read comments every week. If thin samples used to flatter a bad week, prefer a product that suppresses thin samples and shows a margin rather than a naked number. Continuity of habit matters as much as continuity of CSV rows.
Bottom line: export while you can, map scores and timestamps deliberately, import into live trends, and resume a simple one-question program. History should inform the next decision, not sit in a download folder labeled "final_final_delighted.csv."