How can we help?

Why GoodSync

GoodSync stands out for its combination of speed, precision, and trustworthiness. Key strengths include:

• Bidirectional and one-way sync with granular control over conflict resolution
• Block-level copying that transfers only changed portions of files, reducing bandwidth and time
• Propagation of deletions, moves, and renames without duplicating data
• Automated scheduling with real-time, periodic, or event-triggered runs
• End-to-end encryption and versioning for recovery from accidental changes or ransomware
• Broad protocol support including SFTP, WebDAV, SMB, and native connectors for major cloud providers

Pairing Strategy with Google Drive

Pairing GoodSync with Google Drive creates a layered approach that separates active collaboration from controlled backup and archival. Your Gmail address is the same Google identity used for Drive and for authorizing GoodSync—keep that pairing explicit when planning file access and jobs. The strategy works as follows:

1. Google Drive as the collaboration layer. Google Drive remains the live workspace where users create, edit, and share documents. It handles day-to-day access, permissions, and multi-user editing.
2. File access from your Gmail (Google) account. Gmail and Google Drive sit under the same Google account: the address you use to sign in to Gmail is the identity that owns "My Drive," shared libraries, and sharing invitations. For pairing, treat that account as the single source of truth for who can see which files:
   • Connector sign-in — When GoodSync uses Google's native Drive connector, you authorize it with that Google account (OAuth). Use the same account that should read and write the folders you are migrating or backing up; service accounts or delegated access may apply in Google Workspace—match the job to the correct identity.
   • Where files live — Email attachments are not Drive files until you save them to Drive or use Drive-native workflows. Prefer keeping authoritative copies in Drive (or Shared drives) so GoodSync jobs target stable paths rather than mailbox attachments.
   • Scope of access — Decide whether each sync job should use My Drive, a Shared drive, or Shared with me content; permissions follow the Google account you use to connect. Align sharing in Drive with who needs backup or migration before scheduling GoodSync.
3. GoodSync as the migration and backup layer. GoodSync connects directly to Google Drive via its native connector and handles the heavier lifting:
   • Initial migration — bulk transfers from legacy file servers, personal drives, or other cloud platforms into Google Drive, preserving folder structures and metadata
   • Scheduled backups — automated one-way sync from Google Drive to a secondary location (local NAS, external drive, or alternate cloud) on a defined cadence
   • Versioned snapshots — retention of prior file versions outside of Drive's native history, protecting against corruption, accidental deletion, or account compromise
4. Separation of concerns. Google Drive's built-in sync client is optimized for access, not backup. Relying on it alone means deletions and ransomware-encrypted files propagate everywhere. GoodSync breaks that chain by maintaining an independent, policy-driven copy that Drive cannot overwrite.
5. Verification and audit. GoodSync logs every transfer with checksums and timestamps, giving a clear audit trail for compliance and recovery scenarios — something Drive alone does not provide.