> For the complete documentation index, see [llms.txt](https://academy.shade.inc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://academy.shade.inc/guides/setup-and-migration/migrate-from-dropbox-or-google-drive.md).

# Migrate from Dropbox or Google Drive

Move folders from Dropbox or Google Drive into Shade with built-in transfers, then check that everything arrived.

**Outcome:** your Dropbox or Google Drive folders copied into a Shade drive with their folder structure intact, verified, and indexed for search, while your team keeps working.

**Who it's for:** teams moving off Dropbox or Google Drive. For S3, a NAS, or other cloud storage, use [Mass migrating data to Shade via Rclone](/guides/setup-and-migration/mass-migrating-data-to-shade-via-rclone.md) instead.

**Time:** about 15 minutes of setup. The transfer itself runs in the background and can take hours or days, depending on how much media you have.

## Before you start

* Be a workspace admin, and have access to the Dropbox or Google Drive account that owns the files.
* Create the destination drive in Shade first, ideally from your template drive. See [Your first week in Shade](/guides/setup-and-migration/your-first-week-in-shade.md).
* Check that your Shade plan has room for the data you're moving.

## Steps

{% stepper %}
{% step %}

### Plan what moves where

List the top-level folders you're moving and which Shade drive each one goes to. This is a good moment to leave behind old exports and duplicates you don't need. Moving less makes the transfer faster and keeps your new drive tidy.
{% endstep %}

{% step %}

### Connect the account

In Shade, go to **Settings > Integrate > Integrations**, open **Dropbox** or **Google Drive**, and connect the account. You'll be asked to sign in and approve access.
{% endstep %}

{% step %}

### Choose the source and destination

Browse the connected account and select the folders to move. For Google Drive, you can also select shared drives. Then pick the destination Shade drive and folder.

Start with one small folder as a test run before you queue everything.
{% endstep %}

{% step %}

### Start the transfer and watch it

Start the transfer. Progress is listed under **Settings > Integrate > Integrations > Transfers**, with each transfer marked **Queued**, **Transferring**, **Completed**, or **Cancelled**. Transfers run in the background, with checksum verification on every file. You can close the app while they run.
{% endstep %}

{% step %}

### Check that everything arrived

When a transfer shows **Completed**:

* Compare file counts and total size for a few top-level folders in Shade with the source.
* Open a handful of large video files and play them through.
* Give it time. Proxies, transcripts, and AI search data are generated after files land, so very large libraries take a while to become fully searchable.
  {% endstep %}

{% step %}

### Switch your team over

Once you've checked the transfer, tell the team to work only in Shade. Ask them to mount the drive in the desktop app, and set the old folders to read-only so nobody keeps adding to them. Keep the source for a few weeks before you delete anything.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
Need help moving a very large library? Shade offers migration help. See [Do you offer migration assistance from existing storage?](https://academy.shade.inc/help-center/billing/do-you-offer-migration-assistance-from-existing-storage)
{% endhint %}

## Related guides

* [Mass migrating data to Shade via Rclone](/guides/setup-and-migration/mass-migrating-data-to-shade-via-rclone.md)
* [Your first week in Shade](/guides/setup-and-migration/your-first-week-in-shade.md)
* [Build a searchable archive](/guides/search-ai-and-archives/build-a-searchable-archive.md)


---

# 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 dynamically by asking a question.

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

```
GET https://academy.shade.inc/guides/setup-and-migration/migrate-from-dropbox-or-google-drive.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 `build a script that syncs our docs to a CMS` 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.