Storage Buckets Migration

Supabase Storage lets you store and serve files like images, documents, and videos. The Storage Buckets component migrates your buckets, the files inside them, and the access policies that control who can read or write those files.

What Gets Migrated

When you select the Storage Buckets component, Stack2X transfers:

• Bucket definitions -- Each bucket is recreated on the destination with the same name, public/private setting, and file size limits.
• Stored objects -- Every file and folder inside each bucket is copied to the destination. File metadata such as content type and cache settings are preserved.
• Bucket policies -- RLS policies attached to storage buckets are migrated so that access rules stay consistent.
• Folder structure -- The directory hierarchy within each bucket is maintained exactly as it exists on the source.

Plan Availability

Storage Buckets migration is available on the Starter plan and above. It is not included in the Free tier.

Tips and Considerations

• File transfer time. Storage migration speed depends on the total size of your files. A bucket with thousands of images will take longer than one with a handful of documents. Stack2X transfers files in parallel to speed things up and shows real-time progress.
• Storage limits. Make sure the destination Supabase project has enough storage capacity for all your files. Stack2X checks available space before starting the transfer and will warn you if there is not enough room.
• Public URLs change. If your application references storage files by their full Supabase URL, those URLs will change because the destination has a different project reference. Update your application code or database references accordingly.
• Large files. Stack2X supports files of any size. Large files are streamed in chunks to avoid timeout issues.
• Pair with RLS. If your bucket policies reference database tables or auth functions, make sure the corresponding components (Database Schema, Auth Users) are also included in the migration.