Supabase and Postgres
Move a Supabase project into Ahamo
Bring a Supabase project's rows, accounts and Storage files into your published app, check the counts, and retry what didn't move.
On this page
Move from Supabase copies a Supabase project's tables, the people who sign in and, if you like, its Storage files into your published app, then checks that the counts match. Ahamo only reads your Supabase project and never changes it. Passwords move with each person, so they sign in as before.
When to use it
- You want Ahamo to run the app's data and sign-in from now on.
- You rebuilt a Supabase app in Ahamo and need its existing data and users.
How to use it
With your Supabase connection (nothing to paste)
- Connect Supabase under Connectors with the project's ID. The connect screen lists what Ahamo may read and says Ahamo only reads your project; it never changes it.
- Build the app's tables and file kinds to match your project, and publish it.
- Open Runtime › Data › Move from Supabase and select Check next to your project under Use your Supabase connection.
- Fix anything under Fix these first, then select Move into my App.
Ahamo reads the project through your connection, as Supabase's read-only database user, so Supabase itself refuses any change. Files move with short-lived download links Supabase Storage signs; nothing is pasted or stored.
When you connect Supabase for a new app, Ahamo first copies the project's rows into the app's preview data, so the preview shows your real data. People and files move into the published app when you publish.
A Supabase connection made before this way existed can't move data, and the card says Reconnect Supabase under Connectors. Reconnect, or paste the connection string as below.
With a connection string
- Build the app's tables and file kinds to match your project (the build AI can do this from a description or an imported repository), and publish it.
- Open Runtime › Data › Move from Supabase.
- Under Or paste a connection string, paste the Supabase connection string. In Supabase, select Connect, choose Session pooler, and copy it with your database password.
- For files, add the Storage keys from Storage › S3 › New access key; enter the Access key ID, Secret access key and Region.
- Select Check my project. What moves lists rows per table, people and files per bucket; fix anything under Fix these first and check again.
- Select Move into my App. It runs Rows, People, Files and Counts; you can leave the page.
The card then says Moved, and the counts match, with each table's rows in the app and in Supabase. In your next message, the build AI offers to update tables that still point at files in Supabase.
Ahamo keeps the connection string and keys encrypted, never shows them again, and deletes them when the move is done or given up.
Who signs in another way
With your Supabase connection, the check also lists the sign-in methods your project uses besides passwords (such as Google or GitHub). Turn the same methods on in the app, or those people use Forgot password to set one.
What moves, and what doesn't
| Moves | |
|---|---|
| Rows | Every table that the app also has; others stay in Supabase |
| People with a password | Yes; they sign in with their Supabase password |
| People who used a link or a provider, or never confirmed their email | Their accounts move; they use Forgot password the first time |
| Passkeys and authenticator apps | Not moved (apps don't offer them yet) |
| Storage files | Each bucket into the app's file kind of the same name |
| Edge Functions | No; import the repository to see which can become server functions |
If something stops
- Retry goes on from where the move stopped; rows are copied again without duplicates.
- Give up ends the move and deletes the stored connection string and keys. Anything that already moved stays in the app.
- Files that didn't move are listed with a reason and a fix. Apply the fix, paste the Storage keys again and select Retry refused files, and only those files move.
Plans and limits
The same on every plan; the app's file storage limits apply to the moved files.
| Rule | Value |
|---|---|
| Into | The published app's shared data, on Ahamo's built-in database |
| A check is valid for | 1 day |
| Refused files listed | Up to 100 |
| Who | People who can publish the app; copying into the preview's data needs only edit access |
Troubleshooting
"Publish the App first." The move goes into the published app. Publish it, then check again.
"This App already keeps its data in your own Postgres database…". There is nothing to move into Ahamo; see Your own Postgres.
"Some tables have fewer rows in the App than in Supabase." Select Retry.
"Your Supabase connection was made before Ahamo could move data with it." Reconnect Supabase under Connectors, then check again; or paste the connection string.
"… files stay in Supabase Storage because your Supabase connection can't read the project's secret key." Reconnect Supabase under Connectors and check again; the rows and people move either way.
A file is "Larger than the … file kind allows". Ask the build AI to raise that file kind's size limit, publish, then Retry refused files.