#Active Directory Migration Process

The sections below contain the general migration process for Active Directory Migration. The details outlined in this document can serve as general guidelines with some minor adjustments.

More steps may be needed, and some steps included in the process may be optional according to your migration requirements.

#Preparation

Before the migration, you need to identify what object types Fly supports. See the Supported and Unsupported List.

#1. Assess the environment and requirements

• Identify the scope of objects to be migrated: Users, Groups, Contacts, and Organizational Units (OUs).

• Review Supported and Unsupported Object Types, refer to Supported and Unsupported List for details.

• Check interdependencies with applications relying on Active Directory attributes.

#2. Install and configure Active Directory agents

Refer to the following sections to prepare and install the Active Directory migration agent.

#2.1 Install source agent

Ensure the source environment meets the system and network prerequisites, then install the Active Directory agent on a server that connects to the source Active Directory.

#2.2 Configure source agent

Generate and enter the API key, connection name, and service account credentials. Then, scan source objects to identify nodes (OUs, users, groups, and contacts) for migration. Refer to Install the Source Agent for details.

#2.3 Install destination agent

Install the Active Directory agent on a server that connects to the destination Active Directory.

#2.4 Configure destination agent

Enter the shared key, API key, and destination Active Directory administrator credentials, then configure the object import interval. Refer to Install the Destination Agent for details.

The Active Directory migration agent can be upgraded to the latest version manually or automatically, depending on your configuration. Refer to Upgrade the Agent for details.

#3. Create source and destination connections

Refer to Create a Connection to connect Fly to your source and destination Active Directory.

Note the following:

• The API key is essential for agent communication with Fly. Ensure you generate, copy, and securely store it during the connection setup.

• Download and install the agent matching the connection role. Due to the security configurations, while installing agents directly on domain controllers is also technically supported, we recommend installing them on non-domain-controller machines that can connect to the source/destination Active Directory.

#4. Design the migration policy

An Active Directory migration policy allows you to configure attribute mappings (e.g., sAMAccountName, CN, etc.), how users should be created in the destination, conflict resolution policies (skip or overwrite), whether to sync user passwords, whether to migrate group members, whether to enable email notifications. Refer to Create a Migration Policy for details.

#5. Plan a pilot run

We recommend you do a pilot run for the following purposes:

• Get familiar with the Fly interface and understand the whole migration process.

• Discover any potential issues early and resolve them before production migration.

• Understand the throttling situation in case content size is large and then try to resolve with source and destination.

#Migration Execution

Refer to the following sections to execute the migration.

#1. Create a migration project

Navigate to Fly > Projects and create a new Active Directory migration project. Then, associate source and destination connections, assign the relevant migration policy, and apply tags for easier project filtering and organization. Refer to Create a Project for details.

#2. Configure migration mappings

There are different ways to create migration mappings:

• Scan from source agent (tree or search mode).

• Import mappings in bulk via Excel template.

Ensure each mapping includes the source object, destination OU, and object type. Review and confirm mappings before running migration jobs. Refer to Create Migration Mappings for details.

#3. Perform regular full migrations

Select the mappings for which you want to run migrations. If this is your first migration for the selected mappings, select Migration > Full migration to migrate all objects.

Refer to Run Migrations to Migrate Objects for details.

#4. Perform regular incremental migrations

If issues occur during a full migration job or if there are changes in the source Active Directory, you can run incremental migrations to handle new, updated, and failed data. Refer to Run Migrations to Migrate Objects for details.

#5. Perform post-migration actions

After the migrations, you can also perform the following actions:

• Sync user passwords – To sync the passwords of users mapped to the destination or newly created users to the destination.

• Migrate object managers – To migrate the managers of the selected objects.

• Migrate group membership – To migrate the membership of the selected groups.

• Sync objects OU changes – To sync OU changes of source objects to the destination.

Refer to Post-migration for details.

#6. Validate migration results

• Check the migration reports and mapping statuses.

• Check the membership, attribute properties, and any exceptions.

• Check if there are no failed data in the job report.

#7. Finalize and clean up

• Export the final reports and archive the mappings.

• (Optional) Remove agents once the migration is complete. Refer to Uninstall the Agent for details.