# \#import

**URL:** https://community.fibery.io/tag/import/15.md

[Latest](https://community.fibery.io/latest.md) · [Categories](https://community.fibery.io/categories.md) · [Tags](https://community.fibery.io/tags.md)

---

## [Add created by to CSV import as the person who did the import](https://community.fibery.io/t/add-created-by-to-csv-import-as-the-person-who-did-the-import/10477)

<div class="topic-metadata">

**Author:** [@RonMakesSystems](https://community.fibery.io/u/RonMakesSystems)\
**Replies:** 3\
**Last updated:** [September 18, 2026, 8:41pm UTC](https://community.fibery.io/t/add-created-by-to-csv-import-as-the-person-who-did-the-import/10477 "2026-09-18T20:41:16Z")

</div>

Since some items were created via CSV Import, they don’t include the Created By field. Setting it to the person who imported the data would be ideal.

---

## [\[DONE\] Create related entity if doesnt exist on CSV import](https://community.fibery.io/t/done-create-related-entity-if-doesnt-exist-on-csv-import/9783)

<div class="topic-metadata">

**Author:** [@RonMakesSystems](https://community.fibery.io/u/RonMakesSystems)\
**Replies:** 1\
**Last updated:** [February 12, 2026, 3:20pm UTC](https://community.fibery.io/t/done-create-related-entity-if-doesnt-exist-on-csv-import/9783 "2026-02-12T15:20:51Z")

</div>

When importing into a to-one or to-many relation, it will only ever link to existing entities and not create new ones based on the names in the CSV. This means we need to make sure they exist, or else data will be lost …

---

## [Moving from Notion to Fibery \[VIDEO\]](https://community.fibery.io/t/moving-from-notion-to-fibery-video/10315)

<div class="topic-metadata">

**Author:** [@dmytro](https://community.fibery.io/u/dmytro)\
**Replies:** 0\
**Last updated:** [January 29, 2026, 9:34am UTC](https://community.fibery.io/t/moving-from-notion-to-fibery-video/10315 "2026-01-29T09:34:11Z")

</div>

Just published a video to help anyone moving from Notion. Importing data, mental models you need to understand and other useful stuff. Should help anybody to switch from document-first to database-first. Let me know if…

---

## [No option to skip empty source fields when updating existing target data via CSV](https://community.fibery.io/t/no-option-to-skip-empty-source-fields-when-updating-existing-target-data-via-csv/9853)

<div class="topic-metadata">

**Author:** [@Yuri\_BC](https://community.fibery.io/u/Yuri_BC)\
**Replies:** 6\
**Last updated:** [October 28, 2025, 12:12pm UTC](https://community.fibery.io/t/no-option-to-skip-empty-source-fields-when-updating-existing-target-data-via-csv/9853 "2025-10-28T12:12:31Z")

</div>

Issue: In the configuration form of the CSV import feature, in In ‘Manage Duplicates’ when selecting ‘Update existing entity’ And the data that is imported contains fields that are not empty and that are empty. The imp…

---

## [Import into created date field](https://community.fibery.io/t/import-into-created-date-field/8663)

<div class="topic-metadata">

**Author:** [@RonMakesSystems](https://community.fibery.io/u/RonMakesSystems)\
**Replies:** 1\
**Last updated:** [September 3, 2025, 6:56pm UTC](https://community.fibery.io/t/import-into-created-date-field/8663 "2025-09-03T18:56:33Z")

</div>

With the theme of improving import, one piece of data that is hard to import at the moment is the created date. It would be great to be able to select “Created date” field as the import field for the “Created date” in t…

---

## [\[DONE\] Easy import of markdown docs to wiki](https://community.fibery.io/t/done-easy-import-of-markdown-docs-to-wiki/307)

<div class="topic-metadata">

**Author:** [@rickcogley](https://community.fibery.io/u/rickcogley)\
**Replies:** 33\
**Last updated:** [July 28, 2023, 5:26pm UTC](https://community.fibery.io/t/done-easy-import-of-markdown-docs-to-wiki/307 "2023-07-28T17:26:01Z")

</div>

Hello - I have a considerable number of docs in markdown. The wiki docs / other docs, is not really compatible with simply copy-pasting markdown you have. Anything that can be done?

---

## [CSV Import deletes embedded newlines in plain Text fields](https://community.fibery.io/t/csv-import-deletes-embedded-newlines-in-plain-text-fields/4057)

<div class="topic-metadata">

**Author:** [@Matt\_Blais](https://community.fibery.io/u/Matt_Blais)\
**Replies:** 1\
**Last updated:** [July 28, 2023, 12:59pm UTC](https://community.fibery.io/t/csv-import-deletes-embedded-newlines-in-plain-text-fields/4057 "2023-07-28T12:59:04Z")

</div>

Since Fibery plain Text fields can have embedded newlines, this seems like a bug.

---

## [For Field Mapping operations (CSV import, later type conversion) add formula field for concatenating data](https://community.fibery.io/t/for-field-mapping-operations-csv-import-later-type-conversion-add-formula-field-for-concatenating-data/3350)

<div class="topic-metadata">

**Author:** [@Oshyan](https://community.fibery.io/u/Oshyan)\
**Replies:** 0\
**Last updated:** [October 1, 2022, 6:20am UTC](https://community.fibery.io/t/for-field-mapping-operations-csv-import-later-type-conversion-add-formula-field-for-concatenating-data/3350 "2022-10-01T06:20:37Z")

</div>

I find myself using both CSV import and Entity Conversion to other Databases frequently at the moment. One thing I think would be really useful to have for both (at least when Entity Conversion gets Field Mapping), would…
