mirror of
https://github.com/supabase/supabase.git
synced 2026-07-03 00:24:25 +08:00
b0a42fda53
also removes tips for changing timezone and resetting project password and just point to the respective guides we have for those.
98 lines
3.3 KiB
Plaintext
98 lines
3.3 KiB
Plaintext
---
|
|
id: migrating-between-projects
|
|
title: 'Migrating Between Projects'
|
|
description: Migrate data from one project to another
|
|
---
|
|
|
|
Migrating projects can be achieved using standard PostgreSQL tooling. This is particularly useful for older projects (e.g. to use a newer Postgres version).
|
|
|
|
## Before you begin
|
|
|
|
- Make sure [Postgres](https://www.postgresql.org/download/) is installed so you can run `psql` and `pg_dump`.
|
|
- Create a new Supabase project.
|
|
- If you enabled Database Webhooks on your old project, enable it on your new project.
|
|
- Store the old project's database URL as `$OLD_DB_URL` and the new project's as `$NEW_DB_URL`.
|
|
|
|
## Migrate the database
|
|
|
|
1. Run `ALTER ROLE postgres SUPERUSER` in the _old_ project's SQL editor
|
|
2. Run `pg_dump --clean --if-exists --quote-all-identifiers -h $OLD_DB_URL -U postgres > dump.sql` from your terminal
|
|
3. Run `ALTER ROLE postgres NOSUPERUSER` in the _old_ project's SQL editor
|
|
4. Run `ALTER ROLE postgres SUPERUSER` in the _new_ project's SQL editor
|
|
5. Run `psql -h $NEW_DB_URL -U postgres -f dump.sql` from your terminal
|
|
6. Run `TRUNCATE storage.objects` in the _new_ project's SQL editor
|
|
7. Run `ALTER ROLE postgres NOSUPERUSER` in the _new_ project's SQL editor
|
|
|
|
## Migrate storage objects
|
|
|
|
This script moves storage objects from one project to another. If you have more than 10k objects, we can move the objects for you. Just contact us at [support@supabase.io](mailto:support@supabase.io).
|
|
|
|
```js
|
|
const { createClient } = require('@supabase/supabase-js')
|
|
|
|
const OLD_PROJECT_URL = 'https://xxx.supabase.co'
|
|
const OLD_PROJECT_SERVICE_KEY = 'old-project-service-key-xxx'
|
|
|
|
const NEW_PROJECT_URL = 'https://yyy.supabase.co'
|
|
const NEW_PROJECT_SERVICE_KEY = 'new-project-service-key-yyy'
|
|
|
|
;(async () => {
|
|
const oldSupabaseRestClient = createClient(
|
|
OLD_PROJECT_URL,
|
|
OLD_PROJECT_SERVICE_KEY,
|
|
{
|
|
schema: 'storage',
|
|
}
|
|
)
|
|
const oldSupabaseClient = createClient(
|
|
OLD_PROJECT_URL,
|
|
OLD_PROJECT_SERVICE_KEY
|
|
)
|
|
const newSupabaseClient = createClient(
|
|
NEW_PROJECT_URL,
|
|
NEW_PROJECT_SERVICE_KEY
|
|
)
|
|
|
|
// make sure you update max_rows in postgrest settings if you have a lot of objects
|
|
// or paginate here
|
|
const { data: oldObjects, error } = await oldSupabaseRestClient
|
|
.from('objects')
|
|
.select()
|
|
if (error) {
|
|
console.log('error getting objects from old bucket')
|
|
throw error
|
|
}
|
|
|
|
for (const objectData of oldObjects) {
|
|
console.log(`moving ${objectData.id}`)
|
|
try {
|
|
const { data, error: downloadObjectError } =
|
|
await oldSupabaseClient.storage
|
|
.from(objectData.bucket_id)
|
|
.download(objectData.name)
|
|
if (downloadObjectError) {
|
|
throw downloadObjectError
|
|
}
|
|
|
|
const { _, error: uploadObjectError } = await newSupabaseClient.storage
|
|
.from(objectData.bucket_id)
|
|
.upload(objectData.name, data, {
|
|
upsert: true,
|
|
contentType: objectData.metadata.mimetype,
|
|
cacheControl: objectData.metadata.cacheControl,
|
|
})
|
|
if (uploadObjectError) {
|
|
throw uploadObjectError
|
|
}
|
|
} catch (err) {
|
|
console.log('error moving ', objectData)
|
|
console.log(err)
|
|
}
|
|
}
|
|
})()
|
|
```
|
|
|
|
## Caveats
|
|
|
|
- The new project will have the old project's Storage buckets, but not the objects. You will need to migrate Storage objects manually.
|