Importing

Bring testimonials you already have — from a spreadsheet, or from another tool.

Collection → Imports → New import. Upload a CSV, map its columns to fields, and run it.

How it runs

Imports are a background job. The upload returns immediately with a job you can poll, in the dashboard or through the API with read:jobs.

Rows land as pending, like everything else. An import is not a way to publish in bulk — the queue is still the queue.

Column mapping

You map your columns rather than renaming them to match us. Text, name, email, title, company, rating and date are all mappable, and anything you do not map is left empty.

Row errors do not stop the batch

A malformed row is reported as an error against that row; the rest of the file still imports. You get a count and a list, so you can fix twelve rows instead of re-uploading nine hundred.

Undeliverable addresses are dropped, not rejected

If a row's email address has no working mail exchanger, the address is dropped and the testimonial is kept. Losing a real testimonial over a stale address would be the wrong trade — but keeping the address would put your sending reputation at risk the next time you email that list.

Provenance

Imported items are marked as imported, with the batch they came from. That is worth having: six months later, "where did this testimonial come from?" has an answer, which matters if somebody asks you to prove you had permission to publish it.