Open

On This Page

Overview

This page is the technical reference for DryvIQ’s Link Detection and Remediation feature. It defines what is and is not supported, including supported file types, link formats, platforms, and known limitations.

Scope and Processing Constraints

Link Detection and Remediation operate within a defined set of global constraints. These rules apply regardless of platform or file type and explain why some files or links may not be processed.

1. Only the latest version of each file is processed: Link detection and remediation operate only on the current (latest) version of each file when the job runs.

   1. Previous file versions are not scanned.

   2. Links that exist only in older versions will not be detected or remediated.

2. Files must be readable for content inspection: To detect and update links, DryvIQ must be able to open and read the file contents. If DryvIQ cannot read the file (due to source system limitations, connector limitations, access restrictions, file corruption, etc.), it cannot perform link detection and link remediation on that file.

3. Detection and remediation apply only to files within the job scope: A file must be included in the current migration job for its links to be detected. A link can only be remediated if the target item is also part of the same job or another completed migration job. If a link points to content outside the scope of all migration jobs, DryvIQ cannot determine its destination location or remediate it. These links are reported with an appropriate remediation status and can be exported from the Links report to support manual remediation once the linked content is migrated or otherwise made available in the destination.

4. Job filters affect what is scanned: Job-level filters apply to link detection. If a file is excluded by filters, it is not scanned for links. Any links inside excluded files will not appear in link reports and cannot be remediated.

5. External and out-of-scope links cannot be remediated: Links pointing to external websites, systems not included in the migration, or content not part of any job may be detected, but they cannot be remediated because there is no destination item to map them to.

Supported File Types

Link Detection and Remediation supports the following file types:

• Microsoft Files: DOCX, PPTX, and XLSX (available in Microsoft Office 2007 and newer)

• Google Files: Google Docs, Google Sheets, and Google Slides. Link detection occurs after export to Microsoft Office format during transfer; only links preserved by Google's export process are detected.

Supported Link Types

Links are stored differently depending on how they are added to a document. Link Detection and Remediation operate only on specific, supported link types. The table below defines which link types are supported for detection, remediation, or neither. Support is based on how the link is stored in the file, not on the destination system. For example, a hyperlink pointing to SharePoint, Box, a file share, or a website is treated the same way when stored as a standard hyperlink. Links to external websites and other non-migrated destinations are detected but are not remediated, as they do not represent migrated content.

 Connector Support

Link detection and link remediation behave differently across connectors. Link detection operates directly on file content and is supported across all connectors for supported file and link types. In contrast, link remediation requires DryvIQ to interpret and resolve link URLs using connector-specific capabilities.

Link Detection

Link detection is connector-agnostic. DryvIQ scans supported file types (such as .docx, .xlsx, and .pptx) and extracts embedded links directly from the file content, regardless of the source or destination connector.

Link Remediation

Link remediation is connector-dependent and supported only with connectors that can interpret and resolve link URLs. If a connector does not support this capability, links will be detected but not remediated.

Connectors With Link Remediation Support

DryvIQ supports both link detection and link remediation for the following connectors:

• Box/Box Service Account

• Dropbox for Business/Dropbox Teams Folders

• Egnyte

• File System (NFS/SMB)

• Google Drive/Shared Drive/Workspace

• Microsoft Office 365/OneDrive/Teams (Standard and GCC High)

• Nasuni

Connectors Without Link Remediation Support

For connectors that do not support URL resolution, DryvIQ supports only link detection. Links will be identified and reported but cannot be automatically remediated. If a connector is not listed as supporting link remediation, it should be considered detection-only. This includes, but is not limited to:

• Amazon S3

• Autodesk

• Citrix Sharefile

• Documentum

• Docusign

• Google Cloud Storage

• Hitachi

• Opentext

• Procore

• SFTP

• Syncplicity

Supported Platform URL Formats

Link remediation is supported for the following platforms and link types. 

Box

If the link in your document points to a Box file or folder, including links created using Box’s Office Online integration, DryvIQ can remediate it. Otherwise, DryvIQ can’t update it.

Dropbox

DryvIQ can remediate a link to a Dropbox file using a direct preview link. DryvIQ will also remediate a shared link only when Dropbox is the source connection. It treats the shared link as a native-item link and does not create a new shared link on the destination.

Older Dropbox Shared Links

Dropbox has older shared link formats, but DryvIQ does not guarantee remediation for these formats. Even for the supported shared link format, certain scenarios (such as changing the ownership of items pointed to by a shared link) may affect DryvIQ’s ability to remediate shared links. 

Egnyte

DryvIQ supports the remediation of several Egnyte link formats that reference files or folders stored in Egnyte. These links are typically generated when users copy links from the Egnyte web interface or share content with others.

Google

DryvIQ can remediate links in documents that point to a supported Google file type, such as Docs, Sheets, Slides, or Drive file and folder URLs.

Microsoft

For OneDrive and SharePoint, DryvIQ currently remediates only file-based links. This means DryvIQ can update links that point directly to documents (such as Word documents, Excel workbooks, and PowerPoint presentations).

Links pointing to folders or entire SharePoint sites are detected but not remediated automatically. If your documents contain folder paths or site URLs, those links will need to be updated manually after the migration to ensure they point to the correct locations.

Network File System and Nasuni

DryvIQ supports the detection and remediation of file-based links in content stored on NFS-based file systems. 

Application-Specific Behavior

Different applications store links in different ways. In some cases, features that appear to create “links” actually embed or import content, which removes the ability to detect or rewrite the original reference.

This section describes application-specific behaviors and limitations that affect link detection and remediation.