# Q1 replatforming: run reviews and UGC in parallel for 30 days

A day-by-day parallel-run plan so Shopify migrations do not zero out stars, galleries or rights logs. We make Idukki.

By Rohin Aggarwal · 2026-01-20

January is replatforming season. Finance signed the Shopify Plus contract, the agency booked the theme sprint, and someone on Slack asked whether Judge.me “just comes along.” It does not—not without a <strong>parallel run</strong> that keeps reviews, UGC and rights visible while URLs and product IDs change. We make Idukki. This is the 30-day calendar we give merchants who cannot afford a blank PDP in February.

**Quick answer**

- Freeze SKU and handle mapping before you touch the theme.
- Run old and new storefronts with matched JSON-LD for at least two weeks of real traffic.
- Import reviews early; reattach UGC by product ID, not Instagram permalink.

## Quick answer

- Freeze **SKU and handle mapping** before you touch the theme.
- Run old and new storefronts with **matched JSON-LD** for at least two weeks of real traffic.
- Import reviews early; reattach UGC by **product ID**, not Instagram permalink.
- Keep a **rights log** export that survives the cutover—compliance does not pause for migrations.
- Read [headless UGC and public JSON](https://idukki.io/blog/headless-ugc-2027-replatforms-public-json-etags) if you are decoupling the front end.

## Week 0 (before parallel run)

**Day −7 to −1:** Inventory every proof source. Review app, UGC gallery, Instagram feed app, loyalty-driven posts, Bazaarvoice if enterprise. Use the [post-holiday stack audit](https://idukki.io/blog/post-holiday-shopify-stack-audit-seven-apps) as the worksheet.

**Export checklist:**

- Full review CSV from Judge.me, Loox or Okendo ([October comparison](https://idukki.io/blog/judge-me-vs-loox-vs-okendo-2026)).
- UGC metadata: creator, SKU, consent date, channels allowed.
- Redirect map: old `/products/` URLs to new handles.

**Day −1:** Turn off auto-sync jobs that create duplicate product IDs on the staging store.

## Week 1 — Staging truth

**Days 1–3:** Install review app on staging first. Import a **pilot collection** only. Validate stars on PDP match Google Merchant Center feed.

**Days 4–5:** Place UGC module on staging PDP. Run [Shopify product page checklist](https://idukki.io/blog/shopify-product-page-checklist-2026-20-checks) checks 8–14 (social proof zone and speed).

**Days 6–7:** Schema validation. Compare rendered HTML, not just Rich Results test on a perfect URL. Agents read what shoppers get on mobile data.

## Week 2 — Parallel traffic

**Days 8–10:** Soft launch new theme to 10% of traffic if your platform allows; otherwise use a password preview with QA crawlers.

**Days 11–14:** Monitor Search Console for structured data errors. Pair with [multi-source reviews markup](https://idukki.io/blog/multi-source-reviews-without-breaking-google-markup) if you syndicate.

**Parallel rule:** If a SKU sells on both builds during testing, pick one source of truth for **aggregateRating** to avoid double-counting.

## Week 3 — Cutover prep

**Days 15–17:** Full review import on production-new. Re-link UGC tiles. Run diff script: every active SKU should have ≥ the same proof count as old site.

**Days 18–19:** Email capture flows and Klaviyo blocks that embed UGC—swap domains and image hosts ([Klaviyo vs Omnisend guide](https://idukki.io/blog/klaviyo-vs-omnisend-for-shopify-2026) if you switch ESP at the same time).

**Day 20:** Rights log import into spreadsheet or Idukki—do not rely on “it is still on Instagram.”

## Week 4 — Flip and watch

**Days 21–22:** DNS/theme flip in low-traffic window. Immediate 301 audit.

**Days 23–25:** PDP spot checks on top 20 revenue SKUs. Use [fix one PDP element](https://idukki.io/blog/fix-one-pdp-element-january-social-proof-placement) if proof slid below the fold in the new theme.

**Days 26–28:** AI referrer spot check—run three prompts in Perplexity for hero products; compare to pre-migration baseline ([AI citation checklist](https://idukki.io/blog/2027-ai-search-commerce-pdp-citation-checklist)).

**Days 29–30:** Retrospective doc for agency retainer ([2027 UGC retainer scope](https://idukki.io/blog/agencies-sell-2027-ugc-retainers-scope-reporting)).

## Enterprise detour

If you leave Bazaarvoice mid-migration, follow the [Bazaarvoice → Idukki 30-day plan](https://idukki.io/blog/bazaarvoice-idukki-30-day-plan-q1-2027) instead of improvising SKU matching.

## What not to do

- Do not launch a new theme the same week you change review apps unless you enjoy debugging two variables at once.
- Do not delete the old widget until redirects and imports validate—gallery URLs are bookmarked by email campaigns.
- Do not skip [2027 compliance](https://idukki.io/blog/2027-compliance-checklist-ftc-uk-fake-reviews-ugc-rights) re-attestation on imported reviews.

## Roles during parallel run

| Role | Week 1–2 | Week 3–4 |
| --- | --- | --- |
| Dev / agency | Staging schema, redirects | Cutover, 301 audit |
| Ops | Review import pilot | Full SKU diff |
| Brand | UGC re-tag by SKU | Gallery QA on top 20 |
| Legal | Rights export integrity | Re-sign incentives if needed |

## Staging vs production pitfalls

**Duplicate GTINs** on staging pollute Merchant Center if feeds are connected—disconnect feeds until production is canonical. **Review counts doubling** when both themes expose widgets—use noindex or password on old theme except for QA IPs.

If you run headless, read [headless UGC and public JSON](https://idukki.io/blog/headless-ugc-2027-replatforms-public-json-etags) before you assume the Shopify theme app embed still applies.

## Data you must not lose

- Creator consent timestamps and channel list
- Whitelisting end dates for paid social
- Review syndication tokens and Google program enrollment
- Shoppable video attribution settings ([12-question video test](https://idukki.io/blog/how-to-choose-a-shoppable-video-app))

## Post-cutover 48-hour war room

Hour 0–8: top 50 SKU PDP visual check + add-to-cart. Hour 8–24: structured data error report. Hour 24–48: email and SMS modules that embed UGC—swap CDN URLs if domain changed.

Document everything for the client’s [2027 retainer](https://idukki.io/blog/agencies-sell-2027-ugc-retainers-scope-reporting) handoff.

## Checklist export (printable)

- SKU/handle map signed by merchandising
- Review CSV from old store archived
- UGC rights export with consent dates
- Staging JSON-LD validated on pilot SKU
- 301 list deployed day of cutover
- AI referrer baseline captured pre-flip

## Roles during parallel run

| Role | Week 1–2 | Week 3–4 |
| --- | --- | --- |
| Dev / agency | Staging schema, redirects | Cutover, 301 audit |
| Ops | Review import pilot | Full SKU diff |
| Brand | UGC re-tag by SKU | Gallery QA on top 20 |
| Legal | Rights export integrity | Re-sign incentives if needed |

## Staging vs production pitfalls

**Duplicate GTINs** on staging pollute Merchant Center if feeds are connected—disconnect feeds until production is canonical. **Review counts doubling** when both themes expose widgets—use noindex or password on old theme except for QA IPs.

If you run headless, read [headless UGC and public JSON](https://idukki.io/blog/headless-ugc-2027-replatforms-public-json-etags) before you assume the Shopify theme app embed still applies.

## Data you must not lose

- Creator consent timestamps and channel list
- Whitelisting end dates for paid social
- Review syndication tokens and Google program enrollment
- Shoppable video attribution settings ([12-question video test](https://idukki.io/blog/how-to-choose-a-shoppable-video-app))

## Post-cutover 48-hour war room

Hour 0–8: top 50 SKU PDP visual check + add-to-cart. Hour 8–24: structured data error report. Hour 24–48: email and SMS modules that embed UGC—swap CDN URLs if domain changed.

Document everything for the client’s [2027 retainer](https://idukki.io/blog/agencies-sell-2027-ugc-retainers-scope-reporting) handoff.

Parallel runs feel slow. They are faster than recovering organic citations and Merchant Center disapprovals in March.

## Vendor escalation paths

If review import fails mid-cutover, open tickets with **both** review vendor and theme agency in one thread—prevents finger-pointing while PDPs show zero stars.

## SEO and AI baseline

Capture weekly Search Console structured-data errors and three AI shopping prompts pre/post flip. Replatforming regressions show up in citations before they show up in revenue ([agent teardowns](https://idukki.io/blog/how-ai-agents-actually-choose-products-12-conversation-teardowns)).

### FAQs

**Q: Who is this guide for?**

A: Heads of ecommerce, CMOs and campaign leads preparing holiday and 2027 peak-season proof.

**Q: Does this require a new UGC tool?**

A: No. The checklist works with any collection workflow; Idukki is one option for tagged, shoppable galleries.

**Q: Where should I start?**

A: Read the quick answer, then work the first section of Q1 replatforming: run reviews and UGC in parallel for 30 days on your top revenue SKUs.

### References
- [Idukki help centre](/help)
- [Engagement and analytics docs](/docs/engagement-analytics)
- [UGC resources and playbooks](/resources)
- [Related: post-holiday-shopify-stack-audit-seven-apps](/blog/post-holiday-shopify-stack-audit-seven-apps)
- [Related: headless-ugc-2027-replatforms-public-json-etags](/blog/headless-ugc-2027-replatforms-public-json-etags)
- [Related: bazaarvoice-idukki-30-day-plan-q1-2027](/blog/bazaarvoice-idukki-30-day-plan-q1-2027)

---
Canonical: https://idukki.io/blog/q1-replatforming-reviews-ugc-parallel-run-30-day
Tags: replatforming, shopify, reviews, ugc, migration