---
title: IPS Migration Wizard
slug: ips-migration-wizard
createdAt: 2026-07-27T04:11:10.299Z
---

IPS Migration wizard enables seamless migration of RADIUS and TACACS+ configuration, and also automatically creates basic IPS configuration needed for these use cases to work right after migration is complete.

### Prerequisites

Before proceeding with the IPS Migration wizard, export the RADIUS/TACACS+ clients’ details in the form of CSV file from Cisco ACS.

Follow the below steps to export the RADIUS/TACACS+ clients’ details:

1. Log in to Cisco ACS GUI.
2. Navigate to **Network Resources > Network Devices and AAA Clients**.
3. Select all the clients.
4. Click **Export**.

::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/Zq37-3qJJ_DGENexjIkcL_ipsmigrationwizard.png" position="flex-start" size="80" width="1253" height="636" initialPath="images/ips_migration_wizard.png" githubPath="images/ips_migration_wizard.png" darkWidth="1253" darkHeight="636" showCaption="false"}

### Configuring RADIUS and TACACS+ Migration using IPS Migration Wizard

The IPS Migration wizard helps administrators in creating RADIUS and TACACS+ configuration using the CSV file exported from Cisco ACS.

To configure RADIUS and TACACS+ migration using IPS Wizard:

1. Log in to the IPS Admin console.
2. Select **Wizards > Migration > RADIUS and TACACS+ config migration**. The Introduction window lists the configuration steps.
3. Click **Next**.

::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/Vor48Itk3MmxcGrEdbgSB_configuringradiusandtacacs.png" position="flex-start" size="80" width="954" height="552" initialPath="images/configuring_radius_and_tacacs.png" githubPath="images/configuring_radius_and_tacacs.png" showCaption="false"}

In the Import File window, choose the use cases for configuration import – the **RADIUS clients&#x20;**&#x63;heck box or **TACACS+ clients** check box or both. Based on these selections, migration wizard provides steps to create the Radius policies followed by the Shell policies.

5. Click **Browse** and select the CSV file that is exported from Cisco ACS.
6. Click **Next**. After receiving confirmation for successful upload, click **Next**.:inlineImage[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/nRz1sFQkiSSzrOYUhjpbM_tacacsclients.png" alt caption size="80" width="961" height="554"}

:::hint{type="info"}
At any stage of the migration wizard, you can click **Previous** to go back to the previous window or click **Cancel** to cancel the migration.
:::

1. Next step is to configure the Active Directory server. You can select one from the existing list of AD servers or add a new AD server.
   - To select from the existing list, click **Select existing server&#x20;**&#x61;nd choose the required AD server from the list.
   - To add a new AD server, click **Add new AD server**. Enter the name, domain name, Kerberos realm, user name, password that matches with the ACS configurations.
2. Click **Test** to validate the Active Directory configuration. This will take a few seconds to complete.
3. Once the validation is successful, click **Next**.

::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/MUuE4lBOiXULNNAjRHplq_radiusandtacacsconfigmigrationreturnattribute.png" position="flex-start" size="80" width="958" height="616" initialPath="images/radius_and_tacacs_config_migration_return_attribute.png" githubPath="images/radius_and_tacacs_config_migration_return_attribute.png" showCaption="false"}

In the RADIUS Return Attribute Policies window, click **New Policy** and enter a name to the Radius policy.

11. Select Location Groups.

:::hint{type="info"}
IPS supports single location group; nested location groups are not supported. The subgroups created on ACS have to be configured as individual groups in IPS.
:::

1. Select the **Return Attribute** check box. Select appropriate Vendor Specific Attribute as Return Attribute. In the **Value** field, define the ACL/Firewall Filter. For example, Return Attribute is **Filter-Id&#x20;**&#x61;nd Value is compliant.in.
2. Click **Save Changes&#x20;**&#x74;o save the configuration.
3. Click **Next**.

::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/A344pEj3FSvyXd1hIgfE4_returnattribute.png" position="flex-start" size="80" width="926" height="595" initialPath="images/return_attribute.png" githubPath="images/return_attribute.png" showCaption="false"}

::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/rwfkN7odz-mBQIfyYJgFi_radiusandtacacsconfigmigrationreturnattribute1.png" position="flex-start" size="80" width="958" height="616" initialPath="images/radius_and_tacacs_config_migration_return_attribute_1.png" githubPath="images/radius_and_tacacs_config_migration_return_attribute_1.png" showCaption="false"}

1. In the Shell Policies window, click **New Policy** and enter a name to the Shell policy.
2. Define external group, device type, shell profile and the command set.
3. Click Save Changes to save the configuration.
4. Click **Next**.

::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/SGRgV1cfJITHdMGEm5JRq_radiusandtacacsconfigmigrationshellpolicies.png" position="flex-start" size="80" width="960" height="616" initialPath="images/radius_and_tacacs_config_migration_shell_policies.png" githubPath="images/radius_and_tacacs_config_migration_shell_policies.png" showCaption="false"}

::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/QAWGbhAzaZX_NBvf5hF6G_radiusandtacacsconfigmigrationshellpolicies2.png" position="flex-start" size="80" width="893" height="575" initialPath="images/radius_and_tacacs_config_migration_shell_policies_2.png" githubPath="images/radius_and_tacacs_config_migration_shell_policies_2.png" showCaption="false"}

1. In the Summary window, verify the details and click **Finish** to complete the RADIUS and TACACS+ configuration migration.

::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/igslJDdJVxrJj-8gFLjzh_radiusandtacacsconfigmigrationsummary.png" position="flex-start" size="80" width="964" height="619" initialPath="images/radius_and_tacacs_config_migration_summary.png" githubPath="images/radius_and_tacacs_config_migration_summary.png" showCaption="false"}

::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/mT2PXWNnuu_sVBgkgUAvY_radiusandtacacsconfigmigrationstatus.png" position="flex-start" size="44" width="442" height="257" initialPath="images/radius_and_tacacs_config_migration_status.png" githubPath="images/radius_and_tacacs_config_migration_status.png" showCaption="false"}

For more information on 802.1X authentication and troubleshooting, see 802.1X Authentication with Cisco Switch cook book
