# Save Import Settings **URL:** \ **Category:** Ideas & Features\ **Created:** [September 12, 2022, 10:07am UTC](https://community.fibery.io/t/save-import-settings/3281 "2022-09-12T10:07:26Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![neil](https://avatars.discourse-cdn.com/v4/letter/n/839c29/32.png) [@neil](https://community.fibery.io/u/neil)\ **Post date:** [September 12, 2022, 10:07am UTC](https://community.fibery.io/t/save-import-settings/3281/1 "2022-09-12T10:07:26Z")
The CSV import is quite good but it sometimes guesses field types wrong. It would be convenient to be able to save import settings somewhere so I don’t have to enter them every time. This would be particularly useful for any kind of situation where one is either 1) testing data import for a new entity, or 2) where new data imports have to happen periodically. The latter situation may be unlikely for adding fields to an existing entity, but it is more likely to come up if you do imports in a sort of staging table for later import to your production table. ---
**Author:** ![Oshyan](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/oshyan/32/11431_2.png) [@Oshyan](https://community.fibery.io/u/Oshyan)\ **Post date:** [September 13, 2022, 1:27am UTC](https://community.fibery.io/t/save-import-settings/3281/2 "2022-09-13T01:27:04Z")
I could really use this too! Will try to add a vote when I have one to spare. 😄 ---
**Author:** ![Polina\_Zenevich](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/polina_zenevich/32/480_2.png) [@Polina\_Zenevich](https://community.fibery.io/u/Polina_Zenevich)\ **Post date:** [September 13, 2022, 7:11pm UTC](https://community.fibery.io/t/save-import-settings/3281/3 "2022-09-13T19:11:32Z")
Hi, Neil! That’s a very nice idea in fact 🙂 But that seems that you have the same-structured CSV file. So in your case, CSV import is a recurring event when only entities arrive Did I guess right? If so, could you please share the use case? ---
**Author:** ![neil](https://avatars.discourse-cdn.com/v4/letter/n/839c29/32.png) [@neil](https://community.fibery.io/u/neil)\ **Post date:** [September 14, 2022, 12:41am UTC](https://community.fibery.io/t/save-import-settings/3281/4 "2022-09-14T00:41:45Z")
Hi Polina, in this particular case I was importing vendors from our accounting system. But there are tons of irrelevant fields so I had to turn off a bunch, fix the type for a few, etc. Ideally I’d be able to set this up as an automatic thing on a nightly or weekly import sync. Or even better of course would be a deep integration with Sage Intacct and/or [bill.com](http://bill.com). 🙂 ---
**Author:** ![T\_A](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/t_a/32/1619_2.png) [@T\_A](https://community.fibery.io/u/T_A)\ **Post date:** [August 15, 2025, 8:44pm UTC](https://community.fibery.io/t/save-import-settings/3281/5 "2025-08-15T20:44:50Z")
We are running into a similar issue. We use Monograph for timekeeping and would like to pull time and cost data into Fibery. Our only option is to periodically (once a week) export Monograph timesheet data into a CSV and import into Fibery, but each time we do this we need to manually adjust field mapping. We have the same issue with importing invoice data from Quickbooks (once a month). Is there some workaround i am missing? ---
**Author:** ![Polina\_Zenevich](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/polina_zenevich/32/480_2.png) [@Polina\_Zenevich](https://community.fibery.io/u/Polina_Zenevich)\ **Post date:** [August 18, 2025, 3:32pm UTC](https://community.fibery.io/t/save-import-settings/3281/6 "2025-08-18T15:32:17Z")
Hi! If that’s a constant process, maybe you may consider building an integration instead? 🙂 That might be more reliable. So far our primary use case to address is importing new data to Fibery for migration purposes, that’s why this request wasn’t in the initial scope