dima/supabase
1
0 Fork 0
mirror of https://github.com/supabase/supabase.git synced 2026-10-14 05:39:11 +03:00
Code Issues Packages Projects Releases Wiki Activity

fix lints

Browse Source
This commit is contained in:
PLyn committed 2025-08-25 10:09:50 -05:00
1 parent 444795edfb
commit f1a8900bbe
1 file changed
+2 -2
Download Patch File Download Diff File Expand all files Collapse all files
apps/docs/content/guides/platform/migrating-within-supabase.mdx
+2 -2
View File
@@ -12,7 +12,7 @@ to another project feature](/docs/guides/platform/clone-project).
- **Project migration only migrates the Postgres database** and anything else will need to be re-configured.
### Pre-Migration Checklist
### Pre-Migration checklist
<Accordion
@@ -154,7 +154,7 @@ If you already have the database backup, skip to the Restore project step.
### Migrate Storage
The new project has the old project's Storage buckets, but the Storage objects need to be migrated manually. If you have your storage objects locally (eg 90 day paused projects), migrate the storage objects to the new project using this [google colab script](https://colab.research.google.com/github/PLyn/supabase-storage-migrate/blob/main/Supabase_Storage_migration.ipynb).
The new project has the old project's Storage buckets, but the Storage objects need to be migrated manually. If you have your storage objects locally (e.g. 90 day paused projects), migrate the storage objects to the new project using this [Google Colab script](https://colab.research.google.com/github/PLyn/supabase-storage-migrate/blob/main/Supabase_Storage_migration.ipynb).
If the old project is still active, use this script to move storage objects from one project to another: