Dropbox to Google Drive: Automate File Renaming and Movement with Make.com

Introduction

If you regularly receive media assets via Dropbox and end up spending minutes renaming, sorting, and moving files into Google Drive, you know how easy misnaming or misfiling becomes a bottleneck. A small automation can make the entire process predictable: when a new file lands in Dropbox, Make.com renames it with a consistent pattern, moves or uploads it into a preconfigured Google Drive folder, and logs the action for traceability. This post walks you through a lean two-tool workflow that is simple to maintain and scale.

By the end you will have a repeatable pattern: a new file in Dropbox triggers a Make.com scenario, the file uploads to Google Drive with the expected name, and an entry is written to a log sheet so you can audit every asset move. If you want broader patterns, check how we approach cross-platform automation Cross-Platform Automation (XPA).

What You'll Need

• A Dropbox account with a watch/triggers capability for a specific folder
• A Google Drive account with a target folder structure ready for incoming files
• A Make.com account with connectors for Dropbox and Google Drive (a paid plan is recommended for robust runs)
• A Google Sheets file to log the moves (optional but recommended for auditability)

Naming convention tips:

• Use a consistent prefix like clientName or projectCode
• Include a date stamp (YYYY-MM-DD) to keep files sorted
• Preserve the original filename as a suffix for reference

How It Works (The Logic)

Trigger: A new file appears in a Dropbox folder Action 1: Rename the file to a consistent pattern using a Make.com function or mapper Action 2: Upload or move the file to a designated Google Drive folder with the new name Action 3: Append a log row in Google Sheets with original name, new name, Dropbox path, Drive path, timestamp Optional: Post an alert to Slack if a step fails so you can reprocess quickly

Step-by-Step Setup

1. Prepare your Google Drive folder structure

• Create a root folder for Dropbox imports, e.g. Dropbox Imports
• Within it, create subfolders per client or project if you want automatic routing, e.g. Dropbox Imports/ClientA/2026-10-01
• Note the target folder IDs; you will use them in Make

2. Create a Make.com scenario and connect apps

• Create a new scenario
• Add Dropbox as the first module and choose the trigger "Watch Files in Folder" for the folder you prepared
• Add a Google Drive module next and choose "Upload a File" or "Copy a File" depending on what the connector supports for your flow
• Add Google Sheets as the final module with "Add a Row" to log the move

3. Compute the new name

• Use a Make.com mapper or code block to create a new file name pattern like: clientName - YYYY-MM-DD - originalName
• If you do not have a clientName, use a generic tag (e.g., Project-XYZ) and a timestamp

4. Move or upload to Google Drive

• In Google Drive, choose the target folder path that matches your naming convention
• Map the file content from Dropbox, the new file name, and the destination folder

5. Log the operation in Google Sheets

• Use the Add Row action to populate columns such as:
  • Original Filename
  • New Filename
  • Dropbox Path
  • Drive Path
  • Timestamp
• Ensure the sheet columns are stable so dashboards stay readable

6. Add optional error handling

• Route failures to Slack channel or log error details to a separate sheet
• Consider a retry policy in Make and a manual re-run path for stubborn files

7. Test end-to-end

• Drop a test file into the Dropbox folder
• Verify the file appears in Google Drive under the correct folder with the expected name
• Confirm a row was appended to Google Sheets with accurate references

8. Turn on the scenario and monitor

• Start small with a low file volume
• Review the log for a few days to confirm naming consistency and path accuracy

Real-World Business Scenario

A design studio receives client assets via Dropbox. An automation watches a designated folder, renames each incoming file to a pattern like “ClientA - 2026-10-01 - Logo.ai” and uploads it to Google Drive under a client-specific folder. The team then logs each move in a Google Sheet, giving project managers a quick audit trail and a single place to click through to the asset. This eliminates misnaming and reduces time spent searching for assets across platforms. If you want to see how to layer this with other workflows, we’ve covered related patterns in posts like the Shopify to Google Sheets and Slack guide and broader cross-platform automation patterns.

Common Variations

• Extend to multi-folder routing: create per-client folders dynamically when a new file lands
• Add metadata extraction: extract client name and project from the file or its Dropbox metadata to populate name fields automatically
• Integrate with a retention policy: auto-archive older files after a period and update logs accordingly

Why this pattern works

This is a minimal, reliable automation that eliminates manual renaming mistakes and reduces time spent moving files between Dropbox and Google Drive. It provides a clean trail in Google Sheets and a predictable file naming convention that scales as your asset library grows. If you want help tailoring this to your exact folder structure, naming rules, and logging schema, Olmec Dynamics builds outputs like this and more for real teams. See our approach to cross-platform automation Cross-Platform Automation (XPA).

Closing note

If you want a partner to design and maintain these kinds of file and media workflows for your team, Olmec Dynamics can help you implement a robust, auditable automation pattern across Dropbox, Google Drive, and the rest of your stack. Learn more about our services and how we approach XPAs on our site Cross-Platform Automation (XPA).