AvePoint Docs
Graph API
My support tickets
Graph API
My support tickets
English

    Home > Perform Active Directory Migrations > Create a Migration Policy

    Export to PDF

    Create a Migration Policy

    An Active Directory migration policy allows you to define how to map the source and destination Active Directory objects and how to create users in the destination Active Directory, configure the conflict resolutions, migration options, and other settings.

    Refer to the following steps to configure a migration policy for Active Directory migrations:

    1. Click Policies under Settings in the left pane.

    2. Click Migration policies to access the Migration policies page.

    3. Click the Active Directory tab.

    4. Click Create migration policy. The Create migration policy panel appears.

    5. Enter a name and an optional description for the policy, and then click Next.

    6. In the What do you want to migrate? Section, configure how to map the source and destination Active Directory objects and how to create users in the destination Active Directory:

      • How to map the source and destination Active Directory objects? – Select the attributes you want to map for the source and destination objects from the corresponding drop-down list.

      • You can click the Add (Add button.) button to add more mappings, or click the Remove (Remove button.) button to remove an added mapping.

        Fly will use the first attribute mapping to map an object. If the object cannot be mapped, Fly will try to map it using the second attribute mapping, and so on. If no destination object can be mapped using the configured attribute mappings, Fly will create a new object in the destination Active Directory.

        *Note: After Fly migrates a source object based on the attribute mappings configured in the migration policy, the GUID of the object will be saved into the Fly database. If you change the attributes of the source object and run a new migration job to migrate the object, Fly will migrate the object based on the saved GUID.

        *Note: If the source object can be mapped to multiple destination objects based on the attribute mappings configured in the migration policy, the migration of the source object will fail.

      • How to create users in the destination Active Directory? – Select the account format of users that need to be created in the destination.

    7. In the Conflict resolution section, configure the conflict resolution when the source object conflicts with an existing object in the destination. Refer to the following detailed information on each conflict resolution.

    ResolutionConflictNo Conflict
    SkipIgnore the conflicting object and do nothing in the destination.A new object will be created.
    OverwriteOverwrite the conflicting object attributes in the destination based on the source object attributes.A new object will be created.

    1. Click Next after you finish configuring the conflict resolutions.

    2. In the Additional options & mappings step, you can configure the following settings for migrations.

      • Sync user passwords – With this checkbox selected, the passwords of users created by Fly during the migration will be synced to the destination. If the option is not selected, the newly created destination users will be unavailable after the migration.

      • Sync Security Identifier (SID) History – Select this checkbox to enable the Security Identifier (SID) History migration. Ensure that the Security Identifier (SID) History scan is enabled in the Active Directory Migration Source Agent Configuration, and that a scan job has been run first.

      • Add members to destination Active Directory groups – Select this checkbox if you want to migrate memberships of Active Directory groups.

      • Customized features – This function is unavailable for Active Directory migrations now.

    3. Click Next to configure Notifications setting.

    4. Select the Send project level notifications (all mappings within a project) checkbox and configure the settings to send migration email notifications to specific recipients after the migration. The migration email notifications are based on the project level, which summarizes the project name and the mapping count of each migration status.

      • Recurrence – Enter a positive integer to define the recurrence days for the notifications.

      • Start date and time – Select a start date and time to send the first notification. The later notifications will be sent at the selected time based on the recurrence.

        If you want to configure the end date and time of the notifications, you can select the Configure end date and time checkbox and select a date and time.

      • Send migration email notifications to – Define the recipients who will receive the notifications.

      • Email template – Create an email template for the notifications by clicking the Add (Button: Add button.) button. Refer to Manage Email Settings for details on how to create an email template. You can also select an existing email template from the drop-down list.

    5. Click Save to save the migration policy.

    On the Migration policies page, you can manage existing policies.

    - Set as default – Select a policy and click **Set as default** to set it as the default policy. The default policy will be automatically selected when you create projects. - Edit – Click the policy name link to edit the policy. - Delete – Select a policy and click **Delete** to delete it. You can also select multiple policies and click **Delete** to delete them. - Copy – This allows you to quickly create a new policy with similar configurations by completing the following steps: 1. Select your target policy, and click **Make a copy**. You can also open your target policy, and click **Make a copy** on the **Edit migration policy** page. 2. Check the settings and make updates if necessary on the **Copy migration policy** page. 3. Click **Save**.