Delighted Shut Down: What to Do With Your Exported Data

Delighted shut down on June 30, 2026, and the product is no longer available. If you exported your data before access ended, preserve the original files before you clean, combine, or import anything. Before choosing a replacement, make sure the archive remains understandable and recoverable.

If you did not export before the shutdown, the old dashboard instructions no longer apply. Delighted's website now redirects to Qualtrics and states that Delighted is no longer available. Contact Qualtrics directly to ask whether any account-specific recovery option exists, but do not assume that the old dashboard or export workflow can still be accessed.

Quick Answer: What Should You Do With a Delighted Export?

1. Keep an untouched copy of every original CSV or ZIP file.
2. Record which survey, date range, and account produced each file.
3. Check whether response IDs, timestamps, scores, comments, and customer identifiers are present.
4. Document any missing dashboard logic, tags, triggers, or segment definitions.
5. Decide whether to archive the history, rebuild a comparable NPS series, or start a new measurement baseline.
6. Confirm a new tool's actual import support before changing the source files to fit it.

The raw export is evidence. Treat it like source data, not a spreadsheet you can casually edit and overwrite.

Step 1: Preserve the Originals

Create a dated archive folder and place the original files inside it. Do not rename columns, delete rows, change date formats, or combine files in this copy.

A simple structure is enough:

• original/ for untouched Delighted files
• working/ for cleaned or combined copies
• notes/ for a short data dictionary and migration decisions

Store the archive somewhere private with access controls and a backup. Survey exports can contain names, email addresses, user IDs, free-text comments, and other personal data. Do not upload them to a public file converter or an unapproved AI tool.

Step 2: Inventory What You Have

Delighted supported several survey types and export paths, so the exact columns depend on your setup. Check each file rather than assuming every export has the same structure.

Useful fields may include:

Record the row count, earliest timestamp, latest timestamp, and columns present in each file. Those checks make it easier to detect accidental loss later.

Step 3: Document What the Export Does Not Rebuild

A CSV can preserve response-level data without preserving the system around it. You may still be missing:

• dashboard filters and segment definitions
• survey triggers and eligibility rules
• email templates and reminder timing
• tag hierarchy or team conventions
• chart configuration and saved reports
• integrations and downstream workflows

Write down any logic you remember before replacing the tool. A column called plan is useful. Knowing that the old dashboard excluded trials and grouped annual plans separately is more useful.

Step 4: Choose the Right Path

Path A: Archive the history

Choose this when the old survey was occasional, the score is no longer operational, or the data is too incomplete to compare reliably with future results. Keep the original files, document the period they cover, and begin a clearly dated baseline in the new system.

Path B: Preserve a comparable NPS series

Choose this when NPS is an ongoing company metric and the export contains enough information to reproduce the historical calculation. Confirm that the new system can import the relevant scores, timestamps, and identifiers without changing their meaning.

Do not merge old and new charts until you have checked that the survey wording, audience, timing, and scoring rules are comparable.

Path C: Start product-market-fit measurement

Choose this when the next decision is not simply "How satisfied are customers?" but "Which users would genuinely miss this product?"

A Delighted NPS history can provide context, but it is not a product-market-fit baseline. Start the Sean Ellis measurement as a new series and label the first eligible cohort clearly. Keep the old NPS archive separate unless you have a specific, verified reason to join the datasets.

Step 5: Prepare a Working Copy

Only modify copies of the source files.

Typical cleanup tasks include:

1. Standardize timestamps without discarding the original values.
2. Keep stable response and customer identifiers.
3. Separate different survey types before calculating scores.
4. Normalize obvious formatting differences in copied fields.
5. Record every transformation in a short change log.
6. Compare final row counts with the original files.

If a new platform requires different columns, create those columns in the working copy. Do not rewrite the only surviving archive.

Moving From Delighted to FitSignal

FitSignal can be used to begin a new product-market-fit measurement series. Keep your historical Delighted archive intact while you confirm which fields, if any, should move into the new setup.

Do not assume a one-click Delighted import, automatic reconstruction of old dashboards, or a preserved user-level NPS timeline. Those capabilities depend on the actual export format and the current supported product workflow.

For a clean PMF baseline:

1. Define which active users are eligible to answer.
2. Start a new, dated survey cohort.
3. Preserve the original survey wording and scoring method.
4. Keep the Delighted archive as historical context rather than silently mixing unlike measurements.

If You Missed the Export Deadline

The public Delighted site no longer offers the product. If you need to ask about an old account, contact Qualtrics through an official channel and provide only the minimum account information needed to identify it.

Prepare these details before contacting them:

• former Delighted account email
• organization or account name
• approximate subscription end date
• survey types used
• approximate date range of the missing data

Avoid sending survey responses or customer personal data in an initial support request.

Final Checklist

• Original files are stored unchanged.
• A backup exists in a separate controlled location.
• Each file has a survey and date-range note.
• Row counts and timestamps have been checked.
• Missing dashboard and workflow logic is documented.
• Cleanup happens only in working copies.
• The replacement tool's import support has been confirmed.
• Any new PMF measurement starts as a clearly dated baseline.

The shutdown shows why data portability belongs in vendor selection. A usable export, clear identifiers, and documented methodology matter most when the original dashboard is no longer there.

If you are starting a new product-market-fit baseline, try FitSignal free.