Secure Sync for
Google Drive & SharePoint

Context: Connection between Google Drive and a SharePoint server in a secure zone connected over data diodes

• The organization has one on-premises SharePoint server in a highly secure zone
• The only connection from this server is over data diodes.
• The organization needs to move documents one-way between SharePoint and Google Drive, online.

Goal: Unidirectional, highly secure data transfer

How it works: Documents are automatically transferred from a SharePoint server in a highly secure zone to another in a less secure one, using a connection through Data Diodes and filtering if necessary.

Context: Synchronizing documents across various SharePoint and Google environments with precise control using filter rules.

• A business wants to synchronize specific documents using rules to ensure that up-to-date documents are accessible everywhere on a strictly need-to-know basis.
• Filters can be based on file name or type, start date, metadata flags, and others.
• Filtering on metadata such as retention period, approval state, or confidentiality status, makes it easier to meet business rules and legal obligations when sharing documents.
• For example, synchronization could be set up to prevent documents marked as classified from being synchronized, or to indicate that only finalized and approved versions are synchronized.
• Synchronization filters can be combined as needed, for example, synchronize .pdf files in the Invoices folder that aren't marked "Draft" and were created after a specific date.

Goal: Consistent synchronization of specific documents from SharePoint to Google

How it works: The synchronization filter rules specify which files you want to synchronize and which ones you don't. This intelligent, selective method supports regulatory compliance, protects confidential data, and guarantees that only appropriate files are synchronized between platforms.

Context: An organization is moving from SharePoint to Google

• The migration process for document libraries is expected to take a long time because of the number of files and their size.
• The organization would like users to be able to always have access to the documents, even when the migration is ongoing.

Goal: Zero downtime migration between the two environments

How it works: The source SharePoint environment is kept available during the migration, with ongoing synchronization. It is only disconnected when all the documents are available in the target Google environment. The same can be done in the opposite direction (synchronization from Google to SharePoint)

Context: An organization wants to bring together documents from various SharePoint servers and Google Drive.

• The organization wants to consolidate documents into a single, easily managed central location
• One or more document libraries in the target SharePoint server or Google Drive become the destination for documents coming from multiple source SharePoint Servers.

Goal: Centralized access and management of distributed documents

How it works: Multiple sync pairs are established between each source server and the target server, indicating the rules for the synchronization.