Creating a Clone

This guide walks you through every step of the cloning wizard.

Prerequisites

  • At least one connected Supabase account
  • A source project (the one you want to copy)
  • A target project (the one that will receive the copy)

Step 1: Open the Wizard

From the dashboard, click New Clone. The cloning wizard opens with multiple steps.

Step 2: Choose the Source Project

Select the project you want to clone. The selector displays:

  • The project name
  • The organization it belongs to
  • The region

If you have multiple connected accounts, you can switch between them.

Step 3: Choose the Target Project

Select the destination project. You can also create a new project directly from the wizard.

Important: The target project will be modified. If tables with the same name already exist, new columns will be added and data will be inserted.

Step 4: Preview

Twins analyzes the source project and presents a summary:

  • Tables — name, number of columns, number of rows
  • Functions — name and language
  • Triggers — name and associated table
  • RLS Policies — name and table
  • Edge Functions — list of deployed functions
  • Storage — buckets and file count
  • Users — total count
  • Warnings — large tables, missing extensions, potential conflicts

See Preview for more details.

Step 5: Configure Options

Choose exactly what you want to clone. Everything is enabled by default, but you can:

  • Disable individual components (e.g., skip storage cloning)
  • Limit the number of rows cloned per table
  • Enable backup so you can restore later

See Clone Options for the full list.

Step 6: Start the Clone

Click Start Clone. You are redirected to the monitoring page.

What Happens Behind the Scenes

  1. A clone job is created
  2. Components are processed in order (schema, data, functions, etc.)
  3. Progress is displayed in real time — no need to refresh
  4. A report is generated at the end

Step 7: Monitor Progress

On the monitoring page, you can see:

  • An overall progress bar
  • The status of each component (pending, in progress, completed, failed)
  • The elapsed time
  • Any error messages

See Monitoring Progress for more details.

Step 8: Review the Results

Once the clone is complete:

  • The report summarizes what was cloned successfully and what failed
  • You can run a verification to compare source and target
  • You can re-run a clone from the same twin

Common Use Cases

Full Migration

Enable everything, no row limit. To fully duplicate a project.

Schema-Only Update

Enable: schema, views, functions, triggers, RLS policies. Disable: data, storage, users, Edge Functions.

To synchronize structural changes without touching the data.

Data Refresh

Enable: data only. Disable: everything else.

To update staging data from production when the schema is already up to date.

Lightweight Staging

Enable everything, row limit: 1,000. To create a copy with a subset of data for testing.

Next Steps

PreviousConnecting AccountsNextPreview