The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This chapter provides detailed information on migrating data from earlier releases of Cisco Secure ACS to Cisco ISE.
You can migrate earlier releases of Cisco Secure ACS data to the Cisco Secure ACS, Release 5.5 or later state so that it can be migrated to a Cisco ISE, Release 2.2, appliance using the migration tool.
If you are running Cisco Secure ACS, Release 3.x in your environment, upgrade to a migration-supported version of Cisco Secure ACS, Release 4.x.
Step 1 | Check the upgrade path for Cisco Secure ACS, Release 3.x, as described in the Installation Guide for Cisco Secure ACS Solution Engine 4.2. |
Step 2 | Upgrade your Cisco Secure ACS, Release 3.x server to a migration-supported version of the Cisco Secure ACS, Release 4.x. For example, upgrade to one of the following Cisco Secure ACS 4.2.0.124, or Cisco Secure ACS 4.2.1 releases. |
Step 3 | After the upgrade, follow the steps that describe migrating from Cisco Secure ACS, Release 4.x . |
If you are not running one of the migration-supported versions of Cisco Secure ACS, Release 4.x in your environment, upgrade to a point where you can migrate from Cisco Secure ACS, Release 4.x to Cisco Secure ACS, Release 4.2.
If you are running Cisco Secure ACS, Release 5.x in your environment, you must upgrade to Cisco Secure ACS, Release 5.5 or later.
To migrate internal users from Cisco Secure ACS 5.x to Cisco ISE, you must install Cisco Secure ACS 5.5 Patch 4 or later or ACS 5.6 or ACS 5.7 patch 1 or later or ACS 5.8, and then start the migration.