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

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.

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.

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.

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.

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