Migration pitches are everywhere right now, almost all of them from the side that gets paid when a brand replatforms. What rarely gets said out loud is that for a meaningful share of the brands we talk to, the right move is not a migration at all — it is fixing what is actually broken on the platform they already have. Before we will even scope a Shopify migration for a client, we run the same internal audit. Here it is.
The Site Audit We'd Run Before You Spend a Dollar on a Shopify Migration
Theme debt. How much of the current theme is still load-bearing custom Liquid versus inherited cruft from a build two redesigns ago? We profile every section against the live template files the way we outlined in How Headless Lost Its Head — most of what looks like a “platform limitation” is actually theme debt nobody has paid down.
App bloat. Every installed app adds script weight and a checkout or theme-app-extension dependency that has to be re-vetted on a new platform anyway. We audit what each app actually does versus what it was installed to do eighteen months ago, and most audits find at least two or three apps doing nothing a native Shopify feature does not already cover.
Checkout customizations. Shopify Plus merchants running custom checkout logic need to know exactly what that logic does before pricing a migration, because checkout extensibility has changed what is and is not portable. This is the step most migration pitches skip entirely, and it is where budgets actually blow up.
Content model. How tightly is content coupled to the current CMS structure? A clean content model travels; a tangled one means a “simple” migration turns into a rebuild. We have run this audit on real client builds, including the groundwork documented in our Technology & Style acquisition, which exists specifically to handle this kind of ongoing Shopify Plus support work.
Run through all four and a migration budget often shrinks, or disappears, before a single line of new code gets written.