Supabase to Insforge migration with an AI agent

Edu walks through migrating a Supabase project to Insforge using an official migration repository or a custom skill for an AI agent. He describes Insforge as an open source backend with database, authentication, storage and MCP access for work inside an IDE. The tutorial covers both cloud and self-hosted Supabase projects.

The repository method requires Node.js 20 or higher, PostgreSQL's psql command, and connection credentials for both projects. Authentication comes first. Edu explains that the export includes user IDs, emails and password hashes, and says both services use bcrypt so users can keep their passwords. The database stage exports a dump, transforms its SQL and imports it into Insforge. Storage migration recreates buckets, transfers files through the user's machine and updates database URLs that reference them.

Some details still need attention. Policies that use auth.jwt require rewritten logic, and a public.users table needs renaming because it conflicts with an internal Insforge table. Realtime behavior does not migrate automatically, functions need review, and active session tokens do not transfer, so users must sign in again.

The second method uses Edu's migration skill in OpenCode with Kimi 2.6. It follows the same migration stages, asks for credentials and includes manual approval points. The automation does not remove the application checks described in the tutorial.