How to combine 2 Supabase projects?
storageauthHi everyone! 
I'm looking for advice on combining two Supabase projects into one
- BC (target project) is the largest project, that uses RLS, uses Azure as the auth provider and doesn't use Supabase Storage
- IS (to be merged into BC) doesn't use RLS, uses the email auth provider (magic links) and uses Supabase Storage for user-uploaded images
The goal is to move all IS data into BC
I also would like to accomplish the following things:
- IS users should keep their accounts and data and shouldn't need to create a new account or lose access
- IS users must still be able to log in via magic links
- If an IS user and a BC user share the same email, I’d like to merge them into a single
- IS also has its own
I’m aware that some level of re-authentication may be unavoidable, but I’d like to avoid recreating user accounts or breaking existing user–data relationships if possible.
I'm especially unsure about
- Best practices for merging
- How to merge identities/user_metadata/app_metadata safely (which row to pick as canonical, what to copy/merge, ...)
- RLS gotchas: roles/claims/policies that must be transferred or adapted for imported users
- Recommended tools/approach for the storage migration when I copy IS's user image into BC storage while preserving paths/DB refs and access control
Any recommended patterns, tools or gotchas for doing this kind of merge?
Thanks in advance!
I'm looking for advice on combining two Supabase projects into one
- BC (target project) is the largest project, that uses RLS, uses Azure as the auth provider and doesn't use Supabase Storage
- IS (to be merged into BC) doesn't use RLS, uses the email auth provider (magic links) and uses Supabase Storage for user-uploaded images
The goal is to move all IS data into BC
I also would like to accomplish the following things:
- IS users should keep their accounts and data and shouldn't need to create a new account or lose access
- IS users must still be able to log in via magic links
- If an IS user and a BC user share the same email, I’d like to merge them into a single
auth.users- IS also has its own
usersusers.idauth.users.idI’m aware that some level of re-authentication may be unavoidable, but I’d like to avoid recreating user accounts or breaking existing user–data relationships if possible.
I'm especially unsure about
- Best practices for merging
auth.users- How to merge identities/user_metadata/app_metadata safely (which row to pick as canonical, what to copy/merge, ...)
- RLS gotchas: roles/claims/policies that must be transferred or adapted for imported users
- Recommended tools/approach for the storage migration when I copy IS's user image into BC storage while preserving paths/DB refs and access control
Any recommended patterns, tools or gotchas for doing this kind of merge?
Thanks in advance!
