# Import CSV > Create data models from importing a CSV file :::info At the moment, only **Admins** and **Data Analysts** can import CSV data in the Development workspace. In the future, we will work to support this capability for **Viewers** and **Explorers**. ::: ## Introduction Sometimes you might need to quickly analyze data from CSV files for temporary reporting needs. It can be an analysis on some customer survey data, or a CRM export. This process typically includes waiting for data engineers, navigating complex ETL setups, and dealing with access issues. It can be frustrating and result in hours or even days of waiting for what should be a simple, temporary data analysis. To address this, Holistics supports loading spreadsheet data directly into your connected database, and creating a data model ready to use. :::tip Usage note CSV import is designed for quickly setting up your ad-hoc analysis. It is NOT intended to replace full-fledged data integration solutions *(see [Data Models](/docs/data-model))*. ::: ## CSV import ### Initial upload Simply choose a local CSV file for upload, configure the data if necessary, and import. You will have a new data model ready for exploration within seconds. ### Replacing your CSV data After the initial CSV upload, you can always replace this data with a new CSV for fresh data. The new CSV should have the same column structure to ensure compatibility with existing reports and dashboards. To do this, navigate to the Data model → **Details** tab → **Replace file** button. ## How it works Under the hood, Holistics loads the data from your CSV files into a new table in your connected database. Then, Holistics also creates a data model from that table. ## Supported databases :::warning Note Make sure you have granted the **WRITE access** for your Holistics user (or service account) in your database for the import to work. ::: Holistics currently supports importing data to the following databases: - PostgreSQL - Amazon Redshift - MySQL - Google BigQuery - Microsoft SQL Server - PrestoDB - Amazon AWS Athena - Snowflake - ClickHouse This feature is not yet available for other databases, such as Databricks or MotherDuck. ## Other configurations ### Set default write schema for import You can specify the default schema for import in this file path `settings > project_settings.aml`. ``` ProjectSettings project_settings { data_import { default_write_schema: 'public_persisted' //<-- Your default write schema goes here. } } ``` Notes: - This setting only specifies the default option. You can still change the schema when importing. - This setting is global for all data sources.