Migrating Objects Using CSV Files

This section explains how to migrate objects using export_input.csv file and import_input.csv file. These files are present in $FIC_HOME/utility/Migration/conf folder. This folder also contains migration.properties file and OBJECTMIGRATION.xml file. You need not make any entry in the OBJECTMIGRATION.xml file.

To migrate objects, perform the following steps:

  1. Navigate to the $FIC_HOME/utility/Migration/conf folder
  2. Populate the migration.properties file with appropriate values as explained in the following table.

    The values in the properties file are updated by the installer. If you want to Run this utility from another location, the values should be specified accordingly.

    Table 16-4 Names in the Property file and their Descriptions

    Name Description
    EXPORTIMPORT_BASEPATH

    Absolute path of the directory where the metadata/ archive and metadata/ restore folders are created.

    For example:

    EXPORTIMPORT_BASEPATH= /scratch/ofsaaweb/OFSAAI/utility/Migration

    FIC_HOME

    OFSAAI installation directory.

    For example: FIC_HOME /scratch/ofsaaweb/OFSAAI

    READ_FROM_CSV

    Specify whether to read the inputs from CSV files or OBJECTMIGRATION.xml file.

    Set this as Y. Then the utility reads from export_input.csv file for exporting objects or from import_input.csv file for importing objects.

    USERID

    Specify the user ID of the OFSAAI user who will be running the migration utility. Ensure the user is mapped to the specific source Information Domain / Segment.

    The user id should be provided in capital letters.

    Note: The User ID or Service accounts are “SMS Auth Only” in case of SSO and LDAP configured setups.

    LOCALE Set this as en_US.
    INFODOM

    Specify the Information Domain from where objects need to be exported/ imported.

    The information domain name should be provided in capital letters.

    FOLDER

    This is applicable only for importing.

    Specify the Code of the folder /segment to which you need to import objects. The folder value should be provided in capital letters.

    If IMPORTALL_TARGET_FOLDER is not specified in case of IMPORTALL=Y, then the objects are imported to this FOLDER.

    MODE

    Set the mode of the operation as:

    EXPORT - for exporting objects

    IMPORT for importing objects

    DUMP_FILE_NAME

    For exporting, specify the name of the file to be exported which will be created under $FIC_HOME/utility/Migration/metadata/archive folder as a .DMP file.

    For importing, specify the name of the file to be imported, which is present under $FIC_HOME/utility/Migration/metadata/restore folder.

    IMPORTALL

    Y indicates that all exported objects in the .DMP file (dump) will be imported (regardless of any specific OBJECT entries in the import_input.csv or OBJECTMIGRATION.XML file).

    N indicates that only objects explicitly specified in the import_input.csv or OBJECTMIGRATION.XML file will be imported (provided they are already exported and available in the dump file).

    Note: When migrating Sandbox, IMPORTALL should be N.

    IMPORTALL_TARGET_FOLDER Specify the target folder to which you want to import objects when you specify IMPORTALL as Y. If this is not specified, it imports the objects to FOLDER.
    FAILONERROR

    Specify whether to fail operation on any error.

    Y - Stops the import process if there is any error.

    N - Continues with the next object in the import process even if there is an error.

    OVERWRITE

    Specify whether to overwrite any existing metadata.

    Y - Overwrites metadata even if the metadata already exists.

    N - Will not overwrite the object if it already exists and continue migrating the next object.

    RETAIN_IDS

    Specify whether to retain the source AMHM objects after migration.

    Y – Retain the Source AMHM object IDs.

    N – Will not retain the Source AMHM object IDs.

    If you have chosen the value 'Y' for RETAIN_ID and the Target system does not consume the object ID of the Source object, the ID will be retained while migration. If the object in the Target system consumes the object ID of the Source, the ID will not be retained while migration. Instead, it will generate a new ID.

    MIGRATION_CODE

    Enter the unique migration code to identify the status of the migration process.

    For example: 8860

  3. Update import_input.csv or export_input.csv files based on whether you want to import or export objects as explained in the following tables.

    Note:

    Any updates done are available in the export_input_template.csv and import_input_template.csv files. Before invoking the command line utility, ensure that the updates available in the templates files are available in the export_input.csv and import_input.csv files.