Each platform requires unique information to create a connection to it. You can find instructions on how to create a connection for each platform DryvIQ supports under Commonly Used Platforms.

An account map is used to map users from one platform to another. The easiest way to do this is to create an account map CSV file and import the mapping file into the account map that will be used for the job.

Yes, you can add filters to a job to include or exclude specific content based on various filters. Learn how to add filters to your job here.

When link detection is enabled, Simulation job execution time increases due to the need to download the document into memory for link detection, which is an additional step that isn’t normally done as part of the Simulation process. Transfer job execution time is not impacted when link detection is enabled because the document is scanned while the document is in memory as part of the normal migration process. Learn more about how link detection affects job performance here.

Link remediation operates separately from the migration and does not affect transfer times or speed. However, it adds time to the project as it requires an additional process for remediating links after files are migrated. The link remediation process is roughly equivalent to the extra time it would take to do another delta run on a document count basis. For example, remediating links in 1000 files in a job takes about as much time as running a delta run with modifications to a 1000 files. This should be factored in when planning your project if you plan on using link detection and remediation. Learn more here.

No, simulation jobs do not count towards the Data Migrated “Volume used” until simulation is disabled and the job is run as a standard job (in normal mode).