Transfer Cloud Data with Make.com

Transferring files between cloud storage services can be time-consuming if done manually. With make.com, you can build an automated scenario that moves or copies files between platforms like Google Drive, Dropbox, OneDrive, Box, and other supported apps without repetitive work.

Why automate cloud transfers with Make.com

Using make.com for cloud storage transfers eliminates manual downloads and uploads, reduces errors, and keeps folders synchronized across platforms. You can define exactly which files to move, when to move them, and what should happen if something fails.

Move or copy files between different cloud apps.
Apply filters so only specific files are transferred.
Schedule transfers or trigger them automatically.
Monitor errors and handle conflicts safely.

This guide is based on the official how-to from the Make website and shows how to transfer data from one cloud storage to another using a visual, no-code workflow.

Before you start with Make.com

To follow these steps, you will need:

A make.com account with access to the scenario editor.
Access credentials for your cloud storage services (for example Google Drive, Dropbox, or OneDrive).
At least one source folder and one destination folder created in your cloud platforms.

You should also ensure that both storage services are supported as apps in make.com and that your account has the necessary permissions to read and write files.

Overview of the Make.com scenario

The automation will work as a scenario in make.com made from modules connected in sequence. A typical flow looks like this:

A trigger module detects new or changed files in the source storage.
A search or list module retrieves specific files or folders.
A transfer module creates or updates files in the destination storage.
Optional tools handle filters, mapping, and error handling.

Depending on your use case, the scenario can either copy files (keeping them in the original storage) or move them (removing them from the source after a successful transfer).

Step 1: Create a new scenario in Make.com

Sign in to your make.com account.
From the dashboard, click on the option to create a new scenario.
In the scenario builder, you will see a blank canvas where you can add modules representing each cloud service.
Save the scenario with a clear name such as “Cloud Storage Transfer” so you can easily find it later.

This empty scenario will become the backbone of your automated transfer workflow.

Step 2: Add the source cloud module in Make.com

First, choose the cloud storage that will act as the source of your data.

Click the plus icon on the canvas to add your first module.
Search for the source app (for example “Google Drive”, “Dropbox”, or “OneDrive”).
Select a trigger or search module, such as:
- Watch Files / Watch Files in a Folder
- List Files
- Search Files or Folders
Connect your cloud account and grant permissions when prompted.
Configure the folder or path where the files currently reside.

The chosen module determines how make.com detects which files to transfer. A “watch” trigger is useful if you want to transfer new files automatically, while a list or search module works well for one-time or batch transfers.

Step 3: Filter and select files to transfer

To avoid sending unnecessary data, configure filters in your modules or on the connections between them.

Use file name patterns (for example, PDFs only or files with a specific prefix).
Filter by MIME type, file extension, or size.
Apply date filters to move only recently modified files.
Define folder paths or subfolders for more precise targeting.

In make.com you can add filters between modules so that only items matching certain conditions move forward in the workflow. This helps control costs and keeps your destination storage organized.

Step 4: Add the destination cloud module in Make.com

Next, connect the second cloud storage service that will receive the transferred data.

Click the plus icon to add another module after your source module.
Search for the destination app, such as Box, Google Drive, Dropbox, or OneDrive.
Choose an appropriate action, for example:
- Upload a File
- Create a File from a URL
- Create a Folder
- Update a File
Connect your destination cloud account and grant permissions.
Specify the destination folder or root directory where files should be stored.

Using the mapping interface in make.com, map the file content, file name, and any metadata fields from the source module to the destination module. This ensures each transferred item is correctly created or updated.

Step 5: Configure mapping and options in Make.com

Careful mapping and configuration help you avoid duplicates and maintain structure.

File name mapping: Map the original file name or build a new naming pattern using variables (such as date or folder name).
Folder structure: Map folder paths if you want to mirror the same structure in the destination storage.
Overwrite rules: Decide whether existing files should be overwritten, skipped, or renamed.
Metadata: Transfer descriptions, tags, or custom properties when supported by both apps.

Make.com provides a visual mapping panel where you can drag and drop fields, use functions for formatting, and build dynamic paths for flexible transfers.

Step 6: Add scheduling, triggers, and filters

Depending on your use case, you may want a one-time migration or an ongoing synchronization.

Scheduling options in Make.com

Manual run: Start the scenario only when you click “Run once”.
Scheduled run: Use the scheduler to run the scenario at regular intervals.
Event-based trigger: Use a “watch” module that activates whenever new files appear.

Advanced filters using Make.com

You can refine processing with additional filters between modules:

Skip files that already exist in the destination.
Move files only from certain owners or folders.
Exclude temporary or system files.

These filters help you maintain control and avoid unnecessary transfers.

Step 7: Test and debug your Make.com scenario

Before running the automation in production, test the scenario with a small sample.

Use the “Run once” button to execute the scenario for the first time.
Watch the execution inspector to see each module’s input and output.
Confirm that files appear correctly in the destination storage with the expected names and locations.
Adjust filters, mappings, and overwrite settings if needed.

Make.com provides detailed logs and error messages so you can identify issues like missing permissions, incorrect paths, or size limits and adjust the scenario accordingly.

Step 8: Activate and monitor your Make.com automation

Once you are satisfied with the results, activate the scenario.

Switch the scenario from “Draft” or “Inactive” to “On”.
Let it run according to the configured schedule or triggers.
Periodically check the execution history and logs to confirm that transfers continue to work as expected.

If your volume of data grows, you can optimize the scenario by batching items, adding more filters, or splitting the logic into multiple smaller scenarios.

Best practices for cloud transfers with Make.com

Plan folder structure: Decide in advance how the destination storage will be organized.
Start small: Test with a few files before running a large migration.
Limit scope: Use filters to avoid transferring unnecessary or duplicate data.
Monitor quotas: Be aware of API limits and storage quotas on each cloud platform.
Backup important data: Maintain a backup strategy before deleting files from the source.

Following these recommendations helps you keep transfers stable and predictable.

Learn more and related resources

For the original reference on which this walkthrough is based, see the official tutorial on transferring data between cloud storage services on the Make site: Transfer data from one cloud storage to another.

If you need expert help designing complex automation scenarios or integrating additional tools around make.com, you can find consulting, strategy, and implementation services at Consultevo.

By combining the flexibility of make.com with a clear plan for your cloud storage structure, you can automate data transfers reliably, reduce manual work, and keep your files synchronized across the services your team uses every day.

Need Help With Make.com?

If you want expert help building, automating, or scaling your Make scenarios, work with ConsultEvo — certified workflow and automation specialists.

Get Help