Migrate from Legacy PaaS

Document-database BaaS platforms typically export data via vendor CLI tools that produce LevelDB or JSON output. Download the export, then re-shape the documents into a relational schema for managed PostgreSQL on Open Source Cloud. Replace the bundled authentication service with SuperTokens or OpenAuth, both available in the catalog with self-hosted user data. File storage objects move to S3-compatible MinIO with a standard `aws s3 sync`. Document and relational stores have different shapes, so the data step is a re-shape, not a one-to-one dump.

Connect your GitHub repository through Open Source Cloud My Apps, set environment variables in the dashboard, and add your custom domain. Builds run on standard Node tooling and the runtime is a published Docker image you can inspect or run locally. Vendor key-value stores map to Valkey, vendor Postgres to managed PostgreSQL, blob storage to MinIO, all reached through standard connection strings. Edge runtimes and edge middleware are vendor-specific; if your app uses them heavily, plan to refactor those routes to standard Node handlers before cutover.

Open Source Cloud runs upstream PostgreSQL, so `pg_dump` from your existing instance and `pg_restore` into the OSC instance moves data without conversion. Replace bundled authentication with SuperTokens or OpenAuth, swap bundled storage for an S3-compatible MinIO bucket using `aws s3 sync`, and re-point realtime workloads to Centrifugo over WebSocket. Auto-generated REST and GraphQL APIs from PostgREST or pg_graphql patterns are not bundled by default; if your app depends on them, deploy PostgREST as an OSC hosted app or use Hasura GraphQL Engine from the catalog.