Export and Import Feedback

Outcome

You will know when export or import is the right tool, and you will be able to use either one without corrupting the queue or losing environment context. Export and import are not part of normal triage; they exist for handoffs, checkpoints, and consolidation, and they are most useful when used sparingly.

Data formats

The exact file format used for export and import depends on your TMXIO version. The general guidance on this page applies regardless of format, but check the in-product export dialog for the specific options available to you.

When to Export

Export pulls a snapshot of the current feedback queue for a single site and environment. It is most useful when you need to share, archive, or checkpoint the queue rather than as a day-to-day workflow.

• You need to hand off a review set to a stakeholder who does not have TMXIO access.
• You want a checkpoint of the queue before a major change, so you can compare before and after.
• You are migrating reviewers between teams and want a record of historical decisions.
• An external compliance or reporting process needs the feedback set in a portable format.

If you find yourself exporting weekly to work outside TMXIO, that is a signal that something is missing from the in-product workflow. Surface it to support rather than building around it.

When to Import

Import brings external feedback into the Lens queue for a specific site and environment. It is the right tool when you have a structured set of items that should live alongside normal Lens feedback, and the wrong tool for ad-hoc one-off entries.

• You are consolidating review history from a previous tool into Lens.
• You have a curated list of items from a workshop or audit and want to track them through the normal status workflow.
• You are restoring from a previous export after an accidental deletion or environment change.

Validate before importing

Imports change the live queue. Before running an import, confirm three things: the target site is correct, the environment is correct, and the file you are about to import matches what you think it does. An import targeted at the wrong environment will create real items in the wrong place, and there is no automatic undo. If in doubt, export the current queue first as a checkpoint.

Exporting Cleanly

1. Confirm the site and environment. The export reflects exactly one environment at a time. Switch to the environment you intend to capture before opening the export dialog.

2. Filter to the scope you want. If you only need open items, apply the status filter first. Exports respect the active filters.

3. Run the export. Save the file with a name that includes the site, environment, and date. A naming convention like site-name_env_YYYY-MM-DD.ext saves a lot of confusion later.

4. Verify the file before sharing. Open the export and confirm the row count matches what you expected from the filtered view.

5. Note the export in the team log. If your team keeps a shared log of significant queue actions, record the export so it can be reconciled later.

Importing Cleanly

1. Take a checkpoint export first. Before importing anything, run an export of the current queue so you have a clean rollback point.

2. Confirm the target environment. Switch to the exact site and environment the import is meant for. Imports cannot be moved between environments after the fact.

3. Inspect the file. Open it and confirm the column headers, environment field, and row count match expectations. If the file came from another team, read at least the first few rows in detail.

4. Run the import. Use the in-product import dialog. Avoid splitting one logical import across multiple files; it makes deduplication harder.

5. Verify the result in the queue. Filter the inbox to the newly imported items and spot-check at least a handful. Confirm the page context, status, and environment all look right.

6. Triage the imported items. Imported items are not exempt from the normal triage workflow. Assign owners, move statuses, and add comments as you would for fresh feedback. See Review and triage feedback.

What to Verify

Regardless of which direction you are moving data, the same three things matter every time.

• The target site is correct.
• The environment context is correct.
• The team understands whether the import will duplicate or overlap existing items, and has a plan for resolving any duplicates.

What Success Looks Like

• Exports are taken intentionally, not as a default workflow, and are named consistently.
• Imports never land in the wrong environment, because the team verifies before running them.
• A clean checkpoint export exists for every significant change to the queue.
• Imported items go through the same triage process as any other feedback.

Related

Review and triage feedback

Environment behavior

Lens settings in TMXIO