What should I verify when migrating project comments and activity history?

Start by defining what “history” means for your team. It may include comments and their authors and dates, attachments, issue or task change records, work logs, and a separate activity feed. Treat each as its own item rather than assuming that a migration labelled “project data” includes everything.

Make an inventory of the records you rely on, why you need them, and where they are now. Then check the exact migration route: source product and version, destination, and migration method. Ask whether each item transfers, which fields or permissions are retained, and how omissions or failures are reported.

For one specific route—Jira Server/Data Center to Jira Cloud with Jira Cloud Migration Assistant—Atlassian lists comments, attachments, issue history, and work logs among migrated issue data, but lists the Activity Stream as not migrated. This applies to that route, not automatically to other products or methods. [S1]

Ask about authorship and dates separately from whether the comment text appears. Check whether the migration preserves the original author identity, creation date and time, and any visibility or security setting that matters to your project. Also clarify what happens if an author account has no equivalent in the destination; don’t assume a displayed name proves identity was preserved.

The answer can depend on the method. For Jira Cloud’s administrator-accessible External System CSV importer, Atlassian says the default import assigns the reporter and current date/time to comments and attachments. Its documented comment format can specify an author account ID and original creation date. That describes this importer, not arbitrary migration tools. [S3]

Before the full move, use a small, representative sample if your chosen method supports a test. Compare the source and destination comment text, author, date, and visibility. Record exceptions rather than treating changed metadata as original.

Separate records that are part of an individual task or issue from a distinct activity feed. A project can appear to have its comments while still lacking a separate stream of events, so verify those categories independently. For anything excluded, ask whether an export or other archive is available, what it contains, and who will retain and be able to consult it under your organization’s process. Don’t label an archive as searchable or complete unless you have checked that.

For Jira Cloud Migration Assistant, Atlassian notes that a history entry referring to a missing link or attachment may not migrate; migrating the referenced item later can update the history entry. Atlassian also directs administrators to downloadable error logs and a post-migration report to identify entities that did or did not migrate. These details apply to that Jira route. [S2]

A simple planning record can expose gaps before they become surprises:

Record type | Needed? | Expected destination behavior | Evidence to check | Archive or owner

Example, as a hypothetical placeholder: Activity feed | Yes | Not included on this route | Confirm against migration report | [archive location or owner]

Use this checklist and mark an item complete only when you have evidence for your chosen migration route:

1. List required record types: comments, authors, dates, attachments, change history, work logs, and any separate activity feed.
2. Confirm expected behavior for each record type with documentation or the migration administrator; note exclusions and limits.
3. Identify records that need a separate archive, plus its location or responsible owner under your organization’s process.
4. Compare a representative set before and after migration, including comment text, author, timestamp, attachment presence, and relevant visibility settings.
5. Review the available migration report and error logs; investigate missing or failed entities and referenced links or attachments.
6. Record unresolved gaps, their impact, and the person responsible for follow-up before treating the history review as done.

Keep the evidence with the migration notes. A report or sample check can help identify problems, but it does not establish that every record transferred unless the evidence actually covers every required record and field.