Home | Connectors | Google Drive | Google Drive - OpenText Documentum Integration and Automation

Google Drive - OpenText Documentum Integration and Automation

Integrate Google Drive Cloud Storage and OpenText Documentum Cloud Storage apps with any of the apps from the library with just a few clicks. Create automated workflows by integrating your apps.

Common Integration Use Cases Between Google Drive and OpenText Documentum

1. Controlled transfer of working documents from Google Drive to Documentum for formal records management

Teams can draft, review, and collaborate on documents in Google Drive, then automatically or manually promote approved versions into OpenText Documentum for retention, classification, and records control. This is useful for policies, SOPs, quality documents, and regulated submissions where collaboration is needed early, but final content must be governed under strict compliance rules.

  • Direction: Google Drive to OpenText Documentum
  • Business value: Faster collaboration without losing compliance control at the final stage
  • Typical users: Quality, legal, regulatory affairs, and operations teams

2. Publishing approved controlled documents from Documentum to Google Drive for broad internal access

After documents are approved and locked in Documentum, selected read-only copies can be published to Google Drive shared folders for easy access by business users, field teams, or project groups. This helps distribute current procedures, reference materials, and approved templates without exposing the master controlled record to editing.

  • Direction: OpenText Documentum to Google Drive
  • Business value: Improves document accessibility while preserving a single governed source of truth
  • Typical users: Operations, training, sales enablement, and distributed teams

3. External collaboration in Google Drive with final archival in Documentum

Organizations can use Google Drive to exchange drafts with consultants, contractors, or partner organizations, then archive the final accepted deliverable in Documentum once the work is complete. This pattern is effective for marketing assets, project deliverables, engineering documents, and vendor-created content that must eventually be retained under enterprise governance.

  • Direction: Google Drive to OpenText Documentum, with external collaboration occurring in Google Drive
  • Business value: Enables flexible external collaboration while ensuring long-term retention and auditability
  • Typical users: Procurement, project management, marketing, and engineering

4. Compliance review workflow for documents created in Google Drive

Business users can create documents in Google Drive and trigger a review workflow in Documentum for legal, regulatory, or quality approval. Documentum can manage version control, review tasks, and approval status, then return the approved version to Drive for distribution. This is especially valuable for controlled communications, policy updates, and regulated content that requires formal sign-off.

  • Direction: Bi-directional
  • Business value: Reduces manual handoffs and improves traceability of approvals
  • Typical users: Compliance, legal, quality assurance, and document control teams

5. Migration of legacy shared-drive content into governed enterprise repositories

Organizations often use Google Drive as a working repository, but older or high-risk content may need to be migrated into Documentum for retention, legal hold, or lifecycle management. Integration can classify files by folder, metadata, owner, or document type and move only the content that requires formal governance, leaving active collaboration content in Drive.

  • Direction: Google Drive to OpenText Documentum
  • Business value: Reduces compliance risk and improves information lifecycle management
  • Typical users: Records management, IT, legal, and compliance

6. Synchronization of metadata and document status between systems

Document metadata such as document type, project code, owner, approval status, and retention category can be synchronized between Google Drive and Documentum. For example, a file in Drive can display a status such as draft, under review, or approved based on its corresponding record in Documentum, helping users understand which version is authoritative.

  • Direction: Bi-directional
  • Business value: Improves document visibility and reduces version confusion
  • Typical users: Project teams, document controllers, and business operations

7. Automated retention and disposition for business files stored in Google Drive

Files in Google Drive that meet defined business rules can be transferred to Documentum for retention scheduling, legal hold, and disposition management. This is particularly useful for contracts, audit evidence, HR records, and project documentation that must be preserved for a specific period and then disposed of according to policy.

  • Direction: Google Drive to OpenText Documentum
  • Business value: Supports defensible retention practices and reduces storage sprawl
  • Typical users: Legal, HR, finance, and records management

8. Cross-system search and access to approved content for enterprise users

Users working in Google Drive can be given links or surfaced references to approved documents stored in Documentum, allowing them to find authoritative content without duplicating files. This is useful for organizations that want Google Drive to remain the collaboration layer while Documentum serves as the controlled content repository for official documents.

  • Direction: OpenText Documentum to Google Drive, with search and reference access across both systems
  • Business value: Reduces duplicate storage and helps users find the right version quickly
  • Typical users: All business users, especially knowledge workers and frontline teams

How to integrate and automate Google Drive with OpenText Documentum using OneTeg?