Prepare a Podia migration inventory
Read the guide →Guide preview
Move only after the inventory distinguishes transferable content from pages, payments and promises that need separate work.
Public pages, migration, access and a manageable support boundary.
Public pages, migration, access and a manageable support boundary.
New to the topic? Begin with the first guide. Otherwise, go straight to the question you need to answer.
Move only after the inventory distinguishes transferable content from pages, payments and promises that need separate work.
Do not treat content migration as permission or technical support for transferring recurring payments.
An import should preserve permission and exclusions, not turn every historical contact into a marketing subscriber.
A useful sales page answers a real buyer decision and clearly separates public information from member-only delivery.
Check the offer, price, access and customer explanation as one journey before sending an audience to checkout.
A launch is ready when the promise, public route, delivery and recovery plan agree—not when every possible page is finished.
Specify the support your offer includes and keep it distinct from Podia’s platform support.
Diagnose account, entitlement and content visibility separately before changing a buyer’s access or charging again.
Check the limits of integrations, migration, public content and plan allowances against your actual offer.
Preserve domain ownership and existing email records while following Podia’s current supported domain instructions.
Compare the exact hostname and supported records before assuming delay or changing unrelated settings.