Key takeaways
- Shogun renders pages through its app layer. After uninstall, Shogun keeps published pages live as static HTML, but the content is frozen - edit it outside Shogun and the styling can break, and Shogun forms stop working once data is redacted.
- The two things teams worry about losing are Shogun’s page analytics and A/B testing. Plan replacements before you move, because Shogun deletes analytics and test data within 14 days of uninstall.
- The sequence mirrors any Shopify page-builder migration: inventory live pages, share each URL with Fudge, rebuild on a dev theme, test, publish to live at the same URL, then uninstall. No new slugs, no redirects.
- Fudge rebuilds each page as native Liquid, CSS, and HTML in your theme. The output stays fully editable after the app is gone - not frozen HTML.
- Don’t migrate your highest-traffic page first. Run the full cycle on a non-critical page to validate it.
This guide covers moving from Shogun to Fudge AI on Shopify. Shogun is a capable drag-and-drop builder with genuine strengths in page-level analytics and A/B testing. The structural reasons teams migrate are output ownership (pages that stay editable instead of frozen) and page speed (no app rendering layer on customer page loads).
Why you can trust us
Four years inside Shopify, dozens of page-builder migrations across Shogun, PageFly, Replo, GemPages, Instant, and homegrown builders. We build Fudge - the AI agent on the other side of this migration. It reads your existing page and regenerates it as native theme code.
The sequence
Same as any page-builder migration, with a few Shogun-specific notes.
Step 1: Inventory every live Shogun page
Open the Shogun dashboard and list everything currently published. For each page record:
- URL and page type (landing page, blog post, PDP section, homepage section)
- Monthly traffic and whether it carries ad spend
- Active A/B tests - which pages have running experiments you’ll need to resolve first
- Last edit date - pages untouched for 6+ months may be archive candidates, not migration candidates
Two Shogun-specific things to capture now, because Shogun deletes them within 14 days of uninstall: your page analytics history (click-through, conversion, bounce) and any A/B test results. Export or screenshot anything you want to keep before you remove the app.
Step 2: Build a non-critical page first
Don’t start with your top-converting landing page. Pick a medium-traffic, low-stakes Shogun page and run the full cycle: share the URL with Fudge, rebuild on a dev theme, publish to live, monitor.
This gives you the muscle memory for the higher-stakes pages later.
Step 3: Rebuild in Fudge
Paste the live Shogun page URL into Fudge. It reads the existing page and regenerates it as native Liquid + CSS + HTML on an unpublished dev theme, at the same URL. Iterate with prompts until it matches.
A Shogun-specific note: Shogun pages are often built from its CMS and drag-and-drop blocks, so the structure is usually clean and easy for the agent to read. Use the rebuild as a chance to drop anything you only added because the editor made it easy - oversized hero stacks, redundant sections, decorative blocks that never earned their place.
Step 4: Test
Lighthouse Mobile. Add-to-cart through to checkout where relevant. Pixel events (Meta, GA4, TikTok). Slow-4G simulation.
Confirm the page renders identically on the dev theme preview before publishing. Because the live URL doesn’t change after publish, nothing downstream - ad creative, internal links, sitemaps - needs updating.
Step 5: Publish to live, watch
Publish the dev theme. The URL is unchanged. Your theme code now serves the slug instead of the Shogun app layer. No 301 redirects, no new analytics entries, no ad-creative updates.
Watch conversion rate and traffic for 24-48 hours. If anything looks off, investigate before rolling out further migrations.
Step 6: Repeat for the backlog
In priority order. Don’t try to migrate everything in one sprint. Resolve any running A/B tests before migrating those pages - pick the winner, migrate the winning variant, retire the experiment.
Step 7: Uninstall Shogun
Only after every page is migrated, you’ve exported the analytics and test history you want to keep, 14+ days of live data confirm no regression, and the theme is clean of leftover Shogun section and snippet files.
What you give up - and how to replace it
Being fair to Shogun: the reason teams hesitate to leave isn’t the page builder itself. It’s the data layer. Two features in particular.
Page-level analytics
Shogun tracks click-through, conversion, and bounce rate per page inside the app, without external tools. That’s convenient.
The replacement is GA4 plus your theme. Once a page is native theme code, your existing GA4 setup and any heatmap tool (Microsoft Clarity, Hotjar) measure it like any other template. You lose the single-dashboard convenience; you don’t lose the measurement. For most teams already running GA4, this is a wash.
A/B testing
This is the bigger one, and it’s worth being precise. As of late 2025, Shogun split A/B testing into a separate standalone app, and built-in page-builder testing is no longer offered to new Shogun installs.1 So depending on when you onboarded, A/B testing may already live outside the page builder.
Fudge does not include built-in A/B testing. Because Fudge pages are standard theme sections, you can run experiments on them with Shopify-native testing tools or a dedicated app. See our A/B testing guide for the options. If live experimentation is the core of your workflow, plan this replacement deliberately before you move.
Content scheduling
Shogun supports timed page launches. If you rely on scheduled drops, replicate the cadence with your normal theme-publish process or a scheduling app. For most stores this is occasional, not daily.
A note on the uninstall, because Shogun handles it differently
It’s worth being accurate here, since a lot of migration advice gets this wrong.
Unlike builders whose pages go fully blank on uninstall, Shogun keeps your published pages live as static HTML after you remove the app. The pages don’t disappear.
But “live” is not the same as “yours”:
- The HTML is frozen. Shogun’s docs note that editing these pages outside Shogun can strip the styling, which then requires re-publishing through Shogun - which you’ve just uninstalled.
- Shogun forms stop working once your data is redacted (within 14 days), because the app can no longer store submissions.
- Leftover code stays in your theme. Shogun recommends leaving its section and snippet files in place so the frozen pages keep rendering.
So the realistic post-uninstall state of an un-migrated Shogun page is: visible, but un-editable, with dead forms and orphaned app code in your theme. That’s why you migrate each page to native code first, then uninstall - so every live page is genuinely editable and clean.
For the broader cleanup, see our guide on removing leftover app code from Shopify.
Why this migration is worth doing
Two compounding wins for most stores:
- Page speed. Removing the Shogun rendering layer takes app JavaScript off customer page loads. On mobile, that usually helps LCP - see our page builder speed methodology. Faster pages compound on conversion rate.
- Output ownership. Your pages become real theme sections - version-controllable, editable by any developer, durable across app changes, and never frozen. That’s the opposite of static HTML you can’t safely touch.
For the full category comparison, see Fudge AI vs Shogun and our ranking of the best Shopify page builders. To understand the two product categories, our Shopify page builder and Shopify store editor pages explain what Fudge does beyond a single migration.
FAQ
Not immediately. Unlike some builders, Shogun keeps published pages live as static HTML after uninstall. But the HTML is frozen - editing it outside Shogun can strip the styling, Shogun forms stop working once data is redacted within 14 days, and leftover code remains in your theme. Migrating each page to native code first avoids all of that.
Yes, if you don't export it first. Shopify requires Shogun to delete stored data - including page analytics and A/B test results - within 14 days of uninstall. Screenshot or export anything you want to keep before removing the app.
No. Fudge does not include built-in A/B testing. Because Fudge pages are standard theme sections, you can test them with Shopify-native testing tools or a dedicated app. Note that Shogun moved its own A/B testing into a separate standalone app in late 2025, so newer installs already run testing outside the page builder.
No. Fudge rebuilds the page on a dev theme and publishes it at the same URL. There are no new slugs and no 301 redirects, so ad creative, internal links, and sitemaps keep working unchanged.
You paste the live Shogun page URL into Fudge. The AI agent reads the existing page and regenerates it as native Liquid, CSS, and HTML on an unpublished dev theme. You refine it with prompts until it matches, then publish to live at the same URL.
Yes. Shogun focuses on page building with a data layer. Fudge is an AI agent that also edits existing pages, builds quizzes, bundles, and campaign pages, and writes native theme code throughout. If you want more than a page builder, the scope is wider.
Footnotes
-
Shogun moved A/B testing to a standalone Shopify app in late 2025; built-in testing is no longer available to new page-builder installs. Source: Shogun App Store listings and support documentation, 2026. ↩
