Skip to content
KylthDOCS

Migrating from Supabase Cloud

What moving a project from Supabase Cloud to Kylth involves, and which parts you do yourself.

Status: Kylth doesn't have an automated migration tool yet. This page covers what a move involves, using Supabase's own tools for the data.

The overall shape

  1. Create the destination project in Kylth. See Your first project.
  2. Move the database with the Supabase CLI.
  3. Move storage files separately, because they aren’t in the database.
  4. Point your apps at the new address and keys.
  5. Recreate settings that live outside the database.

Try the whole process on a spare project first.

Move the database

Supabase’s guide, Backup and Restore using the CLI, gives the commands. It dumps the roles, schema and data from your Cloud project, then restores them into another database with psql.

Use the project’s connection string, from the Overview tab in Kylth, as the destination. It points at 127.0.0.1, so it only works from the server itself. Run the restore there, or through an SSH tunnel.

Move storage files

Files in Storage buckets aren’t part of the database dump. The same Supabase guide has a section on migrating storage objects.

Point your apps at Kylth

The new project has its own address, and its own keys: ANON_KEY and the rest are on the project’s Overview tab, under Credentials. Update your apps with both.

Because the keys are new, tokens issued by the Cloud project don’t work on the new one, and your users sign in again.

Recreate what isn’t in the database

  • Auth settings, such as providers and redirect URLs, in the project’s Auth tab. Redirect URLs change to the new address.
  • Edge Functions, which you deploy to the new project.
  • Anything else your Cloud project configured in its dashboard, outside the database.

Moving back out

To take a project from Kylth to Supabase Cloud or elsewhere, use a Portable export. See Uninstall.