← All migrations

Migration Guide

Migrate from PageFly
to Section Store.

An honest read on whether the switch fits your store, what stays the same, what changes, the concrete migration path — and the case for staying put if that's actually the right call.

The honest case

Why move from PageFly?

PageFly is a strong page builder but it ships with a third-party rendering runtime that adds measurable Core Web Vitals overhead on every page it touches. For stores running PageFly on more than a few high-value campaign pages, the cumulative performance cost compounds — and brand inconsistency creeps in because PageFly builds outside your theme tokens. Section Store flips both: native Shopify 2.0 theme app extensions (no third-party runtime) and theme-token inheritance by default (no per-page re-styling). The trade-off: you lose PageFly's drag-and-drop full-page canvas. That's the right trade for everyday catalogue sections; it's the wrong trade for one-off campaign landing pages.

What stays the same

  • Your existing PageFly campaign pages keep working — you can migrate gradually rather than all at once.
  • Your Shopify theme, products, collections, and cart flow are unchanged.
  • Your Shopify Apps stack (Klaviyo, Judge.me, etc.) keeps composing with both apps cleanly.
  • Your tracking + analytics setup carries over — no re-tagging.

What changes

  • Catalogue-wide sections now live in your theme editor (Shopify 2.0 native), not in PageFly's canvas.
  • Sections inherit theme color + typography tokens by default — no re-styling per page.
  • Page-speed budget on Section-Store-built pages improves measurably (the third-party runtime is gone).
  • You lose PageFly's drag-and-drop full-page builder — Section Store is section-based, not full-canvas.

Migration path

The concrete steps.

  1. 1

    Install Section Store alongside PageFly

    Both apps coexist. Free tier on Section Store lets you test without commitment.

  2. 2

    Pick your 3 highest-traffic pages currently built in PageFly

    Those are the pages where the performance gain from migrating most matters.

  3. 3

    Rebuild those 3 pages using Section Store sections in the theme editor

    Hero, FAQ, comparison, trust badges, customer stories — most PageFly patterns have a Section Store equivalent.

  4. 4

    A/B test for one week before retiring the PageFly versions

    Verify conversion rate holds or improves; verify Lighthouse scores improve on mobile.

  5. 5

    Continue migrating page-by-page; keep PageFly for campaign-specific custom landings

    No need to remove PageFly entirely — use it where its canvas earns its keep.

When NOT to switch

If your business depends on full-page drag-and-drop campaign landings (BFCM custom landings, deeply custom product pages with non-standard layouts), keep PageFly for those pages. Section Store is the right tool for everyday catalogue sections, not for replacing a page builder. The cleanest answer for most stores: both apps, used for different jobs.

FAQ

About the migration.

Going deeper

More on Section Store.

Ready to migrate?

Free to install. Try Section Store alongside PageFly and migrate page-by-page on your timeline.