Migration: internal admin → SaaS
If you used the internal admin build of ViralSlides, here's how the SaaS surface maps.
If you ran the original single-tenant ViralSlides (the internal admin tool that pre-dated the SaaS), most concepts carry over with new boundaries. This page maps the old surface to the new one.
What changed
- Multi-tenancy: every resource now belongs to an organization. The old admin operated on a single shared dataset.
- Plans & quotas: apps, slideshows/month, hook refresh, and API access are gated by plan. The Free tier roughly mirrors what the old admin offered for a single app.
- Auth: cookie-based admin sessions are gone in the user surface. Users authenticate with email + password (JWT). Super-admins still have an /admin login.
- API: the old /v0/api endpoints required an admin session. The same routes are now mounted under /v0/api/v1 for API-key access on Pro+.
Route mapping
| Old (admin) | New (SaaS user surface) |
|---|---|
| /admin/apps | /apps (dashboard) — /v0/api/v1/apps (API) |
| /admin/hooks | /hooks — /v0/api/v1/hooks |
| /admin/slideshows | /slideshows — /v0/api/v1/slideshows |
| /admin/generate | /apps/:id (dashboard) — /v0/api/v1/apps/:id/slideshows (API) |
| /admin/settings | /account + /billing + /team |
Data migration
If you're a beta tenant being migrated from the internal admin, we backfill a personal organization for each existing user and re-link their apps, hooks, and slideshows automatically. There's nothing to do on your side — log in with your old credentials and your data will be there.
The /v0/admin/* routes (orgs, subs, audit, health) still exist for super-admins. They're now scoped explicitly with requireSuperAdmin and don't grant access to per-org user actions.
Need help?
Email hello@viralslides.app with your old admin login email and we'll confirm your migrated org id and plan within 1 business day.