Vanya Insull (VJ Cooks / Cookplan) had a problem most food creators would envy: 1,000 paying subscribers.
But having a thousand members doesn't mean much when they're canceling faster than you can replace them. And that's exactly what was happening.
Vanya was running her meal plan membership on Kajabi, delivering recipe collections as PDF e-books. Her audience in Australia and New Zealand loved her recipes. But they were leaving anyway.
Here's how she fixed it — and what you can learn from her migration.
The Before State: Kajabi + PDFs + Churn
Vanya's setup was solid by most standards:
Platform: Kajabi (industry-standard for course creators)
Delivery: PDF e-book collections
Content: Hundreds of recipes, organized by theme/season
Audience: Loyal following from years of blogging and social media
On paper, it should have worked. But in practice, members were churning.
The Real Problem: Members Couldn't Find Recipes
Here's what Vanya discovered:
"Finding those recipes in Vanya's huge library became difficult for users."
Think about what that means. She had built an incredible library of recipes over years. Her members wanted to cook from them. But finding a specific recipe in Vanya's collection of PDF e-books was too much work.
The pattern looked like this:
Member joins, excited about the recipe library
Member downloads PDFs from the member portal
Member cooks a few recipes they find easily
Member wants to find "that chicken recipe" from a few months ago
Member has to scroll through email, open multiple PDFs, search page by page
Member gives up, stops cooking, eventually cancels
Vanya's Band-Aid Solution: Spreadsheet Catalogs
Vanya tried to solve this. She created spreadsheet catalogs of all her recipes — organized lists that members could reference to figure out which PDF contained which recipe.
It was better than nothing. But it was still:
Manual work for members to cross-reference
Extra steps between "I want to cook this" and "I found the recipe"
Not searchable, filterable, or mobile-friendly
Members appreciated the effort. But convenience wasn't there. Churn continued.
The Decision Point: Keep Patching or Migrate?
Vanya faced a choice many food creators hit:
Option 1: Keep Kajabi for checkout, keep PDFs for delivery, keep building workarounds.
Option 2: Migrate the cooking experience to a platform built for recipes and meal plans.
She chose Option 2.
But here's the critical nuance: She didn't abandon Kajabi entirely. Many food creators keep Kajabi for what it's good at (sales pages, checkout, email) and add a dedicated meal plan platform for what Kajabi can't do: the member cooking experience.
The Migration: 1,000 Subscribers to an Interactive Platform
Vanya migrated her entire membership — 1,000 active subscribers — to a platform built specifically for food creators (Member Kitchens).
Here's what changed:
1. Searchable Recipe Library (The Core Fix)
The #1 problem was "members can't find recipes." The #1 solution was instant search.
Vanya's members went from:
Opening PDFs and scrolling page by page
Cross-referencing spreadsheet catalogs
Hoping they'd recognize the recipe they wanted
To:
Typing "chicken" into a search bar
Seeing every chicken recipe instantly
Filtering by dietary tags, meal type, or cooking time
Result: The friction that caused churn disappeared.
2. Favorites System (Personal Collections)
With PDFs, if a member loved a recipe and wanted to cook it again, they had to:
Remember which e-book collection it was in
Find that PDF
Search through it again
With the interactive platform, members could:
Click "Favorite" on any recipe
See all their saved favorites in one place
Access them instantly from mobile
This turned Vanya's huge library from "overwhelming" to "personalized."
3. Interactive Meal Plans (Not Static Downloads)
Vanya could now deliver:
Weekly meal plans members could customize
Swap functionality (don't like this recipe? swap it)
Servings adjustment (cooking for 2 instead of 4? one click)
Auto-generated shopping lists
This wasn't just "better PDFs." It was a fundamentally different member experience.
4. Mobile-First Experience
Vanya's members cook on their phones. With PDFs, that meant:
Downloading attachments
Opening them in a PDF viewer
Zooming in to read ingredient lists
Switching between email, PDFs, and shopping apps
With the interactive platform, members could:
Pull up the app on their phone in the grocery store
See the shopping list for the week instantly
Access any recipe from anywhere
Everything synced across devices
Result: Members used the membership more because it was convenient.
5. Branded PWA (No App Store Fees)
Vanya specifically chose a platform that offered a Progressive Web App (PWA) — an installable app that members can add to their phone's home screen without going through Apple or Google's app stores.
Why does this matter?
App store fees: If you sell subscriptions through the Apple App Store or Google Play, they take 15-30% of your revenue. Vanya avoided this entirely.
Branded experience: Her members see "VJ Cooks" when they open the app, not a generic platform brand.
Convenience: Members can tap the app on their phone anytime, just like Netflix or Spotify.
The Results: Churn Slowed Down
Here's Vanya's direct quote after the migration:
"The churn has really slowed down."
Let's unpack what that means:
Before: Members were leaving because they couldn't find recipes in her PDF library. Churn was eating into growth.
After: Members could search, favorite, and access recipes instantly. Churn problem solved.
But that's not all. After launching the interactive platform, Vanya also saw:
+2,000 new signups (word of mouth improved)
Better member experience (fewer support questions about "where is that recipe?")
Avoided app store fees (kept 100% of subscription revenue)
What Made This Migration Work?
Not all migrations succeed. Here's what Vanya did right:
1. She Identified the Real Problem
The churn problem wasn't:
Her recipes weren't good enough (they were great)
Her audience wasn't committed (they wanted to cook)
Her marketing was weak (she had 1,000+ members)
The problem was: Members couldn't find recipes easily. She fixed that specific friction point.
2. She Chose a Platform Built for Food Creators
Kajabi is great for courses. But it's not built for weekly recipe delivery, searchable libraries, or auto shopping lists.
Vanya migrated to a platform designed for exactly what her members needed: interactive meal planning and recipe discovery.
3. She Kept What Worked (Kajabi for Checkout)
Many food creators keep Kajabi for:
Sales pages and checkout
Email marketing
Course content (if they offer cooking classes)
And they add Member Kitchens for:
The member cooking experience
Recipes and meal plans
Shopping lists and favorites
This isn't an either/or. It's using each tool for what it's good at.
4. She Migrated All 1,000 Members
Vanya didn't start fresh. She migrated her existing membership. This meant:
Her members didn't lose access to the recipes they paid for
She didn't lose recurring revenue during the transition
Existing members got the benefits of the new platform immediately
Migration was a retention play, not a relaunch.
Lessons for Food Creators
If you're experiencing churn like Vanya was, here's what to learn:
Lesson 1: Delivery Friction Causes Churn (Not Bad Recipes)
Your recipes are probably great. If members are leaving, the problem is likely:
They can't find recipes easily (no search)
They can't personalize the experience (no swaps/favorites)
Creating shopping lists is too much work (manual copying)
Mobile experience is frustrating (PDF downloads)
Fix the delivery, not the content.
Lesson 2: Interactive > Static (Every Time)
PDFs are static. Members download them once and they're done.
Interactive platforms are habit-forming. Members come back weekly to:
See new meal plans
Search the library
Update their favorites
Generate shopping lists
When members use your membership weekly, they don't cancel.
Lesson 3: Search + Favorites = Retention
The two features that matter most for retention:
Search: Members can find any recipe in seconds
Favorites: Members can build their own collections
These aren't "nice to have." They're churn prevention.
Lesson 4: Migration Doesn't Mean Starting Over
Vanya migrated 1,000 members. She didn't:
Lose her Kajabi setup
Start from zero
Force members to re-subscribe
She improved the experience for existing members. They stayed because it got better, not worse.
Should You Migrate?
If you're on Kajabi, PDFs, Patreon, or any platform where members are churning because:
They can't find recipes easily
They can't personalize the experience
Shopping lists require manual work
Mobile experience is clunky
...then yes, you should consider migrating.
But migration doesn't mean abandoning everything. It means:
Keeping what works (email, checkout, sales pages)
Fixing what causes churn (the member cooking experience)
Migrating existing members (don't start over)
What's Next?
Vanya's story isn't unique. Food creators who migrate from static delivery (PDFs, portals) to interactive platforms consistently see:
Lower churn (like Vanya)
Better member engagement
Less support overhead
Higher retention rates
If you're experiencing churn and wondering why members leave despite great recipes, the answer is probably delivery friction.
Compare Kajabi to interactive platforms
Your recipes are great. Your members want to cook. Make it easy for them.