Duplicate a project
Copy a project, choose between sharing and copying its database, and see what a copy gets.
Duplicating makes a second project from an existing one: a place to experiment, or a starting point for a similar app. The choice that matters most is what the copy does with the database.
Duplicate a project
- 1
Open Duplicate
Open the project on floot.com, click the project name dropdown in the top-left, and choose Duplicate. Duplicating needs a paid plan, and is refused while a hosting balance is unpaid.
- 2
Name the copy
Give it a name that tells the two apart, such as "Shop (copy)".
- 3
Choose a database option
If the project has a Floot database, Database Options offers three choices, described below. Share database is selected by default.
- 4
Click Duplicate Project
The copy opens as a new, private project in your account.
Share or copy the database
| Option | What the copy gets | Use it for |
|---|---|---|
| Share database | The same live database as the original. Both projects read and write the same rows, and a table changed in one is changed for both | Two apps that are meant to work on the same data. Never for testing |
| Duplicate schema only | A new database of its own, with the same tables and no rows | A clean start with the same structure |
| Duplicate with full data | A new database of its own, holding a copy of the data as it is now. Nothing syncs afterwards, so the two drift apart | An experiment you may throw away |
Share database is the default
If you click through without choosing, the copy works on your real data: a test order, a deleted row or a changed column in the copy is the same change in the original. Pick one of the two Duplicate options whenever the copy is for testing.
The choice is offered only for your own project. If you duplicate someone else's public project, you get its code and a new, empty database with the same tables.
What the copy gets
- Copied
- The code (pages, components, backend and static files), its packages, your system prompt and design prompt, the project icon, the files in the project's storage, and the scheduled jobs. A Private only project stays private only.
- Shared with the original
- Your connected integrations. The copy is connected to the same API keys and outside services as the original, and they are live from the first moment. With Share database, the database too.
- Made fresh for the copy
- The secret that signs your app's sign-in sessions, Floot's built-in sign-in providers, the Google and Microsoft account connections, and push notification keys. People signed in to the original are not signed in to the copy.
- Not carried over
- The
floot.appaddress and custom domains (the copy starts unpublished), app store connections and the mobile app ID (the copy gets its own), collaborators, invited users, checkpoints and history, connections to your other apps, email domains, the site description, the splash screen, and the Enable Pre-rendering switch.
When you duplicate someone else's project, integrations are copied as empty slots: you set up your own keys.
Schedules in a copy
- Scheduled jobs are copied, but they wait. They do not run in the copy until you publish it, unless Dev Schedules is on in the copy's Services → Schedules.
- Once the copy is published, its jobs run on the same timetable as the original's. With shared integrations or a shared database, both apps then do the work: two reminder emails, two syncs. Switch off or delete the jobs you do not want in the copy before you publish it.
- Recurring background tasks your app created while running come along only with Duplicate with full data, and start when the copy is first published. One-off delayed tasks are never copied.
Cost
There is no charge for making a copy. A copy with its own database is a second database, and each project's database, storage and published app count toward hosting as usual. Delete a copy you no longer need.