Key takeaways
- Instant migrations skew LP-heavy, because Instant’s audience is paid-traffic teams (often coming from a Figma-to-page workflow).
- The sequence is the same as other Shopify page-builder migrations: inventory, share each URL with Fudge, rebuild on a dev theme, test, publish to live (same URL), uninstall. No new slugs, no redirects.
- Track conversion rate on each migrated LP closely - paid-traffic LPs are the highest-stakes pages in most catalogues.
- Don’t migrate active high-spend campaigns first. Start with a medium-priority LP to validate the cycle.
This guide covers moving from Instant to Fudge AI on Shopify. Instant is a capable LP builder with a strong Figma-to-page workflow; the structural reasons teams migrate are output ownership (pages survive uninstall) and page speed (no app runtime on customer page loads).
Why you can trust us
Four years inside Shopify, dozens of LP migrations across Instant, Replo, PageFly, GemPages, and homegrown builders. We build Fudge - the AI agent on the other side of this migration.
The sequence
Same as any page-builder migration, with a few Instant-specific notes.
Step 1: Inventory every live Instant page
In particular, identify:
- Pages with active ad spend (most important to migrate cleanly)
- Pages with high organic traffic (next priority)
- Test variants you can deprecate (Instant experiments that didn’t win - retire them)
- Pages that haven’t been touched in 6+ months (consider archiving instead of migrating)
Record URL, monthly traffic, ad-platform usage, and last edit. Save the inventory in a shared sheet.
Step 2: Build a non-critical page first
Don’t start with your top-ROAS LP. Pick a medium-traffic, low-stakes Instant page and run the full cycle: share the URL with Fudge, test on dev theme, publish to live, monitor.
This gives you the muscle memory for the high-stakes migrations later.
Step 3: Rebuild in Fudge
Paste the live Instant 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.
An Instant-specific note: Instant pages are often built from Figma designs and tend toward pixel-precise layouts. When rebuilding, take the chance to switch to flow-based, mobile-first layout. The result usually feels lighter and converts at least as well — without the Figma-to-page tooling overhead.
Step 4: Test
Lighthouse Mobile. Add-to-cart through to checkout. Pixel events (Meta, GA4, TikTok, X). Slow-4G simulation.
For paid-traffic LPs especially, confirm UTM handling and ad-platform tracking continue to fire correctly on the dev theme preview. Because the live URL doesn’t change after publish, no ad creative needs to be updated.
Step 5: Publish to live, watch
Publish the dev theme. The URL is unchanged — your theme code now serves the slug instead of the Instant runtime. No 301 redirects, no ad-creative updates, no new analytics entries.
Watch ROAS and conversion rate in the ad platform 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.
Step 7: Uninstall Instant
After every page is migrated, 14+ days of live analytics confirm no regression, and the theme is clean of Instant script/CSS imports.
A note on Figma-built pages
Instant’s Figma plugin is one of its defining features. If your team is shipping LPs from Figma designs today, plan the workflow change deliberately:
- Most Figma layouts translate cleanly to Fudge prompts (“hero with this headline, three-up benefits below, founder quote section, FAQ accordion”)
- The pixel-precise positioning common in Figma-to-page workflows often over-specifies the design. A flow-based rebuild is usually faster and converts better.
- For LPs that really do need exact Figma fidelity, Fudge can scaffold a custom theme section that your developer fills in from the Figma export.
For Shopify A/B testing tooling see our A/B testing guide.
Why this migration is worth doing for an LP-heavy store
Two compounding wins:
- Page speed. LP-heavy stores often see meaningful mobile LCP improvement after removing the Instant runtime — see our Shopify page builder speed test for the measurement methodology. On paid traffic, even small LCP gains compound on CR.
- Output ownership. Your LPs are now part of your theme, version-controllable, editable by developers, durable across app changes.
For the broader category and other migrations: PageFly to Fudge, GemPages to Fudge, Replo to Fudge, AI vs drag-and-drop.
FAQ
Will my ad ROAS drop during the Instant to Fudge migration?
It shouldn’t, if the new page is built well. The URL is unchanged through the migration, so existing ad creative keeps working. We typically see CR hold or improve after migration because page speed improves. Test on lower-spend campaigns first to confirm before migrating top-ROAS LPs.
Is the Fudge LP workflow as fast as Instant for paid-traffic teams?
Different rhythm. Instant is visual + Figma-driven, optimised for designer-led LP teams. Fudge is prompt-driven and generates a full draft in seconds. After the initial prompt, refinement is also prompt-driven. Most LP teams settle into Fudge in 1-2 weeks of daily use.
Can I keep using Instant’s Figma plugin?
No - the Figma-to-page workflow is Instant-specific. Fudge takes prompts and design references (you can describe a Figma frame in prose, or paste a screenshot), but doesn’t read Figma files directly. For LPs you’re unhappy with structurally, the migration is a chance to rebuild without the Figma round-trip.
What about pixel and conversion tracking?
Site-wide pixels (Meta, GA4) usually fire from your theme.liquid and continue working. Instant-specific tracking integrations may need re-implementing in your theme.
Do my Instant pages disappear instantly when I uninstall?
Un-migrated Instant pages typically revert to a Shopify default page or 404 on uninstall. Migrated pages are unaffected — they’re already theme code at the same URL. Migrate or archive every live Instant page before uninstalling.
