> For the complete documentation index, see [llms.txt](https://docs.rhinofcp.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rhinofcp.com/getting-started/quick-start-guide/importing-and-exporting-datasets-to-and-from-your-network-storage.md).

# Importing and Exporting Datasets to and from Your Network Storage

Explains how to import and export datasets on the Rhino FCP from selected storage platforms.

You can import and export datasets on the Rhino FCP to and from the following places:

* Amazon Web Services (AWS) S3
* Google Cloud Platform's (GCP) Cloud Storage (CS)
* Server Message Block (SMB) network file sharing protocol
* Azure Blob Storage

## Prerequisite

Before you can complete these instructions, you will need to mount the bucket or directory that contains the data you want to access. To do this, follow the steps in [Mounting Storage to Your Rhino Client](/settings/mounting-storage-to-your-rhino-client.md).

## Import Datasets

[Import a new dataset](/datasets/registering-configuring-and-exporting-datasets.md) and point the data location to your cloud storage data relative to the Client Mount Paths, see more detail in the Example below.

The integration is available at the workgroup level. Each workgroup can set up their own buckets or network share. Those buckets or network shares are not accessible to other workgroups.

### Example: Importing a file from AWS S3

Suppose you want to import file that is located in a S3 bucket. Here is how you would do this.

{% stepper %}
{% step %}
Find your data by navigating to your organization storage (click on the S3 arrow button)

![](https://content.gitbook.com/content/ydySyCBmy6F7NnGn4bPa/blobs/oA3y0IzZviko0da4uEqC/30126360170141)
{% endstep %}

{% step %}
Find the data you want to import, e.g., **automapper/ORGDataSet.csv**.

![](https://content.gitbook.com/content/ydySyCBmy6F7NnGn4bPa/blobs/sj5QArycd6p3uXQawl7t/30126389110429)
{% endstep %}

{% step %}
Go to Settings > Client Mounted Storage.
{% endstep %}

{% step %}
In the Client Mounted Storage page, find the Client Mount Path that has the file, in this case **/rhino\_data/external/s3**. Click the blue rectangle next to it to copy it.

![](https://content.gitbook.com/content/ydySyCBmy6F7NnGn4bPa/blobs/AI94EAmHlO7CQH7OQBPs/30126389110685)
{% endstep %}

{% step %}
In the Datasets page, on the Overview tab, select **Import New Dataset** and follow the instructions in [Importing a New Dataset in the Rhino FCP GUI](/datasets/registering-configuring-and-exporting-datasets.md).
{% endstep %}

{% step %}
Set the data location as **Client Mounted Path/Relative Path to Your Data in S3**. Following the example in steps 2 and 4, it'd would look like as follows:

![](https://content.gitbook.com/content/ydySyCBmy6F7NnGn4bPa/blobs/AkzXFrZB0DN7DrhPBia3/30126389110941)
{% endstep %}

{% step %}
Select Import New Dataset.
{% endstep %}
{% endstepper %}

## Export Datasets

To export an existing dataset, follow the steps described in [Exporting a Dataset](/datasets/registering-configuring-and-exporting-datasets.md). The Rhino integration with your network storage should be configured as `Is read only` = `False` to allow your Rhino Client to save the exported files in your network storage. (If you are not sure if `Is read only` = `False` in your configuration, please contact the Rhino support team.)

Datasets will be exported to the file storage path set in the integration. For the AWS import example above, datasets would exported to your AWS S3 bucket named `my_bucket`.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.rhinofcp.com/getting-started/quick-start-guide/importing-and-exporting-datasets-to-and-from-your-network-storage.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.