What happened
Shopify made its rebuilt Analytics experience the default on every store, automatically replacing the legacy reports interface. The new version brings real-time data, custom dashboards, metric-and-dimension explorations, and ShopifyQL querying directly inside reports, with the experience carried into the Shopify mobile app as well.
The operative word is automatically. This wasn't an opt-in with a sunset date you could plan around — it's the new floor for everyone. Which is why the immediate housekeeping item is verifying your saved reports survived the switch. A rebuilt interface plus an automatic cutover is precisely the combination that eats custom reports, and the merchants who find out are usually the ones pulling month-end numbers three weeks later, when the old interface is gone and there's nothing left to compare against.
Why this matters
On paper it's an upgrade — real-time data and an in-report query language beat a legacy reports page. But the features aren't the story. The mechanism is: a platform can rebuild your analytics and swap it in without asking, and every saved view, metric definition, and workflow you built on the old version is only as durable as the migration behind it. You didn't get a vote, and neither did the agency whose monthly report template just pointed at an interface that no longer exists.
Platform analytics is a rented view of your own business. Rented is fine for the daily pulse check. It's a problem when year-over-year comparisons, board numbers, or agency reporting depend on an interface someone else can replace on their schedule. This is exactly why we pin client reporting to GA4 and Search Console — no platform swap can take those away, and the definitions stay yours.
BigCommerce merchants shouldn't read this as a rival's stumble. Every SaaS platform runs forced migrations — admin redesigns, API sunsets, report rebuilds — and BigCommerce is no exception. The lesson transfers whole: any number that matters should exist somewhere the platform can't touch.
What to do about it
Audit your saved reports this week (Shopify stores)
Open the new Analytics, list every saved report your team actually uses, and confirm each one exists with numbers that match expectations. Rebuild anything missing now, while people still remember what the old report showed and why it was cut that way.
Run a week of parallel numbers against GA4
Compare revenue, orders, and traffic between the new Analytics and GA4 for a full week. A rebuilt reporting layer can shift metric definitions, and a side-by-side is the only way to catch a number that quietly changed meaning before it pollutes a trend line.
Export a monthly baseline, whatever your platform
Once a month, export your core numbers — revenue, orders, traffic by channel — to a spreadsheet you own. When the next forced migration hits any tool in your stack, your history doesn't leave with it.
Anchor recurring reporting to GA4 and Search Console
If a report goes to a client, a boss, or a board every month, build it on GA4 and Search Console rather than platform reports. Those survive replatforms, admin rebuilds, and vendor pivots alike — platform dashboards don't.