# Switching Costs Are Dead: A 1-Day Yotpo → Idukki Migration, Hour by Hour

A real customer moved 18,000 reviews from Yotpo to Idukki in eight working hours. The hour-by-hour log, the snags we did not plan for, and what it means for lock-in.

By Rohin Aggarwal · 2026-01-30 · (updated 2026-11-11)

Your review contract renews next month. You would switch, but the last migration quote said weeks of engineering and lost photos. One of our customers moved 18,000 reviews from Yotpo to Idukki in eight working hours. This is the log, hour by hour.

Lock-in in the review category used to be close to absolute. Yotpo, Okendo, Trustpilot, [Bazaarvoice](/compare/bazaarvoice): every one of them had a migration story measured in weeks of engineering time. Exports were brittle and review content got lost on the way out. By 2026 that has stopped being true. Last month one of our customers moved from Yotpo to Idukki. It took eight working hours, start to finish. This is the log, hour by hour.

**Bottom line**

- A mid-market brand moved 18,000 reviews in 8 hours
- The import tool handled ~90% of field mapping
- Three snags surfaced; none blocked the migration
- AI-engine citations and PDP conversion rose after cutover
- Switching cost is now an operational footnote

The argument here is narrow. Switching costs in this category are now an operational footnote. So pick a platform on fit, and drop the fear of getting stuck.

## Who was the customer?

Mid-market UK apparel brand, 18,000 historic reviews across 240 SKUs, on [Yotpo](/compare/yotpo) since 2020. The reason for moving was AEO: Yotpo's verified-buyer schema is shallow, the JS-rendered widget is invisible to agent crawlers, and the per-impression pricing was scaling in the wrong direction. Engineering team of three, PM team of two. The crawler-visibility problem is the same one we dig into in the [answer engine optimisation 2026 playbook](/blog/answer-engine-optimisation-2026-playbook).

## The migration, hour by hour

### Hour 0. Pre-flight

Day before the migration: kick-off call, review the runbook, confirm DNS access, confirm Shopify admin access. 90 minutes total.

### Hour 1. Data export from Yotpo

Yotpo exports reviews via API. We pulled 18,000 reviews including ratings, photos, videos, replies, verification status. Total payload: 240MB. Export ran in 35 minutes; remaining 25 minutes spent validating the export against Yotpo's admin counts.

### Hour 2. Schema normalisation

Yotpo's export schema does not line up with Idukki's. The import tool handles the standard fields on its own (rating, body, author, date, SKU). The custom ones (Yotpo's "is_top_review", "is_helpful" counts, custom flags) we mapped by hand in a config file. 50 minutes, plus 10 for spot checks.

### Hour 3. Verified-buyer attestation

Yotpo's verified-buyer flag is email-based. Idukki re-runs the attestation against the merchant's OMS to upgrade to order-ID-linked verification where possible. 14,200 of 18,000 reviews (78.9%) upgraded to higher verification level. 45 minutes; the remainder is a wait-for-OMS task.

### Hour 4. Photo and video transcode

Yotpo stores photos and videos on its own CDN. We pulled all 4,200 photos and 380 videos, transcoded to Idukki's formats (WebP for photos, HLS for videos), and stored in our R2 bucket. Ran in parallel with hour 3; took 80 minutes total but mostly background.

### Hour 5. Shopify storefront integration

Remove Yotpo theme app embeds; install Idukki Shopify app; configure widget placement. The customer had 11 widget placements (PDP, category, homepage, checkout). 40 minutes to map and place; 20 minutes for QA on a preview theme.

### Hour 6. Schema and AEO wiring

Add Idukki's Review + AggregateRating JSON-LD to PDPs (server-side via Liquid). Wire up FAQPage component. Generate llms.txt. Submit updated sitemap. 50 minutes; 10 minutes for validator runs.

### Hour 7. Smoke test and DNS cutover

Run the test suite on a 5% traffic split. Check schema validates, widget renders, review counts match Yotpo's, photos and videos load. All green. Cut over the full traffic. 40 minutes; 20 minutes of monitoring.

### Hour 8. Final QA and Yotpo decommission

Final pass on edge-case pages (sale items, low-review SKUs, B2B SKUs with internal-only reviews). Disable Yotpo widget injection. Schedule Yotpo account cancellation for 30 days out (keeping read access to verify nothing regressed). 60 minutes.

| Hour | Step | Time on task |
| --- | --- | --- |
| 1 | Export 18,000 reviews via API | 60 min |
| 2 | Schema normalisation + custom-field mapping | 60 min |
| 3 | Verified-buyer re-attestation against OMS | 45 min |
| 4 | Photo + video transcode (parallel) | 80 min, background |
| 5 | Shopify widget placement + QA | 60 min |
| 6 | Review / AggregateRating schema + llms.txt | 60 min |
| 7 | Smoke test + DNS cutover | 60 min |
| 8 | Edge-case QA + Yotpo decommission | 60 min |

_The eight hours at a glance._

**Eight hours from Yotpo to live**
1. **Export** — 18,000 reviews out through the Yotpo API. (Hour 1)
2. **Normalise** — Schema and custom-field mapping. (Hour 2)
3. **Attest** — Verified-buyer re-attestation against the OMS. (Hour 3)
4. **Transcode** — Photos and video, in the background. (Hour 4)
5. **Place widgets** — Shopify widget placement and QA. (Hour 5)
6. **Wire schema** — Review and AggregateRating schema, plus llms.txt. (Hour 6)
7. **Cut over** — Smoke test and DNS cutover. (Hour 7)
8. **Decommission** — Edge-case QA, then Yotpo switched off. (Hour 8)
_The same steps as the table above._

> **What made it eight hours and not eight weeks:** The export API was clean, the import tool handled 90% of the field mapping on its own, and the merchant's team had Shopify admin access ready and decision authority in the room. Migrations that drag out almost always stall on access or approvals. Data complexity is rarely the cause.

## What snags did we hit?

Three things did not go to plan.

- Yotpo's API rate-limited us during photo download. We had to throttle to 5 requests/second instead of 20, which added 30 minutes to the photo transcode step.
- 12 reviews had broken photo URLs in Yotpo's export (404s). We surfaced these in a "needs attention" report; the merchant decided to mark them photo-less rather than re-collect.
- Three of the 11 widget placements were in a custom theme section that needed minor Liquid edits. About 25 minutes of theme engineering not in the original estimate.

None of them blocked the migration. The runbook had flagged all three in advance.

## What changed after migration?

Two weeks on, the merchant reported:

- GPTBot fetches on PDPs up 8.2x.
- ChatGPT citations of brand SKUs up 4.4x (measured via 90 query test suite).
- AI-engine referral sessions up 3.1x.
- PDP conversion rate up 6.7% (likely from improved verified-buyer signal and surfaced photos).
- Total monthly review-platform spend down 38% (per-transaction pricing vs Yotpo's impression tiers at time of migration — verify current pricing).

## Implications for SaaS buyers

If you are a DTC operator weighing a switch, the log points at three things to ask for before you sign.

1. A clean export API. If a vendor cannot give you one, treat it as a soft red flag while you are still evaluating.
2. A migration runbook. "We will help you migrate" means nothing without an hour-by-hour plan attached to it.
3. A timeline in hours. With competent tooling on the receiving end, most review-platform migrations now land in one to three working days, end to end.

## Closing

Staying on a worse platform because leaving feels expensive no longer holds up. The lock-in was always a tooling problem on both sides, and both sides have caught up. Evaluate on fit, run the export test while you are still shopping, and move when the case is clear. If the per-impression line on the invoice is what pushed you to look, the wider shift away from that pricing model is covered in [the economics of UGC 2026](/blog/the-economics-of-ugc-2026-per-impression-billing), and the [receiving-end pricing](/pricing) is public before you commit to anything.

**In one line:** A real customer migrated from Yotpo to Idukki in eight working hours. Here is the hour-by-hour log, the unexpected snags, and what it means for SaaS lock-in in the review category.

- **161%** — higher conversion among shoppers who interact with UGC (Yotpo, 200k+ stores / 163M orders analyzed)
- **+144%** — Lift among UGC-engagers (Bazaarvoice 2025 SEI)
- **79%** — Consumers say UGC highly impacts purchase (Nosto)
- **4.1x** — video reviews convert vs text-only (PowerReviews, 2023 baseline)

_UGC conversion benchmarks (cross-vertical)._

### Sources & notes
- [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; +354% conversion on PDPs with reviews vs without.
- [PowerReviews, How UGC Impacts Conversion (2023)](https://www.powerreviews.com/how-ugc-impacts-conversion-2023/) — Video reviews convert 4.1x better than text-only; photo reviews 2.6x; +103.9% lift among photo + video UGC interactors.
- [Nosto, Consumer UGC research](https://www.nosto.com/) — 79% of consumers say UGC highly influences purchase decisions; UGC rated 2.4x more trustworthy than brand-produced content.
- [BrightLocal, Consumer Review Survey 2024](https://www.brightlocal.com/research/local-consumer-review-survey/) — 88% of consumers look at reviews before purchase; 49% trust online reviews as much as personal recommendations.

---
Canonical: https://idukki.io/blog/switching-costs-are-dead-yotpo-idukki-migration
Tags: migration, yotpo, switching-costs, operations
