Duplicate Project

[Zegoverno]

Update: we announced Supabase Branching featuring multiple environments of your project so you can experiment with your database and change its data safely during Launch Week X.

You can follow this GitHub Discussion for the latest: https://github.com/orgs/supabase/discussions/18937.

If you still need an easy way to duplicate your project please drop a comment below describing your use case, what exactly you wish to clone from your existing database (e.g. only schemas, schemas and all data, etc.), and any Supabase products you will continue using after duplicating your project.

---

Would be awesome to duplicate projects and also choose to copy just the database schemas/structure or also migrate all data.

[burggraf]

You can duplicate a project using the instructions here: Migrate the Database

If you want to only duplicate the schema and not the data, you can use pg_dump -s postgres.

[phillipmohr]

It seems like the docs have changed... I was able to duplicate my project with the help of the previous instructions, but the step-by-step list is now gone as it seems. The docs don't seem to explain how to duplicate a project anymore, if I am not mistaken. Plus, I don't know how to access the "Table View" which is mentioned in the docs and I'm also not sure if it will help me to duplicate my entire project...

[GaryAustin1]

The migration method is here now: https://supabase.com/docs/guides/database/migrating-between-projects
I think it is different than before, and have not tried this method.

[paulin-crtn]

I tried https://supabase.com/docs/guides/database/migrating-between-projects but it is deleting everything :(

I would like to duplicate my production project to a staging project (same data, same storage).

Is it achievable ?

[tonyneel]

I would like to create a staging environment as well but am worried by @paulin-crtn comment. Any guidance?

[logemann]

would also like to see a "duplicate" project button in the supabase UI. Would most likely also drive sales.

[tarkanlar]

That would be an amazing feature

[alitnk]

this would be super helpful!

[danarchos]

To be able to easily create new environment, one for testing, one for development and one for production would be a dream

[99power]

Yeah this is so necessary. Coming from mysql where you can just import/export and you're done, this feels really cumbersome.

[sjmog]

Agree – this feels super-necessary (see e.g. Render for how it could be handled)

[johndpope]

Given the in the face alerts for RLS / I need this - don't want to spend a day recreating environment.
I'm even a paying customer. I have an older snapshot - but it's now out of sync - was shut down for long time.
if you could make easier here to sync to an existing live database - that would also suffice.

UPDATE -

wait a second - we have this
https://supabase.com/docs/guides/integrations/snaplet

UPDATE 2 - can you guys buy this snaplet product / company ?/ it should be out of the box.

[adhambadr]

So tried snaplet, and it messed up all the foreign key relationships, practically any foreign table query is 500 error. Its really tedious to clone a project, how are we supposed to maintain a local and live environments in sync ?!

(edited by @MildTomato to remove profanity)

[caseybaggz]

Same. I had to literally make my back-up DB production and now have to figure out how to duplicate my (now) production to a new backup...

[jmcannon]

I'd also love a "Copy this Project" button.

[Angus-Moore-Dev]

I think it would also be cool to have updates be able to be made to different projects (based on their version (say one project has a development, staging and production environment)), similar to how Github handles pull requests.

Say I make some relationship / schema changes to a few tables in development or how the storage bucket RLS works, I would like to be able to merge all of those changes from development into the production database.

Not sure how that would realistically work, just pie in the sky thinking ¯_(ツ)_/¯

[peachp]

Neither Snaplet nor supabase db dump works with our data. Snaplet fails at creating a snapshot and the supabase CLI dump creates broken SQL INSERTs which cannot be restore via psql or supabase db reset

[peachp]

To clarify, our data is not the cleanest (long TEXT values with all sorts of characters), but it worked just fine in legacy system and initially moving it to Supabase using the official JS client worked without issues.

[slawton3]

Anyone know if a "Duplicate project" button/feature is in the pipeline for a future release? I would instantly and gladly pay for this feature.

[saltcod]

Hey there! Some questions to help guide the way here.

How would you see this working?
What is the pain point this would solve? Does branching solve any of this pain?
Why do you need it? What would be the benefit over just using pg_dump as Mark has suggested?

[Gregg-Casey]

@saltcod please read the thread above. All of your questions are answered there.

[didymu5]

I'd like this feature as well!

[saltcod]

Hey there! Some questions to help guide the way here.

How would you see this working?
What is the pain point this would solve? Does branching solve any of this pain?
Why do you need it? What would be the benefit over just using pg_dump as Mark has suggested?

[Gregg-Casey]

@saltcod please read the thread above. All of your questions are answered there.

[alexrabin]

+1

[shane-downes]

Support for prod and dev environments would be awesome.

[akrv]

need.

for now: after few copy paste, worked great and then setup hooks and triggers manually

https://supabase.com/docs/guides/platform/migrating-and-upgrading-projects

[Shawns2759]

plz

[pooriaarab]

is this feature being added @burggraf

[saltcod]

Hey there! Some questions to help guide the way here.

How would you see this working?
What is the pain point this would solve? Does branching solve any of this pain?
Why do you need it? What would be the benefit over just using pg_dump as Mark has suggested?

[zozoheir]

Also adding to this. I find it unbelievable the amount of time saved by Supabase, but then wasted b/c the most common practice (dev/prod/staging envs) is not supported. Cmon...Im not a paying user but I would happily pay for this.

[saltcod]

Hey there! Some questions to help guide the way here.

How would you see this working?
What is the pain point this would solve? Does branching solve any of this pain?
Why do you need it? What would be the benefit over just using pg_dump as Mark has suggested?

[MildTomato]

Would be awesome to duplicate projects and also choose to copy just the database schemas/structure or also migrate all data.

Update from the Supabase team — We are looking into this. We realize this feature request has been here for a while and it has gathered a lot of votes.

Due the complexity of amount of services, each with their own config, data, deployments, we can't offer in the immediate short term a service to duplicate everything in a Supabase project just yet. so we'll think of this as a medium to long term goal.

However, that shouldn't stop us making at least some progress that can satisfy some use cases. So we can start with duplicating the database schema, and we'll aim to roll that out fairly quickly as an easy action you can take in the Dashboard (and probably CLI).

Although we can't promise any timeframes, Database data duplication is probably something we'll consider next, and then we'll start tackling the issues with Storage duplication, Function deployments and so on.

[jzambranoavvy]

Let's goooooo!

[logemann]

Its ok now.

…

On Sun, Oct 15, 2023 at 9:39 AM Jonathan Summers-Muir < ***@***.***> wrote: Would be awesome to duplicate projects and also choose to copy just the database schemas/structure or also migrate all data. Update from the Supabase team — We are looking into this. We realize this feature request has been here for a while and it has gathered a lot of votes. Due the complexity of amount of services, each with their own config, data, deployments, we can't offer in the immediate short term a service to duplicate *everything* in a Supabase project just yet. so we'll think of this as a medium to long term goal. However, that shouldn't stop us making at least some progress that can satisfy some use cases. So we can start with duplicating the database schema, and we'll aim to roll that out fairly quickly as an easy action you can take in the Dashboard (and probably CLI). Although we can't promise any timeframes, Database data duplication is probably something we'll consider next, and then we'll start tackling the issues with Storage duplication, Function deployments and so on. — Reply to this email directly, view it on GitHub <#5930 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AACUR4PL4VJI54AJZGIPCQLX7OHMPAVCNFSM5QZQVD3KU5DIOJSWCZC7NNSXTOKENFZWG5LTONUW63SDN5WW2ZLOOQ5TOMRYGM4DSMQ> . You are receiving this because you commented.Message ID: ***@***.***>

-- regards marc logemann https://www.linkedin.com/in/logemann/

[williamli]

I think Supabase's upcoming Branching feature will help to address this.

[Gregg-Casey]

The branches aren't meant to be permanent so I am not sure about that @williamli .

[mounikpatel]

I am also looking for a similar implementation where I can copy my whole database (minus the data) from dev env to prod env. Both environments are on different user accounts as well. I would really appreciate any help.