Manual · 07

Cloud backup

With cloud backup, you additionally back up the SD-Migrator folder to your cloud storage. This gives you a further copy of your footage while you are on the road. The cloud serves exclusively as a backup destination.

Supported services:

  • Dropbox
  • Google Drive
  • OneDrive
  • pCloud
  • iCloud Drive

How cloud backup works

Only new files are uploaded

  • SD Migrator uploads only new files to the SD-Migrator folder in your cloud storage. The folder structure is the same as on the device: first the card label, then the date below it.
  • Existing files in the cloud are never overwritten.
  • Incomplete copies and the Backup folder are not uploaded. The same applies to system files such as .DS_Store, ._*, .Trashes and Thumbs.db. Dropbox rejects some of these anyway.
  • If an upload was interrupted, the next run resumes from that point.
  • If a single file fails, you see it listed by file name. All other files are still processed and verified.

Verification after upload

After the upload, SD Migrator compares every file in the cloud with the original:

  • Dropbox, Google Drive, OneDrive, pCloud: comparison by checksum, i.e. of the file content.
  • iCloud Drive: comparison by file size only.

If there are discrepancies, the job ends with Error. In this case, nothing is deleted.

Volume limit per job

With Maximum transfer (GB) you set the maximum amount of data a job uploads. The default is 5 GB. The limit applies to every connection, including mobile data.

When the limit is reached, the job ends with Partial. Start the upload again to continue.

Tip: On the road with a limited data allowance, you can upload large collections in several small stages this way.

Delete locally after upload (optional)

With Delete locally after verified upload, SD Migrator frees up storage on the device after the upload:

  • Deletion only takes place after you confirm it.
  • Only files whose cloud copy has been confirmed identical by checksum are deleted.
  • Empty folders are then removed.

Caution: This option is locked for iCloud Drive. iCloud does not provide checksums, so the cloud copy cannot be verified reliably enough.

Starting a cloud backup

  1. Open Distribute backups.
  2. Select the 03 / Cloud panel.
  3. Select the cloud destination you want.
  4. Adjust Maximum transfer (GB) if required.
  5. Enable Delete locally after verified upload if required.
  6. Start the upload.

At the top of the page you can see the progress, the speed and the volume already uploaded.

Caution: You cannot start copy jobs during a cloud upload. Conversely, cloud upload is locked while a copy job is running.

Setting up a cloud destination

You set up cloud destinations under Settings → Cloud destinations.

Dropbox, Google Drive, OneDrive, pCloud

Signing in to these services requires a browser. You therefore do it once on a Mac.

  1. Install the rclone program on the Mac once:

    brew install rclone

  2. Run the matching sign-in command on the Mac:

    • Dropbox: rclone authorize "dropbox"
    • Google Drive: rclone authorize "drive"
    • OneDrive: rclone authorize "onedrive"
    • pCloud: rclone authorize "pcloud"
  3. Sign in to your cloud service in the browser.

  4. Copy the complete output of the command.

  5. Paste the output into the field provided in SD Migrator under Settings → Cloud destinations.

After that, SD Migrator renews the access automatically.

Additional options:

  • Own client ID: Optionally, enter your own credentials in the Client ID and Client secret fields. The sign-in command shown then includes them automatically. This is strongly recommended for Google Drive (see below).
  • Renew access: Replaces the access and client ID of an existing destination without creating the destination again.
  • pCloud: SD Migrator detects by itself whether your account is on an EU or US server. You do not need to select anything.
  • OneDrive: The pasted output may be older than one hour. SD Migrator then renews the access itself.

iCloud Drive

  1. Enter your Apple ID.
  2. Enter your normal Apple password.
  3. Enter the 6-digit verification code that appears on your Apple device.

Caution: Apple lets the sign-in expire after 30 days. Then tap Sign in again and enter a new verification code.

For iCloud Drive, rclone version 1.69 or later must be installed on the SD Migrator.

Testing and removing a connection

  • Test checks whether the connection to the cloud storage works.
  • Remove deletes only the credentials on the SD Migrator. Files in your cloud are never deleted.

The interface never displays saved passwords and access credentials again.

Without your own client ID, SD Migrator uses an access for Google Drive that is shared by all users. Google throttles this access heavily. With many files, the upload may then appear to stall for minutes. In addition, Google is shutting down this shared access during 2026.

Your own client ID is free. You create it once in about 10 minutes. You can also find detailed instructions from rclone: https://rclone.org/drive/#making-your-own-client-id

  1. Open https://console.cloud.google.com and create a new project, e.g. “sd-migrator”.

  2. Open APIs & Services → Library and enable the Google Drive API.

  3. Open Google Auth Platform, i.e. the OAuth consent screen:

    • Select External as the audience.
    • Enter an app name and your own email address.
    • Under Data access, add this scope: https://www.googleapis.com/auth/drive.file

    This gives SD Migrator access only to files it creates itself. Google classifies this scope as “non-sensitive” and does not require verification for it.

    To publish, Google requires a homepage and a privacy policy under Branding. Both must be public addresses on a domain of your own. This domain must be entered under Authorised domains.

  4. Publish the app under Audience (“In production”).

    Caution: In testing mode, access expires after 7 days. You must therefore publish the app.

    For your own use, you do not need verification by Google. When you sign in, the notice “Google hasn’t verified this app” then appears. Tap Advanced and continue.

  5. Open Clients (credentials) and select Create OAuth client ID. Select the type Desktop app. Then copy the client ID and client secret.

  6. In SD Migrator, open Settings → Cloud destinations. For the Google Drive destination, tap Renew access or create a new destination.

  7. Enter the client ID and client secret.

  8. Run the displayed command on the Mac. It has the form rclone authorize "drive" "eyJ…".

  9. Paste the output and tap Save.

Caution: Use exactly the command shown. A short form with only the client ID and secret requests full access to your Google Drive. Google blocks this sign-in.

The access always belongs to a specific client ID. Therefore, always change both together.

Tip: With your own client ID, SD Migrator only sees its own uploads. If your Google Drive already contains an SD-Migrator folder that was created manually or with a different client ID, it is invisible to SD Migrator. The upload then creates a new SD-Migrator folder.