Hi, I’m pretty new to Fibery. I want to create an entity “subtype” of an existing database. I can either: update the original database by adding new fields that are specific to the subtype, and a field that will label new entities with the name of the subtype. This reduces redundancy but makes …

Now you can duplicate field to another database [image] 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 Changelog This release has several qua…

I was hoping someone would offer a quick reply or tell me where to search for the relevant info. Though I can appreciate the high-level discussions among the experienced/power users on here, is anybody from Fibery monitoring the help channel for more basic questions from new users? I’ve attended t…

Hi! Regarding the example above, I can’t suggest a good solution :slight_smile: As for me, everything is based on the use case, that you have. What is “subtype”? What kind of data are we talking about?What kind of fields are we discussing? From a technical perspective, both suggested solutions ar…

[image] jbreichel: There should be a few fields that are copied over from the original database to the new database. Is there a way to do this, or do I need to re-create all new fields manually? I understand you want help with a one -time conversion of labeled entities into new database entit…

Thanks for responding, both. I’m trying deliberately not to specify a particular use case, because I’m searching for a general principle or convention. If you have two similar-ish types of entities (for example, “customers” and “investors” are both subtypes of “people”), should they be in one larg…

[image] jbreichel: Is there any way to copy a field from one database to a different database? Unfortunately not. And the entire “complexifying” issue you’re talking about here is definitely a big concern for me and some other folks here as well. [image] jbreichel: For example, if I have…

Thanks, Oshyan. I didn’t know I could save a custom template. Is this the thread you’re referring to, with a kind of workaround to accomplish that? It occurs to me that the “heavy” solution to keep certain fields in sync across different spaces and databases by making them into their own database…

Also, exporting the data doesn’t include the views? It is time-consuming to configure these. No way to back them up?

[image] jbreichel: the csv files that are created exclude all of the relations This isn’t correct. The CSV export includes unique ids for each entity, and where one entity is linked to another, this is shown by including the id under that relation column.

[image] jbreichel: if I have a multi-select field called “category” and there are 10 different choices, it is painful to manually recreate the same field in a new database, and it would be much easier to have a way to copy the field including its choices from one database into a second database. …

I do now see that the relation fields are included in the backup! The fields in the csv export are in a different order than the fields in the original, and it hadn’t occurred to me to search out of order (I’m a little curious why, but no bother). That said, the entries from linked entities are li…

Copying fields between databases

Get Help

mdubakov April 17, 2025, 1:01pm 17

Now you can duplicate field to another database

Topic		Replies	Views
Convert select options to database Ideas & Features flexible-domain	2	48	February 26, 2026
May 29, 2025 / Import a new Database, Require values in a Field to be unique, Add images in bulk on Whiteboard Changelog	20	555	June 19, 2025
CHANGELOG: April 14 / Duplicate entity, Audit Log for all users, Convert entity improvements Changelog	24	2157	June 11, 2021
Separate a database into two different business Get Help	6	82	October 16, 2025
Convert select fields into regular databases Ideas & Features flexible-domain	24	171	October 30, 2025

Copying fields between databases

Related topics