Delighted shuts down on June 30, 2026. If you do not export your data before then, your entire NPS history, every response, every comment, every trend line, is gone. This is the step-by-step walkthrough: how to export the CSV, what is inside it, what is missing, and what to do with the file once you have it.

Do not leave this for June. The Delighted UI will get slow as everyone tries to export at once, and if anything goes wrong you want time to fix it. Export by June 15 at the latest. Earlier is better.

Quick Answer: How Do You Export Data From Delighted?

Log in to Delighted, open the survey you want to export, click Reports → Export, choose the date range (pick "All time" to get the full history), select CSV, and download the file. Repeat for every active survey. The export contains all responses, comments, scores, user IDs, and timestamps. It does not contain your segmentation logic, email templates, or trigger rules. Those have to be rebuilt in your new tool.

Why This Is Urgent

Delighted's shutdown notice confirms June 30, 2026 as the final day. After that, the dashboard goes dark. There is no grace period. There is no "export later, we'll keep your data warm" option.

A few things founders keep underestimating:

Your NPS score changes meaning once you lose the history. A 42 today is only useful because you can compare it to a 38 from six months ago.
Open-ended comments are where the real signal lives. Those disappear too.
If you have cohort analysis or segment-level NPS, that reporting logic lives inside Delighted's UI. The CSV gives you raw data, not the rebuilt dashboard.

The good news: the export itself is painless. The follow-up (deciding what to do with the CSV) is where most teams get stuck. I will cover both.

Step 1: Export Your Responses

For each survey you want to keep:

Click the survey name to open it.
In the top navigation, click Reports.
Look for the Export button (top right, usually next to the date range selector).
Select your date range. Pick All time unless you have a specific reason to slice it.
Choose CSV as the format.
Click Export and wait for the email with the download link, or download directly if the file is small.

Large accounts (>50,000 responses) may get the export as a ZIP file split into multiple CSVs. Keep all of them. They are numbered sequentially.

Tip: Delighted's export sometimes times out on accounts with >100,000 responses. If that happens, export in chunks: one year at a time, then stitch the CSVs together locally.

Step 2: Understand What Is in the CSV

Open the file in a spreadsheet. You should see columns like these:

Column	What it contains
`Response ID`	Unique identifier for each response
`Person ID` or `Email`	The user who answered (depends on your setup)
`Score`	0–10 for NPS, 1–5 for CSAT, etc.
`Comment`	Open-ended response text
`Timestamp`	When they responded (UTC)
`Platform`	Email, web, SMS, link
`Tags`	Any tags you or your team applied
`Properties`	Custom properties you passed in (plan type, signup date, etc.)

This is the full response-level data. Everything a user actually said or scored is here.

Step 3: Understand What Is NOT in the CSV

This is where most teams get surprised. The CSV contains responses, but it does not contain:

Your segmentation logic. If you had dashboards showing "NPS by plan tier" or "NPS for users >90 days old," those filters live in Delighted's UI. You get the raw properties, but you have to rebuild the segments in whatever tool comes next.
Your email templates. The subject lines, body copy, and send-timing rules do not export.
Your trigger rules. "Send a survey 14 days after signup, never more than once per quarter." That logic is gone.
Your team's tag taxonomy. The tags you applied to responses come through as plain text in a column. The hierarchy and color coding do not.
Trend charts and screenshots. If you want the actual visual graph of NPS over time, screenshot it before June 30. The CSV gives you the data, not the rendered chart.

None of this is a dealbreaker. But it does mean a straight CSV export is about 60% of the work. The other 40% is rebuilding the segmentation and send logic in your new tool.

Step 4: Export Your People List Separately

Most teams forget this. Your people list (everyone who has ever been surveyed, along with their properties) lives in a separate export.

Go to People → Export and download the full list. This CSV has:

Every email or user ID you ever surveyed
Custom properties attached to each person
Last survey date
Current NPS segment (promoter / passive / detractor) if calculated

Why it matters: if you plan to re-survey these users in your new tool, you need the list. Otherwise you are starting from scratch.

Step 5: Export Any Custom Reports and Screenshots

If you built custom reports or dashboards inside Delighted, especially anything your team or investors looked at regularly, screenshot them.

Specifically:

The overall NPS trend chart (month-over-month)
Any segment breakdowns you use in board decks
Comment clouds or themed comment reports
Tag distribution reports

Save these as PNGs in a dated folder. Future you will thank present you. I have seen more than one founder rebuild an entire investor update because they lost the one chart they always showed.

Step 6: Decide What the CSV Becomes Next

You now have the raw data. Three realistic paths:

Path A: Keep Measuring NPS (Different Tool)

If NPS is the number you actually care about, pick an NPS-native replacement. SatisMeter and Refiner.io are the closest equivalents. Both will let you import a historical CSV to preserve the trend line, though the import process varies by tool.

This is the lowest-friction option if your current setup works fine and you just need a new home for it.

Path B: Switch to PMF Measurement

If you are an indie developer or early-stage founder, NPS was probably never the right metric for you anyway. NPS tells you how users feel about you today. It does not tell you whether you have product-market fit.

The Sean Ellis 40% test measures something different: how many users would be "very disappointed" if your product disappeared. That is the signal you need at the pre-PMF or early-PMF stage. NPS becomes useful later, once you are trying to optimize a product that already has fit.

FitSignal was built for this transition. You can use your Delighted CSV as a baseline: the response timestamps and user IDs map directly onto FitSignal's user timeline, and the open-ended comments carry over as context. Once the historical data is in, you start sending the Sean Ellis survey to the same users and begin building a PMF trend line alongside the NPS history.

Path C: Archive and Move On

If the Delighted data was informational rather than operational (you ran a survey, acted on it, and the score is not a number you track week to week), just archive the CSV somewhere safe (Google Drive, a private S3 bucket, wherever) and start fresh in whatever tool you pick next.

No shame in this. Not every team needs a continuous NPS time series. Plenty of products are better off measuring the thing that actually predicts retention, which for early-stage SaaS is usually not NPS.

How to Import Your Delighted CSV Into FitSignal

FitSignal does not have a one-click "Import from Delighted" button yet. But the manual process takes about 15 minutes and preserves everything that matters. Here is the walkthrough.

1. Clean the CSV. Open the Delighted responses export in a spreadsheet. Keep these columns, delete the rest:

Person ID (or email)
Score
Comment
Timestamp
Any custom properties you segmented by (plan, signup date, etc.)

2. Sign up for FitSignal. Create your project at fitsignal.com. The free tier handles 250 survey sends per month, which is plenty for running PMF measurement alongside an existing NPS history.

3. Upload your people list. In FitSignal, go to People → Import CSV and upload the Delighted people export. Map the columns (email, name, custom properties) to FitSignal fields.

4. Upload historical responses as context. FitSignal stores historical survey data as context attached to each user. Go to Survey → Import History → NPS and upload the cleaned responses CSV. This gives you the NPS timeline preserved on each user's profile. It does not become your active PMF score (that comes from the new survey), but it does mean you can see which current NPS promoters are also PMF-very-disappointed (huge signal) and which NPS detractors somehow became PMF-very-disappointed (rare, but extremely informative).

5. Launch the Sean Ellis survey. In FitSignal, go to Surveys → New → PMF (Sean Ellis). Select your imported people list as the audience. Send.

6. Watch both numbers. Your NPS history sits alongside your new PMF score. Over the next 4–8 weeks you will start building the PMF trend line that actually tells you whether you have fit, while the NPS history gives context on how that maps to customer feelings.

Total setup time: about 20 minutes, including coffee.

Common Export Problems (and Fixes)

"My export is empty or only has a few rows." You are probably looking at a single page of recent responses. Make sure you selected All time as the date range before clicking export.

"The CSV is huge and Excel can't open it." Excel caps at ~1M rows. If you have more responses, open the file in Google Sheets (handles more, slower) or use Numbers, or just read it with a command-line tool like csvlook from csvkit. Better yet, import it directly into your new tool without ever opening it in a spreadsheet.

"The custom properties column is a JSON blob." Delighted stores custom properties as a JSON string in one column. If you want them as separate columns, run the CSV through a small Python script or a tool like csvjson. Most modern import tools (including FitSignal's) can parse JSON properties on the way in.

"My team's tags do not match anything in my new tool." Tags come through as plain text. You will have to manually recreate the tag taxonomy in your new tool. Start with your top 10 tags by volume. That usually covers 80% of the responses.

"The export email never arrived." Check spam. If still nothing, try exporting a smaller date range (one year instead of all time) to see if the export is timing out silently. Contact Delighted support if that fails. They are still responding through June.

Do This By June 15, Not June 30

Two weeks of buffer is not paranoia. Two weeks of buffer is the difference between a smooth migration and finding out on June 29 that one of your CSVs is corrupt and there is no one left at Delighted to fix it.

Put June 15, 2026 in your calendar right now. Block two hours. Export everything. Verify the files open and contain the data you expect. Stash them somewhere you will not lose them.

Then, and only then, start thinking about what tool replaces Delighted. Do not try to do the migration and the tool selection in the same session. You will get the migration wrong.

Best For / Not Best For

This guide is best for: Delighted users with active surveys, historical data they want to preserve, and under 100,000 total responses. Also works for teams considering a switch from NPS-only measurement to PMF measurement.

This guide is not best for: Enterprise Qualtrics users (different platform, different export process), teams using Delighted only as a CSAT tool with no intention of continuing measurement elsewhere (just archive the CSV), or teams with >500K responses (contact Delighted support directly for bulk export assistance).

Next Steps

Block two hours on your calendar before June 15, 2026.
Export responses, people list, and screenshot your dashboards.
Pick your next tool: NPS replacement, PMF replacement, or archive.
If you are moving to PMF measurement, try FitSignal free. Import your Delighted CSV, launch the Sean Ellis survey, and start building your PMF baseline in about 20 minutes.

Do not wait until June 29 to think about any of this. The Delighted shutdown is one of the cleaner vendor sunsets in recent SaaS history, but it is still a hard deadline. Export early, move deliberately, and you will come out with more data than you started with, just in a tool that actually fits where you are now.