Backdating Posts

Backdating posts

When you import or migrate feedback, you usually want posts to keep their original creation date so the historical sequence is preserved.

Backdating during import

The standard importer accepts a Created Date column. The importer uses that value instead of the import timestamp.

  1. Add a Created or Created Date column to your CSV.
  2. Use a date format the importer recognizes (ISO 8601 like 2025-10-12 works reliably).
  3. On the Map Your Columns step, the importer auto-detects the column and maps it.
  4. Import.

After import, the post appears as if it had been created on that historical date, chronological ordering, age-based filters, and roadmap timelines all reflect the original date.

See Importing feedback posts for the full importer flow.

Backdating a single post manually

The standard post create form uses today's date. To change a post's creation date after the fact:

  • Use the ProductLift API and set the created_at field.
  • Or open the post in admin and edit the date field if exposed in your sidebar configuration.

Why backdate?

  • Migrating from another tool and preserving the chronological order.
  • Logging a feature request you received months ago via email.
  • Reconstructing customer demand history for prioritization.

Backdating votes too

If you also want votes to reflect their original cast date (not the import date):

  • Use the API to set vote created_at per voter.
  • For bulk migrations, this is the kind of detail our migration concierge service handles. See the migration guides under Migrations.