# Migrating from Loox / Stamped / Foursixty to Idukki, Hour by Hour

Switching UGC and reviews tools is a one-day job, not a one-month project. The hour-by-hour log, what transfers versus what gets rebuilt, and a first-week checklist.

By Rohin Aggarwal · 2025-11-26 · (updated 2026-06-16)

The migration brief landed on a Monday with a deadline of "before the next drop, please." The store had three years of photo reviews on one tool, a UGC gallery on a second, and an Instagram shop wall on a third. The founder assumed it would eat a sprint. It took a working day, and the only real snag was a column of star ratings that two tools labelled differently.

Migrating from Loox, Stamped, or Foursixty (now Bazaarvoice) to Idukki is a one-day job, not a multi-week project. Your reviews, photos, videos, and granted rights export from the old tool, import and re-tag in Idukki, and the storefront widget swaps over without downtime. The part that takes planning is not the data: it is access and approvals.

**Quick answer**

- Reviews, photo/video content, and existing rights grants transfer; the live widget and any custom theme placements get rebuilt
- Export from the old tool first (CSV or API), validate counts, then import into Idukki
- Re-tag products with Super Search instead of hand-mapping thousands of items
- Swap the widget on a traffic split so there is no downtime
- Most stores land the whole move in one working day; the friction is access, not data

This is a general playbook, not a guarantee about any one vendor's export format. Loox, Stamped, and Foursixty each expose data differently, and the specifics change. Treat the hour estimates below as a realistic shape for a mid-market catalogue, and run your own export test while you are still evaluating.

- **+18%** — Median PDP conversion lift with UGC (Idukki dataset, 2,400+ brands)
- **+144%** — Conversion lift among UGC-engagers (Bazaarvoice 2025 Shopper Experience Index)
- **79%** — Say UGC highly impacts what they buy (Nosto consumer research)
- **1 day** — Realistic end-to-end migration window (Idukki migration runbook)

_Why stores move, and what they stand to keep._

## What do you actually keep when you switch?

The fear that stops most switches is losing three years of reviews and a painstakingly built gallery. In practice the content layer travels well. Star ratings, review bodies, author names, dates, verified-buyer flags, photos, and videos are all standard fields that any serious tool can export and any serious tool can import.

What does not travel is anything tied to the old tool's rendering: the live widget, the exact theme placements, custom CSS, and any vendor-specific badge. Those get rebuilt in Idukki, which is usually a few minutes of placement work rather than a migration risk. The same is true for rights grants. If your old tool stored explicit consent records, those should be preserved on import so you are not re-requesting permission you already hold. If it stored loose or implicit rights, you carry that weakness with you and should re-clear the gaps. There is more on that in our [UGC rights and permissions guide](/blog/ugc-rights-and-permissions-guide).

| Asset | Transfers | Rebuilt | Notes |
| --- | --- | --- | --- |
| Star ratings & review bodies | Yes | No | Standard CSV/API fields; map the rating column carefully |
| Author name & review date | Yes | No | Preserved so historical reviews keep their timestamps |
| Verified-buyer status | Yes | No | Re-attested against your OMS where order IDs exist |
| Photo & video content | Yes | No | Pulled from the old CDN and re-stored; URLs change |
| Granted UGC rights records | Yes | No | Imported if explicit; gaps flagged for re-clearance |
| Product tagging on content | Partly | Partly | Re-applied with Super Search rather than by hand |
| Storefront widget & placements | No | Yes | Idukki app embed replaces the old widget |
| Custom CSS & vendor badges | No | Yes | Re-styled to your theme during placement |

_What transfers automatically versus what gets rebuilt in Idukki._

## How do you export from Loox, Stamped, or Foursixty?

Every migration starts with a clean pull from the tool you are leaving. Most UGC and reviews platforms offer either a CSV export from the admin or a programmatic API, and sometimes both. The CSV path is the path of least resistance for reviews and ratings; the API path matters when you have a large media library and want to pull photos and videos at their original resolution.

- Request the full export early. Large catalogues queue, and a 200MB+ media payload is not instant.
- Validate the export row count against the admin dashboard count before you do anything else. A short export is the single most common silent failure.
- Note how each tool labels its rating field. This is where the one real snag usually lives: a 1-5 integer in one tool can be a 0-100 score or a decimal in another.
- Pull media URLs, not just review text. Photo and video reviews are the assets that actually move conversion, so they are the assets you most want to carry over.

> **The export-test red flag:** If a vendor cannot give you a clean export of your own reviews and content, treat that as a soft red flag while you are still shopping. Lock-in that depends on data you cannot retrieve is the only switching cost that still bites, and it is one you can test for before you ever sign.

## How do you import and re-tag in Idukki?

Import in Idukki handles the standard fields on its own: rating, body, author, date, SKU, verified status. Custom or vendor-specific fields (a "top review" flag, a helpfulness count) get mapped by hand in a small config, which is a spot-check job, not an engineering project. Photos and videos are pulled from the old CDN and re-stored, so the storefront never depends on a URL that is about to be cancelled.

Re-tagging is where Idukki saves the most time. Old tools often need each piece of content hand-linked to a product, which is fine at a hundred items and miserable at ten thousand. Idukki's Super Search lets you describe what you are looking for in plain language ("white sweater on a beach", "watch close-ups") and pulls the matching content so you can attach the right products in bulk. Pair it with auto-curation to keep the galleries fresh after launch. The mechanics are covered in [AI content tagging for UGC](/blog/ai-content-tagging-for-ugc).

**The one-day migration timeline**
1. **Hour 0: Pre-flight** — Kick-off, confirm store-admin and DNS access, confirm decision authority is in the room. Done the day before. (90 min)
2. **Hour 1: Export** — Pull reviews, ratings, photos, videos, and any rights records from the old tool. Validate the count against the admin dashboard. (~60 min)
3. **Hour 2: Field mapping** — Map the standard fields automatically; hand-map the vendor-specific ones (top-review flags, helpfulness counts). Spot-check the rating column. (~60 min)
4. **Hour 3: Verified status & rights** — Re-attest verified buyers against the OMS where order IDs exist; import explicit rights grants and flag any gaps. (~45 min)
5. **Hour 4: Media transcode** — Pull photos and videos from the old CDN, re-store in Idukki formats. Runs mostly in the background. (~80 min bg)
6. **Hour 5: Re-tag with Super Search** — Bulk-attach products to content using natural-language search instead of hand-mapping every item. (~50 min)
7. **Hour 6: Widget rebuild** — Install the Idukki app, place galleries on PDP, collection, and homepage, restyle to the theme, QA on a preview. (~50 min)
8. **Hour 7: Split-traffic cutover** — Run on a 5% traffic split, confirm counts match and media loads, then cut over fully. No downtime. (~40 min)
9. **Hour 8: Final QA & decommission** — Edge-case pages, disable the old widget, schedule the old account for cancellation 30 days out for read-only verification. (~60 min)
_A realistic hour-by-hour shape for a mid-market catalogue. Several steps run in the background._

## How do you switch the widget without downtime?

Downtime is the fear that keeps tired storefronts on tired tools. It is avoidable. The old widget keeps rendering while you stage the new one, so the live site never shows an empty gallery. You place the Idukki widget, QA it on a preview theme, then route a small percentage of traffic to the new embed and watch the numbers.

- Stage the Idukki widget alongside the old one; do not remove anything yet.
- QA on a preview or duplicate theme so shoppers never see a half-built page.
- Cut over on a 5% traffic split, confirm review counts and media match the old tool, then go to 100%.
- Keep read-only access to the old tool for 30 days so you can verify nothing regressed before you cancel.
- Watch Core Web Vitals through the swap; a heavier widget can quietly cost you LCP. The trade-offs are in our [Core Web Vitals for UGC widgets](/blog/core-web-vitals-ugc-widgets) piece.

## What goes on the first-week checklist?

The migration is one day. The first week is where you make sure nothing drifted. Run this list before you consider the move finished.

1. Reconcile review and content counts against the old tool's final numbers, SKU by SKU on your top sellers.
2. Confirm every flagged rights gap has been re-cleared or the asset retired from live surfaces.
3. Check that JSON-LD (Review, AggregateRating, Product) validates and is server-rendered so agent crawlers can read it.
4. Spot-check edge-case pages: sale items, low-review SKUs, and any product with video-only content.
5. Confirm analytics is firing so you can attribute the lift; the method is in [how to measure UGC ROI](/blog/how-to-measure-ugc-roi).
6. Decommission the old tool only after read-only verification, then cancel on the scheduled date.

**What shoppers see after the swap**
Product: White Sweater Green Stripes ($110.76)
Hotspot: Tap to shop
- Re-tagged content: Product attached via Super Search, not by hand
- One-click add: Checkout link carried over from the old gallery
- Verified badge: Re-attested against the store OMS on import

> Switching costs in UGC and reviews are now an operational footnote. Choose a tool on fit, not on the fear of getting stuck.
> — Rohin Aggarwal, Co-founder, Idukki.io

**In one line:** Reviews, photos, videos, and rights transfer; the widget and placements get rebuilt in minutes. Run the export test before you sign, swap on a traffic split, and most stores land the whole move from Loox, Stamped, or Foursixty in a single working day.

### FAQs

**Q: How long does a migration from Loox, Stamped, or Foursixty to Idukki take?**

A: Most stores complete the full switch in a single working day, not a multi-week project. The runbook covers export, field mapping, verified-status re-attestation, media transcoding, re-tagging with Super Search, widget rebuild, and a traffic-split cutover, adding up to roughly eight hours, with several steps running in the background.

**Q: Do reviews, photos, and videos transfer when switching UGC and reviews platforms?**

A: Yes. Star ratings, review bodies, author names, dates, verified-buyer flags, photos, and videos are standard fields that export from Loox, Stamped, or Foursixty and import into Idukki. What does not transfer is the old tool's rendering: the live widget, theme placements, and custom CSS, which get rebuilt in Idukki instead.

**Q: How do you export data from Loox, Stamped, or Foursixty before migrating?**

A: Pull a full CSV or API export from the admin, then validate the row count against the dashboard before doing anything else, since a short export is the most common silent failure. Check how each tool labels its rating field, since a 1-5 integer in one tool can be a 0-100 score or a decimal in another.

**Q: Can you switch UGC widgets without taking the storefront offline?**

A: Yes. Stage the new Idukki widget alongside the old one without removing anything, QA it on a preview theme, then cut over on a small traffic split and confirm review counts and media match before moving to 100%. Keep read-only access to the old tool for a period to verify nothing regressed before cancelling.

**Q: What should you check in the first week after migrating to Idukki?**

A: Reconcile review and content counts against the old tool's final numbers on your top sellers, confirm every flagged rights gap has been re-cleared or the asset retired, and check that Review and AggregateRating JSON-LD validates. Spot-check edge-case pages like low-review SKUs, then decommission the old tool only after read-only verification.

[Download the migration checklist](/downloads/loox-stamped-foursixty-migration-checklist)

### Sources & notes
- [Loox Help Center, exporting reviews](https://help.loox.io/) — Public documentation on review export and import; exact fields vary by plan.
- [Stamped.io Help Center, data export](https://help.stamped.io/) — Review and rating CSV/API export documentation.
- [Bazaarvoice (Foursixty) resources](https://www.bazaarvoice.com/) — Foursixty now operates under Bazaarvoice; consult current export documentation.
- [Bazaarvoice, 2025 Shopper Experience Index](https://www.bazaarvoice.com/press/bazaarvoice-shopper-experience-index-shows-surging-importance-of-ugc/) — +144% conversion / +162% RPV among UGC-engagers.
- [Nosto, consumer UGC research](https://www.nosto.com/) — 79% of consumers say UGC highly influences purchase decisions.
- [Google, Core Web Vitals thresholds](https://web.dev/articles/vitals) — LCP, INP, CLS targets to hold through a widget swap.

---
Canonical: https://idukki.io/blog/migrate-from-loox-stamped-foursixty-to-idukki
Tags: migration, loox, switching-costs