Need help to migrate from self-hosted Supabase on AWS to Supabase SaaS

[gllona]

Hello,

We run a self-hosted Supabase instance installed on AWS using the CloudFormation repo https://github.com/gllona/supabase-on-aws , which I forked from https://github.com/supabase-community/supabase-on-aws (and did some minor changes trying to revive the Studio).

We are using Supabase mainly for auth purposes.

However, the mentioned repo from supabase-community is no longer maintained, which is risky for us due to lack of bug patches. Also, AWS has announced its end of support for Lambda functions running nodejs v18.x, which the Supabase components in the mentioned repo use.

Then I need to migrate my current Supabase on AWS instance to Supabase SaaS (new project in EU region). In this migration, I need to preserve all the current PostgreSQL database data, including everything related to the auth module, existing users, etc.

What could be the best migration strategy? I think I can not simply create a new Supabase SaaS instance, and replace the content of the "auth" schema with our current content from Supabase on AWS, because there could be schema differences due to Supabase version changes.

These are the Supabase components versions I use on AWS:

• public.ecr.aws/supabase/gotrue:v2.139.1
• public.ecr.aws/supabase/postgrest:v12.0.2
• public.ecr.aws/supabase/realtime:v2.25.61
• public.ecr.aws/supabase/storage-api:v0.46.5
• public.ecr.aws/supabase/imgproxy:v1.2.0
• public.ecr.aws/supabase/postgres-meta:v0.75.0

Any help is greatly appreciated.

Thank you,

Gorka Llona