Migrating from Delighted

UserVane supports CSV import of historical Delighted (and similar) exports so trends and verbatims are not stranded when you cut over.

What ships

• Dashboard Import flow that accepts a CSV export.
• Auto-detection of common Delighted column headers (score/rating, comment, timestamp, email, name, survey type, plus metadata columns).
• Mapped rows land as imported source responses (distinct from live measured responses).
• Imported identity uses email hashed server-side to an imp_… respondent id for privacy export/erase by email.

Exact header names vary by Delighted export generation. The importer matches aliases (for example score, nps score, comment, created at, email) rather than requiring one frozen header row.

Suggested cutover

1. Export your Delighted history as CSV.
2. In UserVane, create the destination survey(s) (type should match: NPS vs CSAT, etc.).
3. Open Import, upload the CSV, confirm column mapping, run the import.
4. Install @uservane/browser or @uservane/react with your publishable key; replace the Delighted embed.
5. Keep Delighted read-only until you trust live traffic, then cancel.

After import

• Imported rows participate in results views as historical data (source labeled imported).
• DSAR erase by email covers imported identity (DELETE /v1/privacy/erase?email=… with the secret key).
• Live SDK respondents use userId as respondentId on privacy routes.

What import is not

• It does not re-fire Delighted webhooks or email campaigns.
• It does not invent correlation for agent-native Langfuse sessions.
• Column mapping still needs a human check when headers are custom.

Privacy selectors: Privacy guide.