Sync to Google Drive OneDrive and SFTP with GoodSync
The right side of a GoodSync job does not have to be a folder on a disk. It can be your Google Drive, the office OneDrive, an SFTP server across town — or another PC entirely, with no cloud in between.
🎥 The folder browser in the video is where all of this starts — every endpoint below is chosen from that same window
When you click the folder bar while building a job, GoodSync shows its real range: local folders, network shares, FTP, SFTP and WebDAV, cloud storage including Google Drive, OneDrive, Dropbox, Box, Amazon S3 and Backblaze B2 — and GoodSync Connect, its own peer-to-peer route between computers. Each endpoint has a different sign-in and a different honest limit. This guide walks all four routes people actually ask about.
GoodSync folder browser — choosing where the job ends
Local Folder — this PC and attached disksREADY
Google Drive — sign in with Google accountREADY
OneDrive — sign in with Microsoft accountREADY
SFTP — server address and login neededSETUP
GoodSync Connect — another computer, directSETUP
👆 The endpoint list inside the folder browser. Same job window, five very different destinations — the setup effort moves from zero (local) to a few minutes (SFTP and Connect).
1
Route 1 — Google Drive and OneDrive as the Destination
Create the job, click the Right folder bar, and choose Google Drive or OneDrive from the file-system list
GoodSync opens your browser for a normal OAuth sign-in — you log in to Google or Microsoft directly; GoodSync never sees your password
Pick the destination folder inside the drive and finish with Analyze before the first Sync, exactly as with a local job
Honest limits: your cloud quota is the ceiling — a full drive stops the job mid-way. And editing the same document in the cloud while GoodSync pushes a local edit is how conflicts are born; let one side lead
2
Route 2 — An SFTP Server, for Offices and Websites
In the folder browser choose the SFTP file system and enter the server in the form sftp://server-address (SFTP rides on SSH, default port 22)
Enter the username and password your server admin gave you — or point GoodSync at your private key file if the server uses key login
Navigate to the target folder on the server, then Analyze
Why SFTP over plain FTP: the connection is encrypted, including your password. If a server still offers only FTP in 2026, that is the server's problem to fix, not a reason to send credentials in the clear
3
Route 3 — GoodSync Connect, PC to PC With No Cloud at All
GoodSync Connect is the route for “sync my office PC and my home PC, but the files should never sit on someone else's server”:
Install GoodSync on both computers and sign both into the same GoodSync Connect account
Each PC becomes reachable to the other's jobs through the Connect file system — you pick the remote computer and folder just like a local one
GoodSync's mediator introduces the two machines, after which the data travels in a direct peer-to-peer connection — no port forwarding, no static IP, and the files themselves do not rest in a cloud account
Honest limits: both PCs must be on and online for the job to run, and speed is capped by the slower home connection's upload
4
Route 4 — Protect the Job Itself
For cloud destinations, prefer a 1-way backup job with deletions not propagated — otherwise a local accident syncs straight into your cloud copy, and the cloud faithfully keeps the damage
Turn on saved versions (deleted/replaced files) for cloud jobs too — that is what turns “the wrong file synced up” into a two-minute recovery
GoodSync offers encryption options for jobs on supported file systems — worth using when the destination is a server you do not control
Test the route at small size first: one test folder, one Analyze, one Sync, then check the destination with your own eyes in the cloud app or an SFTP client
🔴 The sentence to remember: putting files in Google Drive or OneDrive through a 2-way sync is not a backup — it is the same data with an internet address. The protection comes from the job design around it: one-way direction, deletions held back, versions saved. The video shows the job window where all three of those choices live.
🎥 Watch the Complete Video
The video walks the folder browser live — watch the endpoints get picked so these four routes feel like one skill, not four.
No. GoodSync is the messenger, not the warehouse. Your files go directly between the two endpoints of the job — folder to folder, PC to PC, or PC to the cloud account you signed in with. With GoodSync Connect the transfer is peer-to-peer after the mediator introduces the machines; nothing is stored on GoodSync's servers.
Can I sync the same folder to Google Drive and an SFTP server?
Yes — as two separate jobs sharing the same Left folder. Offices often do exactly this: one job to a local or SFTP destination for speed, one job to a cloud drive for off-site safety. Just schedule them at different times so both are not reading the folder in the same minute.
My cloud job failed halfway with a quota or storage error. What now?
That is the cloud account refusing more data, not a GoodSync fault. Free the space or upgrade the plan, then simply run the job again — GoodSync compares both sides on Analyze and copies only what is still missing, so nothing already uploaded is sent twice.
This guide is based on the Technical Anshu GoodSync Explained video • Stuck on any step? Ask in the video comments — you will get a reply there 🙏