What I built for you

Two tools, both built for the migration your apps are facing: the Embed Migration Kit (a Shopify app) and Cutover (a control room for the team that runs the migration). Every time below is in Mérida time (UTC−6) and comes from the commit history or the session logs.

The Embed Migration Kit

A Shopify app that moves a store from script tags and legacy theme code to a theme app embed, and proves it works before it removes anything. It has four stages, run store by store:

1. Measure: the legacy code in every theme, with file and line.
2. Activate: opens the exact theme so the merchant can click; no app can do that click for them.
3. Verify: three signals, including a ping from the live storefront.
4. Remove: one store at a time, with retries.

It also fixes prices by country: it moves stores that fake local prices with one variant per country to Markets price lists.

In numbers

• Under 3 hours of wall-clock time from the first commit to the production release with price lists (Oct 10, 2:35 → 5:14 pm).
• 12/12 unit tests passing.
• Shopify refused a new script tag on API versions 2026-10, 2026-01 and 2025-10, tested live.
• 6 legacy-code markers on the live theme and 0 on the cleaned copy.
• Prices: a product in Mexico went from 16,558 MXN (converted) to a fixed 15,999 MXN from the market's price list. The old per-country variant, priced at 15,999, showed 299,006 MXN once Markets converted it again.
• Batches of up to 250 prices per call. Running it twice changes nothing.

The traditional estimate is my judgment of what a senior developer who already knows the system would need. It is an estimate, not a measurement. The full build log, with the basis of each estimate, is here: the build log

The weekend, step by step

Cutover · the migration control room

https://cutover.dabychos.com

I built Cutover on the morning of our call, for the people who will run the migration day to day. It is an installable web app (PWA) that works offline, in English and Spanish.

• The deadlines, live. A countdown to the day script tags stop loading, and a board of every dated platform change since 2024. Each change links to its source and carries a confidence label.
• Migration manuals. Step by step, with copyable code that fills in your store's values. Official facts and field notes are labeled differently.
• Your team's manuals. Write your own in Markdown, keep them there and export them.
• Track a store. The same stages as a per-store checklist, with the runbook's verdicts.
• Stuck on Verify? A decision tree that asks a few questions and gives the fix, plus a troubleshooting table you can filter by symptom, cause or fix.
• Tools that run in your browser. Nothing you paste leaves the page.
  • A theme scanner: paste theme.liquid or drop a theme .zip, and it finds legacy currency code and a broken </body>, with file and line.
  • A token inspector: it tells you whether an access token survives January 1, 2027.
• Migration tracker. A dashboard, a task list by phase and a roadmap, with a tutorial for every step:
  • tasks done against the plan, week by week;
  • the next deadline;
  • a CSV export;
  • a one-minute tour of the real screens.

Open each piece