If the application being imported does not exist in the target environment, you can use Lifecycle Management to create the application shell. Before importing information, however, you must edit the migration definition file with target-specific information. See Creating an Essbase Application Shell, Creating a Planning Application Shell, and Creating a Financial Management Application Shell.
Applications must be assigned to an application group or belong to the Default Application Group before migrations can occur. You cannot migrate applications belonging to the Default Application Group if two applications with the same name exist.
Note: | Only the Default Application Group can have multiple applications with the same name. However, artifact migration cannot occur unless they are assigned to another Application Group. |