LcmImport: Restore Cube Files

The lcmimport CLI command for Essbase restores cube artifacts from a Lifecycle Management (LCM) .zip file. To run this command, you must be the power user who created the application, or a service administrator.


lcmImport [-verbose] -zipfilename filename [-overwrite] [-targetappName targetApplicationName] [-artifactlist artifactList]
Option Abbreviation Description
-verbose -v Optional. Show extended descriptions
-zipfilename -z Name of compressed file containing backup files
-overwrite -o Optional. Recreate the target application.
-targetappName -ta Optional. Target application name, if you want it to be different from the source name.
-artifactlist -al Optional. Name of the file containing the list of artifacts to import. This file can be generated from lcmexport.

To skip artifacts, comment out or delete entries from the list. For example, to skip importing audit records, comment out that line, as shown:

# ------------IMPORT-----------------
import @Provisions
import @Databases/Basic
#import @Databases/Basic/Audit
import @Databases/Basic/Text_files
import @Databases/Basic/Xml_files
import @Databases/Basic/Calc_scripts
import @Databases/Basic/Open_XML_Excel_files
import @Databases/Basic/ScenarioManagement
import @Databases/Basic/Provisions
import @Databases/Basic/Rule_files

To control import order, rearrange the import entries in the text file.

If –overwrite is used, the import operation deletes and recreates the entire application, importing only the artifacts present in the list. If –overwrite is not used, the import operation includes the artifacts specified in the list, without impacting any other artifacts already present in the target application.


  • This command, like other CLI commands, can be used from outside the Essbase machine, whereas the LCM utility must be run within the Essbase machine.

  • After the LCM import completes, you may need to take further action to restore migrated connections to external sources. To do this, open the connection and enter the password.

  • When partitions exist between cubes being migrated, you must import the data source before the data target. Otherwise, partition definitions may not be restored.

    Lifecycle Management (LCM) import operations (and Migration Utility import) are not supported for migration of federated partitions. Federated partitions must be recreated manually on the target.

  • LCM Import does not migrate location alias credentials. You must replace your location alias credentials, either by recreating location aliases using MaxL, or by editing the location alias credentials in the XML exported by LCM Export.


esscs lcmImport -z C:/Sample/ -o -al C:/Sample/Sample.txt