How to get there: Go to Settings → Import & export.
Bulk-import posts into ProductLift from a CSV or Excel file. The wizard auto-detects your columns with AI, lets you create missing statuses and categories on the fly, and tracks every import as a batch so you can find and review its posts later.

.csv).xlsx, .xls).tsv, .txt)The first step of the wizard has direct download links for an Excel Template and a CSV Template with all supported columns pre-filled.
The import accepts:
You don't have to use all of them. The mapping step lets you ignore any column.
You don't have to rename headers in your file. AI maps your column names to ProductLift fields automatically and suggests a mapping you can adjust before continuing.
alice@example.com;bob@example.com). Each email becomes a voter on the post. Use semicolons because commas appear inside email lists in many exports.YYYY-MM-DD or YYYY-MM-DD HH:MM:SS.23, not 23 votes).title,description,status,category,tags,author_email,created_at,votes
"Add dark mode support","Users want a dark theme option.","Under Review","UI/UX","ui,design","customer@example.com","2026-01-10",47
"Export reports to PDF","Export analytics as PDF.","Planned","Reporting","export,pdf","admin@example.com","2026-01-12",23
"Slack integration","Notify Slack on status changes.","New","Integrations","slack","john@customer.com","2026-01-15",15
The import wizard has three steps: upload, mapping and preview.
The Excel/CSV templates are available as download buttons on this same screen, plus a Show supported fields toggle that lists every column the importer recognizes.
ProductLift uses AI to suggest how each of your columns maps to a ProductLift field. The mapping table shows:
Adjust any mapping you don't like, then click Continue to Preview. Title is required; other fields are optional.
The preview screen shows:
If your file references categories or statuses that don't exist yet, panels appear above the preview:
Statuses you create here are auto-attached to the board you picked in Step 1, so the imported posts have somewhere to live.
Click Execute Import when the preview looks right. The job runs in the background and stamps every imported post with an import_batch identifier so you can find them all later.
When it finishes, you'll see a View Imported Posts link that takes you to All Posts filtered by the import batch. From there you can:
YYYY-MM-DD in the source.23 votes -> 23).For large migrations, import the first 5-10 rows as a separate test file first. Open a few of the imported posts to make sure dates, authors, statuses, and tags look right. If anything is wrong, fix the source file. Remove the test posts before importing the complete file to avoid creating duplicates.
If you want to start over after a test, use View Imported Posts to open that batch, check the selected records and bulk-delete the test posts before importing the complete file.
For exports from another feedback tool, Jira or Trello, follow the migration guide. It explains which data transfers through the import and what needs a separate step.
For automated, ongoing, or very large imports (tens of thousands of posts) you can skip the wizard and use the API directly. See:
Map an assignment column to Assigned To (Email). Use the email address of an existing admin in this workspace. Headers such as “Assigned to”, “Assigned” and “Owner” are still recognised.
The import does not create a new user for an assignment. If the email does not match an existing admin, the preview shows a warning and the post will be imported without that person assigned. Add or invite the admin first, then check the preview again. Author and voter email columns have their own rules.