AgentReady
AgentReady

Import reviews from Judge.me

Export from Judge.me, map the columns AgentReady reads, and import without losing verified badges, replies, or photos.

Last updated 2026-09-01

Judge.me remains stronger at unlimited collection emails, video, and a generous free plan. This page is only the move: get your history into AgentReady Reviews without losing the fields that survive a CSV.

The longer version is Moving from Judge.me to AgentReady Reviews. After import, moderate before you publish.

1. Export from Judge.me

In Judge.me, export your reviews to CSV. Keep the file. Do not uninstall Judge.me until counts match on sample products. If Judge.me also emits review markup, you will turn that off later during the ownership check.

2. What columns carry over

AgentReady fingerprints a Judge.me file when the header includes reviewer_name, reviewer_email, review_date, or metaobject_handle. These fields map when present:

  • Stars, title, and body
  • Reviewer name and email
  • Review date
  • Product id or handle
  • Verified-buyer badges
  • Public merchant replies
  • Photo URLs (re-hosted into your Shopify Files on import)

Video, widgets, and Judge.me collection emails do not come across. Those stay better on Judge.me.

3. Source-rejected rows arrive unpublished

If Judge.me marked a row rejected, spam, or hidden, AgentReady imports it unpublished. You decide whether it ever goes live. Re-imports are duplicate-safe: the same review is not stored twice.

4. Unmatched products

Rows whose product id or handle does not match a live product land in a repair queue. They are not dropped. Fix the handle or gid and import again, or match them in the queue.

5. Limits

One file may be up to 25 MB and 50,000 rows. Split larger libraries.

Paste your header row below to see which aliases matched.

Check a CSV header row

Paste the first line of an export. This uses the same header fingerprints as the importer: Okendo, Judge.me, Loox, or generic.

Nothing to check until you paste a header.

Next