# Preserve the created-at timeline on imported feedback

> Map the original created-at timestamp when importing historical notes so support and product teams read the feedback in the right order later.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/preserve-created-at-timeline-on-imported-feedback/
- Source: [productlane.com](https://productlane.com/docs/get-started/import)
- GrowthDex source hub: [Productlane Docs](/sources/productlane-docs-productlane-com/)
- Last checked: 2026-05-27
- Rarity: uncommon
- Budget: free
- Channels: Support, Analytics, Operations
- Stages: migration, signal quality, historical data, support-led growth


## Why this can grow

A support archive loses a lot of meaning if every imported record looks new. Keeping the original created-at time preserves the timeline of demand, makes follow-up easier, and stops the inbox from confusing old evidence with fresh pain. It also gives later reporting a cleaner view of when a pattern actually started instead of when the migration happened.

## Ian's take

From scaling consumer platforms across MENA and Southeast Asia, my default is to distrust growth work that only looks good in a slide. My bias is to treat this as a small market test first. Make the audience narrow, make the promise concrete, and let the first real response decide whether it deserves more work. I would run it small enough to learn quickly, then only scale the parts that real users repeat, save, reply to, or buy from. For this tactic, I would watch one clear growth signal before putting more time or budget behind it.

## Action plan

1. Define one narrow startup segment where preserve the created-at timeline on imported feedback can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Support and Analytics channel.
3. Use the evidence from productlane.com to set the first version of the message, format, and audience.
4. Launch a small test for 7 to 14 days with one success metric: one measurable growth signal.
5. Review the result, keep the winning message, remove weak variants, and turn the learning into a repeatable growth playbook.

## Source-backed example

Productlane's CSV import asks teams to map the original createdAt column so imported notes keep their timeline instead of inheriting the migration date.

## Adjacent tactics in the same lane

- [Dry-run validation before support-data import](/growth-ideas/dry-run-validation-before-support-data-import/) - same source, 2 shared channels, 2 shared stages
- [Remap or skip custom fields during changelog import](/growth-ideas/remap-or-skip-custom-fields-during-changelog-import/) - same source, 1 shared channel, 1 shared stage
- [Docs live only after first published article](/growth-ideas/docs-live-only-after-first-published-article/) - same source, 1 shared channel, 1 shared stage
- [AI chat weekly doc-gap report](/growth-ideas/ai-chat-weekly-doc-gap-report/) - same source, 1 shared channel, 1 shared stage

## Read GrowthDex essays

Browse the plain-English essay index at [GrowthDex Blog](/blog/).

## Related GrowthDex essays

- [The support surface should answer and remember](/blog/the-support-surface-should-answer-and-remember/) - support-led growth, brand trust, documentation

## Advisory

If you want help turning this into a working growth system, Ian Goh offers advisory at https://iangoh.com/advisory.