Getting Started With a Migration Project

Learn the basic migration project structure to help get you started.


Overview

Welcome to the DryvIQ Platform Knowledge Center! Our goal is to help you find all the answers to your questions related to your migration project.

To help you get started with the DryvIQ Platform, we’ve provided a basic migration project outline below, along with links to the relevant documentation in the knowledge center. Review the information throughout your project to ensure the best migration results.

1. Identify the accounts for your platform connections.

The account used to create the connection to a platform must have the proper permissions to read/write/update/delete content based on the actions you want DryvIQ to perform during your migration. Refer to the connector documentation for the platforms you will use in your migration project to understand the account types and permissions required.

2. Create your connections.

You need to create at least one source and destination connection. You may need more connections depending on how you plan to run your migration. The information required to make each connection depends on the platform. Refer to the connector documentation for your platforms to ensure you have the necessary 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 that permissions are preserved between platforms. Maps are composed of three parts, based on how you need to link users and groups.

  1. User or Group Mapping Policy: This policy specifies which information DryvIQ uses 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 map users explicitly 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 allows you 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 (if one was not added when the simulation job was created).

5. Review the job reports.

As the jobs run, review the job reports to track progress. 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 that DryvIQ was unable to 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 center, so make sure you take a look around. If you cannot locate answers to your questions, we recommend visiting our “Migration Frequently Asked Questions” 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 contact your designated DryvIQ Consulting Services representative or submit a ticket to DryvIQ Customer Support.