Skip to content

migrate · drive → dosya

Move your Google Drive across in three clicks.

No terminal needed. Connect Google from your dashboard, pick the folders, and dosya.dev copies them server-side in the background. Nothing in Drive is changed, and nothing downloads through your machine.

See the steps Before you run it

The steps

Three clicks, then a notification.

The importer does the copying. It reads from Google's servers and writes to your workspace, so the size of your Drive and the speed of your connection do not matter. Folder structure arrives intact.

drive → dosya
  1. 1 Connect Google Drive from your dashboard. Sign in with Google. dosya.dev asks for read-only access and changes nothing in Drive.
  2. 2 Pick the folders, Shared Drives included. The picker shows your whole Drive. Choose everything, or one project at a time.
  3. 3 Close the tab. The import runs in the background. You get a notification when it finishes, and each file shows where it came from.
Read the guide Migrate off Google Drive without downloading everything The download-and-re-upload approach wastes days and quietly breaks Google's own formats. Here is a migration that avoids both problems. 5 min read.

Before you press enter

Two things about each end.

Read once, then run. Everything here shows up in the log if you skip it, so nothing is lost, only time.

At Drive

  • Google formats are exported. Docs, Slides and Drawings arrive as PDF, Sheets as .xlsx. The originals stay in Drive untouched.
  • Shared Drives are in the picker. Choose a Shared Drive like any folder. Shortcuts are followed to the file they point at.

At dosya.dev

  • Empty files are refused. A 0-byte object is skipped with a warning and rclone check lists it, so you know which ones.
  • Filenames stop at 255 characters. A longer key fails and shows up in the log; rename it at the source and run the copy again.
  • Your region is yours to pick. A workspace lives in one of 46 regions on 6 continents; choose it when you create the workspace, before the import.

Where Drive is the better fit

If your day happens inside Docs, Sheets and Slides, Drive is where those files should live: dosya.dev previews and comments on documents but does not edit them.

Read the guide Egress fees: the cloud storage cost nobody quotes Storage is priced per gigabyte stored. The bill that surprises people is per gigabyte read. Here is how egress works and why it punishes success. 5 min read.

Questions

Before you run it, answered.

What happens to Google Docs, Sheets and Slides?
The importer exports them: Docs, Slides and Drawings as PDF, Sheets as an .xlsx spreadsheet. The originals stay in Drive exactly as they were.
Does the import go through my computer?
No. dosya.dev reads from Google's servers and writes to your workspace directly. You can close the tab; the import carries on in the background and you get a notification when it finishes.
Can I still use rclone with Drive?
Yes, rclone has a Drive backend, but it needs your own OAuth client ID and exports Google formats on the fly. The importer is the shorter road for a Drive; rclone is the right tool for buckets.
Do I need a paid dosya.dev plan to migrate?
No. The free plan has 5 GB and the importer. Bring one folder across, look at the result, and pick a plan when you know the size of what landed.

Copy one folder first.

5 GB free and every protocol on it. Bring one folder across, look at the result, then move the rest.

Create a workspace How the importer works