Migration Challenges from ATG 9.x to ATG 10.x

Following are some of the migration challenges from ATG 9.x to ATG 10.x:

• The migration can be achieved by executing scripts provided by Oracle, the information about which could be found in their detailed migration guide or the same can be accessed on this page. However, it is recommended to have an experienced migration architect deal with migration initiative from 9.x to 10.x versions.
• It has been found that migrating directly from any ATG 9.x  versions to any ATG 10.x versions landed up with one or more issues. If the current ATG version is at 9.x, it may be advisable to first migrate to an intermediate 10.0.3 version and, then migrate to 10.1 or 10.1.x. From 10.1 to ATG 10.1.1, it is a direct installation.
• Data Migration: There has been changes in data definitions from ATG 9.x to ATG 10.x. Some of the key tables to pay attention to while migrating are users, orders, catalog, category, product, promotions, SKU etc. You could adopt one of the two strategies which is either exporting and importing the data and, another being recreating the whole catalog in BCC and do a full deployment. In case of doing export and import model with data related to catalogs, the care has to be taken to associate the data such as category, products and SKUs with SITES which is a new feature in ATG 10.x. In relation with migrating customer and order related data, as per Oracle recommendation, it is advisable to do a full migration of PRODUCTION_CORE schema.  Migrating promotions has its own set of challenges how to deal with active and expired promotions.
• Source Code Changes: There are classes which have got moved to different packages and the same forces changes in the source code. The care has to be taken to update the source code files with appropriate package paths.