Migration guide
Migrate from Strapi to RankFlo
Self-host with less config — RankFlo gives you out-of-the-box SEO, AI, and analytics.
Why move from Strapi
- Out-of-the-box: AI writing, SEO scoring, analytics — Strapi requires plugins for everything
- Modern Next.js + Tiptap stack — Strapi's admin UI is older
- Type-safe tRPC API alongside REST
- Built-in cookieless analytics, no separate Plausible/Umami install
- Same self-host story (Docker Compose) but with batteries included
- Native scheduled publishing, team roles, and approvals
Things to plan for
Edge cases that come up on most Strapi → RankFlo migrations.
Custom content types
Strapi lets you define any content type. Map each to a RankFlo project (or use tags for finer-grained categorization).
Plugins
Strapi plugins (i18n, SEO, GraphQL, etc.) translate to RankFlo's built-in features in most cases. Check our feature matrix in the migration tool.
Step-by-step migration
4 steps. Export format: JSON via Strapi REST API or import-export plugin
- 1
Export Strapi data via API
10 minHit Strapi's REST API: GET /api/articles?populate=*. Save as JSON. Or use Strapi's import-export plugin if installed.
- 2
Run the Strapi importer
5–15 minSettings → Import → Strapi (JSON). Map fields and run import.
- 3
Re-host assets
Strapi uploads live in your own /uploads folder or S3. The importer fetches by URL and re-uploads to RankFlo.
- 4
Update API consumers
Replace /api/articles calls with RankFlo's /api/v1/content. Field shapes are similar; titles, slugs, and body content map directly.
After the migration
SEO and operational checklist — don't skip these.
- ✓Set up 301 redirects from old URLs to new RankFlo URLs
- ✓Submit your new sitemap to Google Search Console
- ✓Verify all internal links resolved correctly
- ✓Re-add SEO meta titles and descriptions where missing
- ✓Configure your custom domain and HTTPS
- ✓Run a crawler (Screaming Frog) against the new site to catch broken links
Ready to leave Strapi?
Start a free trial — the importer ships with every plan.