Getting started

Before you start

SupaClone is designed for copying a Supabase project into a fresh, disposable target project. Do not point the target connection at production or at a project that already contains important application data.

You need:

• Access to the source Supabase project.
• A fresh target Supabase project.
• Database connection strings for source and target.
• Supabase OAuth access when cloning Storage, Edge Functions, project settings, or Auth configuration.

Recommended first clone

Start with a structure-only clone before copying table data or optional managed resources. This validates the schema, restore plan, permissions, and target connection with the smallest blast radius.

1. Create an empty target Supabase project.
2. Connect SupaClone to the source and target projects.
3. Select the schemas and resources you want to clone.
4. Keep table data off for the first run if you are testing a new project.
5. Review the clone summary before execution.
6. Run the clone.
7. Read the clone report and manual steps.

Target project requirements

The target project should be fresh and empty. SupaClone assumes it can create schemas, tables, constraints, functions, triggers, policies, and optional managed resources without colliding with existing application objects.

For Storage file cloning, target buckets must be empty. If an existing bucket contains files, SupaClone stops instead of merging object data into an unknown state.

What the clone report tells you

Every run produces a report with cloned, skipped, failed, manual, and notice items.

• Cloned means SupaClone wrote or restored the resource.
• Skipped means the resource was intentionally left out.
• Failed means SupaClone attempted the resource and could not complete it.
• Manual means you need to finish a security-sensitive or platform-limited step yourself.
• Notices call out configuration differences or risks that deserve review.

Safe rollout path

Use this sequence when cloning a serious project:

1. Run structure only.
2. Add selected table data.
3. Add Storage buckets and policies.
4. Add Edge Functions.
5. Review Auth settings and re-enter secrets manually.
6. Run your application test suite against the target.
7. Only then promote the target into a staging or migration workflow.