Getting Started With DryvIQ Migrate

Welcome to the DryvIQ Migrate knowledge base! Our goal is to help you find all the answers to your questions related to your migration project.

To help you as you get started with DryvIQ, we’ve provided a basic migration project outline below with links to the relevant documentation in the knowledge base. Be sure to reference the information throughout your project to ensure the best migration results.

1. Identify the accounts you need to use to connect to your platforms.

The account used to create the connection to a platform needs to have the proper permissions to read/write/update/delete the content based on the actions you want DryvIQ to perform as part of your migration. Refer to the connector documentation for the platforms that will be used in your migration project to understand more about what account types and permissions are required.

2. Create your connections.

You need to create at least one source and destination connection. Depending on how you plan to run your migration, you may need more connections. The information required to create each connection depends on the platform. Refer to the connector documentation for your platforms to ensure you have the required information to create the connections.

3. Create your user and group maps.

User and group maps allow you to specify how you want to link accounts on the source platform to accounts on the destination platform. This link ensures permissions are preserved between platforms. Maps are made up of three parts based on how you need to link the users and groups.

  1. User or group mapping policy: This tells DryvIQ which information to use when mapping users and groups between platforms. This mapping only works if the selected information matches between platforms.

  2. Exceptions mapping: This mapping is optional and is only used when information between platforms varies (such as email addresses, last names, etc.). It allows you to explicitly map users between platforms.

  3. Exclusion mapping: This mapping is optional and is only used if there are users or groups whose permissions you don’t want to preserve.

4. Create your jobs.

At this point, you are ready to create jobs. Generally, you will select a few pilot accounts and run the test jobs in simulation mode to ensure you are seeing the expected results. This give you the opportunity to recreate the pilot jobs using different configurations to maximize transfer success. Once you are satisfied with the simulation results, you can convert the job to a transfer job and even add a schedule to the job (if one was not added when the simulation job was created).

5. Review the job reports.

As the jobs runs, you will review the job reports to identify the progress of the job. The reports help you understand the progress of individual jobs or groups of jobs depending on how you want to review the information.

6 Remediate the flagged items.

Flagged items are files DryvIQ could not migrate. Items can be flagged for multiple reasons, so DryvIQ provides remediation best practices to help you navigate the various error messages associated with your flagged items.

Please note that the links above represent only some of the information available in our knowledge base, so make sure you take a look around. If you're unable to locate answers to your questions, we recommend visiting our Frequently Asked Questions (FAQ) page. We’ve diligently compiled this information to provide quick but comprehensive responses to the most commonly asked questions. If you still have questions, please feel free to contact your designated DryvIQ Consultative Services representative or submit a ticket to DryvIQ Customer Support.

DryvIQ Migrate Version: 5.7.1
Release Date: May 17, 2024