WP Recipe Maker is the leading WordPress recipe plugin. Member Kitchens imports your WPRM library and turns your recipes into a full membership product — with meal plans, grocery lists, nutrition, and a branded app members install.
You choose the path and the pace — hybrid, phased, or full transition. Last reviewed June 2, 2026.
Most creators use one of these approaches — or combine them over time. None require a fixed deadline.
Alongside
Use alongside
Keep WordPress and WPRM for your public recipe blog and SEO. Launch Member Kitchens for your paid members alongside, importing your best recipes for the member cooking experience.
Best when:
WP Recipe Maker already handles sales or site pages you do not want to rebuild.
You want members cooking in a dedicated app without migrating every system at once.
You are testing Member Kitchens with a new tier while existing members stay on their current workflow.
Start a new paid tier on Member Kitchens using your WPRM export. Existing free readers stay on WordPress; paying members get the full interactive app.
Best when:
You have an active membership and want to avoid a disruptive all-at-once change.
You are still building your recipe library and prefer to expand content after go-live.
Billing cycles or annual plans make gradual migration the practical choice.
Full transition
Full transition
Import your full WPRM library into Member Kitchens and sunset the WordPress recipe stack. Members get a branded app on your domain with search, meal plans, grocery lists, and cooking mode.
Best when:
WP Recipe Maker no longer fits how members cook from your content every week.
You want one branded app for recipes, meal plans, monetization, and member experience.
You are early enough that migration scope is manageable on your timeline.
What stays vs what moves
What typically stays on WP Recipe Maker vs moves to Member Kitchens
Item
Often stays
Moves to Member Kitchens
Public recipe blog and SEO pages
WordPress blog (common in hybrid setups)
Optional — MK marketing pages for a unified presence
Recipe content (WPRM data)
WordPress during import phase
Imported library on MK with structured recipe data
Membership billing
Current setup until MK Stripe cutover
Native Stripe subscriptions and access levels on MK
Nutrition metadata
WPRM nutrition fields until import
Preserved through WPRM JSON import on MK
Typical phases (your pace)
These phases describe common order — not fixed dates. Skip or repeat steps as your situation requires.
1 Explore and import content
Tasks:
Start a trial and explore sample content to see how recipes, meal plans, and member views work.
Import flagship recipes from PDF, Word, CSV, WPRM JSON, or URL — review before publishing.
Decide which content must be live on day one versus what can follow in later batches.
What affects pacing:
A small library you have already structured moves faster than hundreds of PDFs needing review.
Higher editorial standards before publish extend this phase — that is normal and under your control.
2 Brand, access levels, and payments
Tasks:
Apply your theme, logo, and domain so members see your brand — not a generic template.
Set up access levels and offers that match how you sell today (or how you want to sell tomorrow).
Connect Stripe on Member Kitchens or map external checkout via integrations when you stay hybrid.
What affects pacing:
Stripe Connect and DNS for a custom domain add steps — plan for that if they are new to you.
Webhook product-to-access-level mapping takes longer when you have many SKUs or legacy offers.
3 Pilot with a trusted member group (optional)
Tasks:
Invite a small cohort — often 5–20 members — to use the app before a broad announcement.
Collect feedback on navigation, meal plans, and shopping lists while you still refine content.
Skip this phase if you prefer a soft launch to all members at once — many creators do.
What affects pacing:
Pilot length depends on how much feedback you want before scaling communication.
Busy seasons or launch windows may shorten or skip a pilot — your call.
4 Communicate and expand
Tasks:
Tell members what is changing, what stays the same, and where to log in.
Roll out remaining content in batches if you did not import everything upfront.
For phased migrations, move tiers or renewals to Member Kitchens on the schedule you set.
What affects pacing:
Phased rollouts follow your billing cycles and communication rhythm — not a platform deadline.
Large lists or multiple segments need more messaging prep; solo operators often move faster.
Factors that affect your timeline
Every creator moves at a different pace. These factors affect how long each phase takes more than any fixed schedule we could suggest.
Recipe and content library size
A dozen flagship recipes can be imported and reviewed quickly; hundreds of PDFs or legacy posts benefit from batch import and staged publishing.
How polished content must be before launch
Some creators launch with core recipes and expand weekly; others want every ingredient matched to nutrition data first.
Hybrid, phased, or full transition
Keeping checkout elsewhere and adding Member Kitchens for the member app is often the fastest first step; full cutover adds payment and member migration planning.
Access and payment complexity
Simple Stripe offers on Member Kitchens are straightforward; many external products mapped to access levels take more configuration and testing.
Pilot vs broad member rollout
A small pilot adds a feedback loop but delays a full announcement; big-bang launches compress calendar time but need clearer member messaging.
Your bandwidth and team help
Solo operators often move in focused sprints; teams with VAs or ops help can parallelize import and setup.
WPRM JSON export size
The larger your WPRM library, the more time to review AI-extracted import results before publishing — plan for a phased rollout for libraries over 200 recipes.
Getting started on Member Kitchens
Start a free trial on Discover and explore with sample content.
Import your first recipes while you still use WP Recipe Maker — no need to pause your current workflow.
Customize theme and pages so the app feels like your brand.
Connect payments or provisioning (Stripe, webhooks, or SSO) when you are ready — not before.
Read the full comparison if you are still evaluating fit.
Support while you transition
Transitions look different for every creator. Our team helps you map content import, access setup, and member communication to the pace that fits your business — not an arbitrary launch date.
Frequently asked questions
How does the WPRM import work?
Export your recipe data as WPRM JSON from WordPress, upload to Member Kitchens, and review AI-extracted structure — ingredients, steps, nutrition, and tags — before publishing.
Will my nutrition data come across?
Yes. WPRM JSON includes nutrition fields that Member Kitchens preserves during import. Complex custom fields may need manual review before publishing.
Can I keep my WordPress recipe blog?
Yes. Many creators keep WordPress for SEO and free public recipes while Member Kitchens powers the paid member cooking app. WordPress SSO can bridge logins if needed.
What happens to my recipe URLs?
Hybrid setups keep recipe URLs on WordPress unchanged. A full migration typically sets up 301 redirects from old WordPress recipe URLs to the new Member Kitchens app.
What affects import and switch speed?
Library size, recipe complexity (multiple ingredient groups, notes), whether you run a hybrid blog alongside MK, and member communication timeline — all creator-controlled.
