Skip to main content
Workspace owners on Starter, Growth, or Plus can bring existing product records into Glean Feed from Settings > Import. Each import handles one type of data: feedback requests, roadmap items, or changelog entries. Free workspaces see an option to upgrade instead of the import flow. Imports create records without sending customer emails or notifications.

Before you start

  • You must be the workspace owner.
  • Your workspace must be on Starter or higher.
  • Choose one import type for the file.
  • Keep the file at or below 1 MB and 1,000 data rows.
  • Start from the downloadable template so the column names match.
  • For feedback, create the destination board first. The imported requests use that board’s visibility.
  • For changelog tags, create each tag in Glean Feed before referring to it in the CSV.

1. Choose what to import

Open Settings > Import, select Start import, then choose Feedback requests, Roadmap items, or Changelog entries. For feedback, also choose:
  • The destination board.
  • Whether requests with a blank workflow status should start as Approved or Pending review.

2. Prepare the file

Download the template for the selected import type and replace its example rows with your data. Keep the header row unchanged. Only title is required; the column reference explains the optional fields. Use source_id when your previous system provides a stable record ID. Glean Feed uses it to catch a record that was already imported. Duplicate source_id values within the file also block the import.

3. Preview the import

Upload the CSV and select Preview. Preview checks the file without creating records and reports:
  • Source rows checked.
  • Records that will be created.
  • Blocking errors, including invalid values and duplicate rows.
  • Warnings about source details that Glean Feed stores for reference but does not reproduce as product behavior.
Correct every error in the CSV, upload the corrected file, and preview it again. Warnings do not block the import, but review them before continuing.

4. Confirm and review

When preview shows no errors, confirm the import. A completion message reports how many records were created. Open the matching area—Feedback, Roadmap, or Changelog—and check a few imported records. Confirm their titles, workflow stage, visibility, dates, and links before importing the next file.
For a large migration, import a small representative file first. Check the result in the dashboard, then continue in batches of no more than 1,000 rows.

Fix a failed preview

Column reference

Custom header names are not mapped. Use the headers from the downloaded template.

Workflow mapping reference

Feedback

If status is blank, the row uses the Initial request status selected in the import flow. Rows imported as planned, in_progress, completed, or closed also create a linked roadmap item. Closed requests remain dashboard-only.

Roadmap

If status is blank, the item starts as planned. Supported values are planned, in_progress, done, and closed.

Changelog

Changelog uses state, not status. If state is blank, the entry is imported as published. Use draft when the entry should not appear to customers yet.