What evidence would help you investigate whether an export preserves usable meaning?
An export button does not guarantee that another system can use the result. Decide whether a product's portability claim supports moving a public project archive into a new workspace. Focus on relationships, timestamps and attachments rather than file availability alone, and avoid calling a successful download a complete migration without checking semantic preservation.
Review this product archive export for preserved identifiers, relationships, timestamps and attachments, separating download success from migration readiness.Set the task boundary
List the archive elements required for the destination task: records, identifiers, links, comments and attachments. Include public export examples showing actual files or documented schemas. Exclude screenshots of a download button as fidelity evidence. Record the product version and export mode, since summary reports and complete archives may intentionally preserve different fields.
Trace the evidence
Compare visible source records with the exported representation. Identify time zones, multiline text, encoding and stable identifiers. A count match does not prove field meaning survived. Inspect public documentation rather than opening untrusted executable attachments, and keep any transformations described by a reviewer separate from the native export the product itself provides.
Check alternative explanations
Look for destination-side examples with linked records and attachments intact. Distinguish import limitations from missing export fields. When a user reports lost data, preserve the exact affected element rather than labeling the entire format broken. Counts should describe only inspected rows, and inaccessible files should remain unverified rather than reconstructed from screenshots.
Prepare the decision
Deliver a field-mapping checklist and an unresolved portability list. If no paired source-and-export example exists, recommend an authorized disposable archive test before migration. Do not delete the original workspace, promise lossless transfer or infer success from the presence of a CSV file that omits relationships essential to the intended follow-up work.
Keep the boundaries clear.
- Keep data export fidelity conclusions within the inspected examples, not a population estimate.
- Badges show context for data export fidelity research; availability still needs checking.
Start with a read-only check: ask your agent to report actual source coverage before collecting records or exporting an audience.
Primary references
Documentation reviewed 2026-11-13. Product capabilities, client availability and plans can change. Third-party marks identify their products, not an affiliation.