# \[DONE\] Copy / Duplicate a Workflow **URL:** \ **Category:** Ideas & Features\ **Created:** [December 14, 2022, 3:45am UTC](https://community.fibery.io/t/done-copy-duplicate-a-workflow/3698 "2022-12-14T03:45:59Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![B\_Sp](https://avatars.discourse-cdn.com/v4/letter/b/e8c25b/32.png) [@B\_Sp](https://community.fibery.io/u/B_Sp)\ **Post date:** [December 14, 2022, 3:45am UTC](https://community.fibery.io/t/done-copy-duplicate-a-workflow/3698/1 "2022-12-14T03:45:59Z")
Hi, I haven’t seen this requested yet so I thought I’d add the request. If it’s something that is already doable and I just haven’t figured out how to do it, please feel free to close this request out! I’d like to be able to duplicate a workflow I created between db’s. With a close to 3 yr old Fibery instance my team uses, we have developed some fairly good workflows in certain db’s - 8- 10 states, custom icons and colors (which are great features of workflow!). We have boards that won’t work unless certain types (dbs) have the exact same workflows, because we use columns for states. Occasionally we create a new db that’s related to an existing one with one of these advanced workflows. When this happens, in order to duplicate the workflow from the existing db, it can be a 6- 8 minute process to manually make sure all the states are named the same, have the same icons, and color. If you could do this with a click of a button that would be so much easier! With an advanced Fibery instance it’s not something that is going to be an issue for my particular team as we don’t have a lot of db’s to add, but I could see a new team wanting to do, for example, a dev board and needing bugs, stories, tasks, indcidents - say 3 + dbs in one workflow - , that could use this quick ability to duplicate the workflow attribute. Basically a big time saver when setting up a new Fibery instance. Thanks guys! ---
**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\ **Post date:** [December 14, 2022, 6:36am UTC](https://community.fibery.io/t/done-copy-duplicate-a-workflow/3698/2 "2022-12-14T06:36:14Z")
It sounds like you should use a fully-fledged database for your workflow states, rather than the native workflow field. Then it can be reused for multiple databases across the workspace. ---
**Author:** ![Matt\_Blais](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/matt_blais/32/1464_2.png) [@Matt\_Blais](https://community.fibery.io/u/Matt_Blais)\ **Post date:** [December 14, 2022, 3:47pm UTC](https://community.fibery.io/t/done-copy-duplicate-a-workflow/3698/3 "2022-12-14T15:47:32Z")
Can you do that and still have all the inbuilt Workflow features (Assignments, notifications, etc)? ---
**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\ **Post date:** [December 14, 2022, 4:13pm UTC](https://community.fibery.io/t/done-copy-duplicate-a-workflow/3698/4 "2022-12-14T16:13:20Z")
The native workflow state automatically includes notifications, so if you made a new DB you’d need to create automations to do this. The only other difference is that the native workflow states have the ‘completion/tick’ icon included. There’s no interaction between workflow and assignees. ---
**Author:** ![ebell](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/ebell/32/1293_2.png) [@ebell](https://community.fibery.io/u/ebell)\ **Post date:** [September 30, 2023, 10:41pm UTC](https://community.fibery.io/t/done-copy-duplicate-a-workflow/3698/5 "2023-09-30T22:41:39Z")
@Chr1sG , I created a seperate database for a ‘reusable’ workflow state. However, they are displayed out of order. Meaning, the drop down in a table/grid view show the options in Alphabetical order (rather than the state order). Is there a work around to show the proper order on the table? Note the Board view shows the states in the proper order. As an example, the Table view shows as: - Beta - Done - Evergreen - Icebox - In Process - Next …etc I would like to to show: - Icebox - Open - Next - In Process …etc ---
**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\ **Post date:** [October 1, 2023, 7:35am UTC](https://community.fibery.io/t/done-copy-duplicate-a-workflow/3698/6 "2023-10-01T07:35:23Z")
When you click on the cell to choose a state, you will see a funnel icon and a double arrow icon. Click the double arrow, and you’ll see that the default sort order is by name. If you remove that sort option, the choices will be shown in rank order (which is probably what you need). If you need to change the rank order, create a view (list, grid, board) of the state options, and drag and drop to reshuffle. ---
**Author:** ![ebell](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/ebell/32/1293_2.png) [@ebell](https://community.fibery.io/u/ebell)\ **Post date:** [January 10, 2024, 7:13pm UTC](https://community.fibery.io/t/done-copy-duplicate-a-workflow/3698/7 "2024-01-10T19:13:44Z")
@Chr1sG: It works, thanks! ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [April 17, 2025, 1:00pm UTC](https://community.fibery.io/t/done-copy-duplicate-a-workflow/3698/8 "2025-04-17T13:00:57Z")
Now you can duplicate fields to another database > [@April 17, 2025 / leaf\_fluttering\_in\_wind Duplicate Field, Improve Entity creation flow when entity name is generated via a formula, Multi-accounts in Google calendar](https://community.fibery.io/t/april-17-2025-duplicate-field-improve-entity-creation-flow-when-entity-name-is-generated-via-a-formula-multi-accounts-in-google-calendar/8625): > > This release has several quality of life improvements for creators and users. Enjoy! leaf_fluttering_in_wind Duplicate Field Imagine you setup a long and beautiful single-select field for Tasks database and suddenly realise that you need it in Bugs database as well. You had to re-create it from scratch… No more! Now you can quickly duplicate basic fields (including single- and multi-selects) into another database. squid Improve Entity creation flow when entity name is generated via a…